The Community Engine Blog

News, tools, and analysis for innovating in the information economy

  • Main
  • RSS 2.0

« Web 2.0 can and will be commoditized | | High Octane Blogging — Susie Gardner weighs in »

Archives are at the heart of decentralized communities

In decentralized, emergent communities, the community archive defines the community over time. Therefore, designers of such communities need to pay attention to the processes by which these archives emerge. The ongoing debate over folksonomy provides us with a public record of decentralized archiving strategies that do and don't work.

Sections:

Topics:

In describing one of the fundamental building blocks of decentralized blog communities, James Farmer remarks:

If you’re implementing blogs in your school, college or university or even organisation one of the first things you’re going to want to think about is aggregation.

BLOGSAVVY » Savvy public aggreation tools, the key to binding your blogs together

Nothing could be more true. The “River of News” style public aggregators that James then goes on to review all do a good job of displaying a decentralized community's zeitgeist. But, by itself, zeitgeist as captured by near real-time blog aggregation is insufficient to sustain decentralized communities for the long term. For that, these communities need archives.

Archives crystallize what such communities found important over time and ultimately define the community.

I'm sure this must sound like anathema to advocates of the emergent, interactive Web 2.0, but I'm not advocating static archives created by some central authority. Rather, I'm talking about living archives created by the community. To be concrete, folksonomy is an example of an emergent, community-created archive. In folksonomy people “tag the Internet” and then share their tags with the community. As people in the community start to tag the same items, rough consensus emerges over the prevalent community views (tags) regarding these items along with a sampling of the diversity of viewpoints that surround them. As such, folksonomy captures both the consensus and the dissent that surrounds all cultural artifacts.

Over time, the navigation structure derived from folksonomy is richer and messier than what might arise from a formal taxonomic approach or a ratings system that consists merely of evaluations. My guess is that some of the major problems that have been noted in this area derive from the fact that most folksonomies are open to the world at large. In this regard, I think limited scope real-world experiments like Infoworld's use of folksonomy in its editorial process will be instructive. InfoWorld is a focused publication, and the editors are more or less on the same page. Thus, there is likely to be consensus on their main views of the world but still plenty of room for dissent.

What might emerge from the InfoWorld experiment is a reasonable navigation structure along with enough underlying disagreement to make for interesting exploration. The value to the InfoWorld editor community is a record of what they found important over time and where they disagreed, in other words the things that shaped their intellectual output, the ultimate reason for being of their community.

The general message for those wishing to create decentralized communities is that the success of the archiving strategy, not just capturing zeitgeist, will determine the community's long-term success or failure. The ongoing debate over things like folksonomy will provide us with a public record of emerging archive strategies that do and don't work.

Bud posted this on June 2, 2005

Trackback Pings

TrackBack URL for this entry:
http://thecommunityengine.com/cgi-sys/cgiwrap/fpgibson/thecommunityengine.com/mt/mt-tb.cgi/593

Comments

Post a comment




Remember Me?