structuring your web based knowledge system

Question

How would you structure the information which you maintain to keep all of the information about your projects and clients at your fingertips. We are finding that ours is becoming so large that at times we don't know for sure what we are looking for only that we know it is in the knowledge-base. We use a confluence in a classical hierarchy with tagging as well. Any suggestions or articles would be appreciated.

Answer 1

In a company I worked once we bought a server from Google that indexed pretty good all our documents.
I believe it has a 5 digit price tag.

Answer 2

Why not trying a search engine? Sth. like lucene (solr/luke)?

Solr is amazing fast even with millions of documents in the index.

Answer 3

Put the documents in an Alfresco instance:

1. You get to access the document repository like a shared folder, moving, editing and copying files like it's a regular shared folder.
2. You get full text indexing and a search interface for free
3. You get all the standard things we're used to: folder structure, tags + metadata if you need it
4. You get versioning for free
5. You can get a first instance up and running in an hour