Knowledge and information systems

What an organisation knows is rarely kept in one place. A knowledge system gathers it up and makes it findable, on open source and on your own infrastructure.

What an organisation knows is rarely kept in one place. It sits in mailboxes, on drives, in people’s heads and in a filing structure only the person who created it still understands. A knowledge and information system gathers that up and makes it findable.

Tools

As with the other building blocks, I work with open source software. Wiki.js and DokuWiki suit manuals, procedure descriptions and anything that can be written as a page. I use XWiki and MediaWiki where structure, permissions and templates matter, and Nextcloud Collectives when the knowledge should sit where the files already are.

DokuWiki needs no database and stores everything in text files, which makes backing it up and moving it simple. Wiki.js has the more modern interface, with full text search and permissions. XWiki handles structured fields and forms, while MediaWiki copes with large holdings and many authors. Which one fits depends on the case, not on preference.

My part

First I clarify with you what this is about: which knowledge is regularly missing, who looks for it, and where the search fails today. The choice of tool follows from that, not the other way round.

Then I set up the system. That includes the structure of the content, permissions and access, moving existing holdings across and connecting it to what is already running.

After that I look after operations: updates, backups and an introduction for the people who write and maintain the content. So you get consulting, prototype, delivery and upkeep from a single source.

Location

The system runs on your own infrastructure. What an organisation knows does not belong on someone else’s service whose terms can change. Open source leaves you the choice of where it sits.

Reservations

I am sceptical of a system that has no one to look after it. A wiki nobody has written in for six months is worse than none: it looks like an answer and gives the wrong one.

I am just as sceptical when every document is to end up in one place simply because it can. A knowledge system answers questions; a records system manages cases. Those are two different jobs, and a tool meant to do both at once usually does neither well.

Frequent questions

Wiki or document store?

A wiki answers questions, a store manages cases. Put both into one tool and you usually get neither of them well.

What happens to what is already there?

Existing pages, manuals and folder structures can be moved across. A short review shows how much of it is worth moving: a lot is out of date and stays behind.

Who writes in it afterwards?

Your people. A knowledge system maintained by a single person lasts exactly as long as their attention. That is why a walkthrough and an agreed responsibility are part of it.

Knowledge that sits only in people’s heads?

Let us talk about your project.

Call +49 228 629 380 60 I can be reached on working days. If I cannot pick up, I will call you back. Book appointment Take a free slot in the calendar A short conversation clears up a lot.