May 09, 2003
Weblogs for business
A WEBLOG-BASED CONTENT ARCHITECTURE FOR BUSINESS
"In a previous post, The Weblog as Filing Cabinet, [the writer] proposed that business weblogs could be used to codify and 'publish', in a completely voluntary and personal manner, the individual worker's entire filing cabinet. The key advantage of providing such a capability is vastly increased access to, and sharing of, a company's knowledge. This post outlines a content architecture that could enable this to occur.
This architecture would have two principal components: The Enterprise Content Architecture and the Desktop Content Architecture..."
Posted by ghbrett at May 09, 2003 09:58 AM
Thank you very mutch!
Hmmm, lots of weird and random thoughts... but a few organized ones first.
I suspect that one could create intranet-blogs (intranogs?) that would only be viewable by individuals inside a company. This way, companies could encourage information sharing within the company but not fear losing oranizational knowledge to the outside world. I believe that Lou Rosenfeld has hit upon this theme a few times on his site. Knowledge portals or something akin to that.
Second thought- workers should consider what they do to be owned by a company. It is in their best interest to share information so that the corporation can succeed, and thus, their lot in the company is improved. Or something idyllic like that. Now, there is the real archival questions about all of this; archival in terms of what ones legal responsibilities are once a collection policy of any sort is put into place, formal or not. (My wife roundly/routinely chastises me for never erasing email. I think i have 90% of the email I have ever received stored.)
In terms of curator... I think that this is increasingly being moved to brute force computational search. As yucky as the idea is, Google rocks. If one uses a meta-search tool to combine the results of google (a brute force link analysis tool) with tools like autonomy (a "brute force" symantic analysis tool), the results can be really surprising, and many times better than a human. Yes, cold and sterile, but oft times the only solution when the source data sets become overwhelmingly large.
OK, rambled enough for the day.
...before I forget, "Google to fix blog noise problem" might be of some interest in terms of the entire SNR*/archive/curatorial debate. A new problem has appeared... Blogs create too much stuff. :)
I run away now...
* Signal to Noise Ration
Does a company want to share its knowledge? Without profit or compensation? Even moving one's files to an archival (hardcopy) repository involves all sorts of decisions regarding who will have access to what with which limitations....
The idea of shared individual files is intriguing but what would be the motivation? And who would have the time to collate the individual files into a meaningful collection (who in other words would be the curator)?