| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
klogs
|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Thursday, August 22, 2002eRoom spruces up hosted collaboration offering. "NEXT WEEK COLLABORATION software provider eRoom plans to roll out an updated version of its hosted digital workplace offering, featuring integrated real-time communication tools and new business process capabilities."
Posted to klogs @ 2:41:01 PM ( comments)
Dody Gunawinata has set up a Manila/Radio community for his organization: AIESEC. Nice. [John Robb's Radio Weblog] I like it too. Is it possible to do something like this (I mean the home page) for Radio Community Server? Posted to klogs @ 2:26:02 PM ( comments)
You cannot make people smarter. Curiouser and curiouser! quotes Mathemagenic:
And continues with his concerns: "My fear is that klogging will only thrive in organisations that are healthy, and that there may not be enough of them. Or, worse, that klogging will thrive as a control mechanism imposed by insecure and fearful management. I don't want to be a part of that." [Curiouser and curiouser!] Very good point. I don't that the former is something to be afraid of. It may work as a nice indicator of the health of the company ;).[from my PhD proposal] Learning is best described by the metaphor “you can lead horse to the water, but you cannot make it drinking”, or as Joseph Kessels says “you cannot make people smarter”. Even in the case of formal learning an organisation does not have control over employee’s brain and heart, so in order to benefit from employee learning, companies have to find the way to support and encourage it without full control. The author believes that the answer lies in supporting interplay between individual and organisational needs by relating and integrating employee-driven informal learning and organisation-driven formal learning.
Posted to klogs @ 2:23:01 PM ( comments)
Ray Ozzie: Architecture matters: The Rebirth of Public Discussion. "In traditional discussion, topics and their responses are contained and organized within a centralized database. The relationship between topics and responses is generally maintained in a manner specific to the nature of the database - that is, in newsgroups the messages might be related by Message-ID hyperlinks or crudely by title, in Notes they are related by the $REF hyperlink, and so on. Summary-level "views" are generated through database queries. And that has been the general architectural design pattern of public discussions for quite some time.
But blogs accomplish public discussion through a far different architectural design pattern. In the Well's terminology, taken to its extreme, you own your own words. If someone on a blog "posts a topic", others can respond, but generally do so in their own blogs, hyperlinked back to the topic's permalink. This goes on and on, back and forth. In essence, it's the same hyperlinking mechanism as the traditional discussion design pattern, except that the topics and responses are spread out all over the Web. And the reason that it "solves" the signal:noise problem is that nobody bothers to link to the "flamers" or "spammers", and thus they remain out of the loop, or form their own loops away from the mainstream discussion. A pure architectural solution to a nagging social issue that crops up online." Posted to klogs @ 10:57:09 AM ( comments)
Tuesday, August 13, 2002Blunt Force Trauma: Managing Local and Remote URLs in Radio. "I don't know anything about writing macros for Frontier so how would I create an ifLocal macro? For my reference mainly, as I don't fully understand the fix but I most definitely understand the problem -- it's bitten me a couple of times already." Shouldn't be difficult. Code of the macros was posted already:
on ifLocal (url1="/", url2=radio.macros.weblogUrl()) {
if radioResponder.flSameMachine {return (url1)} else {return (url2)}
} Create file ifLocal.txt in Macros folder of Radio, copy this code there and you're done. Now you can use iflocal() in your templates. Posted to klogs @ 9:23:22 PM ( comments)
Technography: Meeting Checklist. Intelligence of your meeting system. 23 smart and not-so-smart things people do. Posted to klogs @ 6:34:10 PM ( comments)
Sunday, August 11, 2002Jon Udell on Radio deployment descriptors. "I was reminded of: (1) how much non-default configuration I depend on, (2) how little I remembered having done that configuration, and (3) how hard it was to articulate, then transfer, that configuration." I'm glad I'm not the only one who struggles with custom configuration. I'm doing installations for my co-workers and would like to be able to set up proper configuration with minimal effort. The easiest way that I found is probably to use radioStartupCommands.txt file, which is executed at every startup. The problem is that weblogData.root (which is where the most preferences are stored) is not opened when radioStartupCommands.txt is executed, so I need to open the database myself in radioStartupCommands.txt. Any ideas on how to do that? Ideally I would like to have "Save configuration as" button that will create that file with ALL setting I currently have, so I can enable/disable some of them and update Radio configuration. One more Radio question: How to update templates without republishing the whole site? Posted to klogs @ 1:40:35 PM ( comments)
Wednesday, August 07, 2002Jon Udell is moving his weblog to new home using Radio and external FTP site. One of the gotchas he found:
"- If you hardcode your site address anywhere, you'll get burned. I did this in a few places. For example, I had:
http://radio.weblogs.com/0100887/stories/2002/03/16/storylist.html
instead of:
<%radio.weblog.getUrl()%>stories/2002/03/16/storylist.html"
Right. In fact, I use my own macro to do just that and little bit more. <%ifLocal()%> macro, which looks like this:
on ifLocal (url1="/", url2=radio.macros.weblogUrl()) {
if radioResponder.flSameMachine {return (url1)} else {return (url2)}
}
Posted to klogs @ 12:39:22 AM ( comments)
Sunday, July 21, 2002Blunt Force Trauma: Traction vs. Radio -- A Personal View. "The e-mail interface is something Radio badly needs. The more ways you can get data into, and out of, a KM system the more likely everyone is to use it. The ability to easily e-mail log summaries, as well as accept and route incoming e-mail posts, is a very nice feature." Agree. I'm running community server behind the firewall and for some business users it's very important to be connected via email. Although, there are some tools like news2email and the ability to mail to category that allow you to do that.
"There is one other broad philosophical issue: Traction seems built for a top-down, hierarchal, controlled access system -- precisely what you would expect from a CIA software project. Radio is much more a bottom-up package -- a grass roots, revolutionary, damn-the-IT department sort of thing that people can get excited about, have fun with, proselytize. Can you imagine anyone but a CIO or IT-geek proselytizing the densely woven fabric of Traction?" Right to the point. I'm all in favor of bottom-up approach, but it seems like the most practical approach is somewhere inbetween: company will benefit from using both, top-down and bottom-up systems, they just have to be well-connected. Posted to klogs @ 11:07:27 PM ( comments)
Saturday, July 20, 2002John Robb: Knowledge Sharing -- a new buzzword that makes a lot more sense that Knowledge Management. Posted to klogs @ 11:53:30 PM ( comments)
Tuesday, July 16, 2002Mikel Maron: myRadio release. "myRadio is a digital dashboard styled tool, much like My Yahoo, but based on Radio Userland and desktop aggregation." I think I'll give it a try. Posted to klogs @ 11:24:55 PM ( comments)
Updated 8/22/2002; 5:13:36 PM