K-Log Networks and Communities
Note: This is another post to the K-Logs (knowledge management weblogs) community on Yahoo Groups. If you like this topic, you are welcome to join).
A large part of the magic behind K-Logging is the ability to connect participants to improve the rate, quantity, and quality of knowledge shared in an organization or community. Simply publishing a personal K-Log gets you part of the way there. However, to go to the next level you need to provide tools and information that help K-Loggers to connect to each other. How do you connect K-Logs? Through K-Log community software.
K-Log community software runs in a central location on the Intranet or the Web (or on a community leaders desktop) and acts like a hub for the K-Log network. Participants in the community connect to it by pointing their K-Log software to that hub. The steps involved are easy. When participants publish, they send information to the community software that is then aggregated with information from other participants, processed, and displayed as Web pages that the community can use to can use to connect to each other. This community information allows you to find the high quality sources within the community quickly. Once found, you can cement your connection to a high quality K-Log via a subscription ( see my earlier post for more information on this).
Here are the features that community software provides:
1) Recently updated K-Logs. This webpage lists K-Logs that have updated their sites recently. It tells you when they last updated (via a time-stamp) and organizes the updated K-Logs chronologically, with the most recent updates at the top of the page ( http://www.weblogs.com is an example of this). Additional functionality that is provided by Radio ( http://radio.userland.com), allows users to build a personal list or subset of recently updated K-Logs they want to track.
2) Referrer pages (referers for techies). A referrer page tracks the location of webpages that link to your site and provides into on the number of people that used that link to arrive at your site ( here is an example of my referrer list). An important part of K-Logging is knowing who is linking to you. This gives you information on who's reading your K-Log and how much influence they have (as measured by the number of people that use their link to travel to your site). By clicking on the referrer link you can quickly find out what other people are saying about your site or a particular post you made.
3) Search.
4) Traffic on community K-Logs ranked by number of page views. Here is an example of this. This information tells you who is getting the most traffic or readers in the community. The higher the traffic, the more influential that K-Log is.
5) A list of the most active and popular subscriptions. As mentioned earlier, subscriptions are a way to get news on recent updates to K-Logs you want to follow and from general news sources. Information on which subscriptions are the most popular and active is aggregated on this page. Here is an example of this type of page. This page combines subscriptions to general news sources as well as other K-Logs. This is a great place to find sources of news that may interest you.
Note: Another aspect of community software is that it provides a way for a company or organization to manage a network of K-Logs. For example: it can allow a community manager to set limits on file types and the amount of disk space consumed by each K-Log in the network on the hosting server.
UserLand is shipping a Radio Community Server that makes setting up a network like this easy. It's free software that runs as an application on UserLand's Frontier or Radio. Here is more about the Radio Community Server. So, if you want to build a K-Log network within the firewall at your corporation or organization, this is the software to use. Or, if you want to build a community of K-Loggers that transcend corporate or organizational boundaries, this is the software to use. If you are interested in learning more or need help thinking this through, contact me. [John Robb's Radio Weblog]
5:12:45 AM
|