InfoQ

News

Tagging for Knowledge Management

Posted by Deborah Hartmann on Jun 09, 2006 02:47 PM

Community
Agile
Topics
Artifacts & Tools,
Collaboration
Tags
Web 2.0,
Podcasts,
Wiki
Tagging is a mechanism that has become wildly popular in recent Web 2.0 apps - partly in response to the difficulty of discovering highly relevant results using traditional search engines.  Del.icio.us provides a simple example of tagging in action.

The buzzword Web 2.0 ("web-two-oh") evokes, for some, a list of languages and tools: Ajax, Ruby, Rails, DiggFlickr.  This, in fact, puts the cart before the horse: Web 2.0 is widely considered to indicate a second generation of services available on the World Wide Web to allow people to collaborate and share information online.  These new languages and tools have emerged in response to this shift in the philosophy of internet computing.  Web 2.0 is democratic, social and participant-based - seemingly a perfect match for teams working in an Agile paradigm.

Although the term was coined in 2004, Web 2.0 applications often use a combination of techniques devised in the late 1990s, including public web service APIs (dating from 1998), Ajax (1998), and web syndication (1997).  The term includes "social software" such as blogs (~1997) and wikis (1995). In fact, some Agile teams have been using wiki servers to collaborate for a decade already.

So, back to tags. They let users to generate a "folksonomy", a collaboratively generated, open-ended labeling system that allows users to categorize content through the browser. Technically, this mechanism applies equally well to enterprise intranet applications as to the internet.  Like the searchable Wiki, tagging can allow information to coalesce and emerge over time.  Proponents claim that the freely chosen tags improve search effectiveness because content is categorized using a familiar, accessible, and shared vocabulary.  The "2.0" label certainly does apply to this mechanism - what a significant shift, allowing categories to emerge in this unplanned manner!

Web 2.0 detractors cite concerns over security, reliability and lack of control.  This shift of control from organization to individuals seems to be part of the problem with enterprise acceptance.  SAP's Kagermann dismisses blogs and wikis as "too unstructured to do 'real' office work".  Many proponents of Extreme Programming and Scrum will smile, finding this sentiment familiar (and, in their own realm, disproven).

Can our organizations tolerate the temporary chaos required to make these emergent processes work? And if so, could tagging enhance knowledge sharing and mining in our businesses?  One notable proponent suggests that Web 2.0 technologies can help alleviate some of the current knowledge mining woes:
No matter how technologically elegant their design, knowledge management "platforms" and "repositories" tend to quickly collapse under the weight of their own complexity. Using them turns out to be more trouble than it's worth - particularly for those employees who have the most valuable knowledge - and the platforms and repositories fall into disuse...
On his Controlled Agility blog, Geoffrey Hewson, Chief Knowledge Officer at the Software Productivity Center, has looked at problems and opportunities in his entry on Tagging and Enterprise Knowledge Management.  He has written on and included links about combining the bottom up tagging approach with a top-down ontological view; about inductive algorithms, tag quality and findability.  Hewson maintains that tagging brings to an enterprise a valid bottom-up mechanism of harnessing intelligence in their human network.

But after reading Hewson's post, the nagging question still remains: is tagging ready for prime time? Hewson does not address this.

Web 2.0 is not monolithic - it is a collection of rapidly maturing practices, attitudes and technologies - and some are sure to be more "enterprise ready" than others at any given point. The debate continues - interactively, on the web, of course :-)



While on the subject of collaboration, social software and wiki: Ward Cunningham, father ot fhe wiki, was interviewed earlier this year on SQLsummit.com. In that podcast he talked about social software, organizing for collaborative development and the future of software, among other subjects. (via TestDriven.com)

Related Sponsor

VersionOne is recognized by Agile practitioners as the leader in Agile project management tools. Companies such as Adobe, BBC, CNN, Dow, HP, IBM, Sony and 3M have turned to VersionOne to help deliver greater value to their customers.

1 comment

Reply

No matter what tagging could bring by Jerome Jar Posted Jun 11, 2006 11:28 AM
  1. Back to top

    No matter what tagging could bring

    Jun 11, 2006 11:28 AM by Jerome Jar

    I've decided to use tagging for our new website that is currently being designed. I guess tagging could help building a more considerate system based on recent tagging actions a user has done.

Exclusive Content

Rationalizing the Presentation Tier

Thin client paradigm characterized by web applications is a kludge that needs to be repudiated. Old compromises are no longer needed and it's time to move the presentation tier to where it belongs.

Agile Project Management: Lessons Learned at Google

In this presentation filmed during QCon 2007, Jeff Sutherland, the creator of Scrum, talks about his visit at Google to do an analysis of Google's first implementation of Scrum.

AtomServer – The Power of Publishing for Data Distribution

In this article, Bryon Jacob and Chris Berry introduce AtomServer, their implementation of a full-fledged Atom Store based on Apache Abdera, which is now available as open source.

An Introduction to Virtualization

It is easy to think that virtualization applies only to servers. In reality the recent resurgence of the concept is also being applied to networking, storage, and application infrastructure.

REST Anti-Patterns

In this article, Stefan Tilkov explains some of the most common anti-patterns found in applications that claim to follow a "RESTful" design and suggests ways to avoid them.

Choosing between Routing and Orchestration in an ESB

In this article, Adrien Louis and Marc Dutoo discuss the differences and relative merits of using orchestration vs. routing in a typical ESB setup, and discuss various implementation options.

Enterprise Batch Processing with Spring

Wayne Lund discusses batch processing, Spring Batch objectives and features, scenarios for usage, Spring Batch architecture, scaling, example code, failures and retrying, and the future roadmap.

User Story Estimation Techniques

Developer Jay Fields draws on his experiences as a ThoughtWorks consultant to describe effective user story estimation techniques.