The too-much-infomation society
rawn 100000R0P5 997 Views
As our developerWorks Community Editor, I'm faced with issues which are part talent management and part information management. Aside from all the regular issues of focusing effort and developing content to build a stronger community, I'm facing a happy problem of having so many enthusiatic contributors: what happens when there's too much to read?
It isn't hard to see this problem is evident; just try googling on a topic and see how many hits you get. Would you really want to read anything more than 100 entries?
In talking with James Snell and others a few weeks ago regarding corporate blogs, wikis and other such tools, we agreed that there are typically two ways of looking at who should contribute. We both agree everyone should be able to do so; but when you start running into large numbers, how do you organize this information?
First, there's the top-down approach where you pick the topics and find people to contribute to each category. This is quite commonly used; dW does this in our many zones.
Then there's also a bottom-up approach where you want topic experts to self-emerge from a population.
This second approach is harder to figure out, but the answer may not be as complicated, especially when you have a large population and numbers on your side.
I think the idea lies in building a Reputation network, modeled on trust. Each individual essentially would rate how a particular interaction with a potential expert turned out (in two types of trust, which I'll discuss later). You can then average all the trust ratings per candidate to determine their reputation. The number of interactions combined with this average trust rating describes their reputation.
Those with higher reputations automatically emerge as "experts" in whatever categories they want to focus on. The process is democratic and self-emergent within the community. For that matter it also automatically helps to define topic areas that people are interested in.
That's the basic principle. I'm quite sure there are many ways of looking at this, so I'd be curious to hear counterpoints.