[thelist] Blog based KM tool

[Boris Mann]

My instinctual response was to answer "Drupal" as well, especially when
you mentioned multiple people with their own blogs (and potentially
different types of info, like how-tos, interesting links, etc. etc.)
BUT it's PHP/MySQL, not Coldfusion/SQLServer...

I bet the Drupal folks would be real happy if you ported it to CF :)

In any case, I'll second the motion that it is a good tool to look at,
even if you do end up rolling your own. One feature I'll point out is
the ability to add in multiple RSS "feeds" in which individual items
can then be "blogged" directly by members -- a good way to pull in
market-specific information, news, general tips, etc.

A Wiki, especially for marketing types ( kidding! kidding! although
they will likely complain about the use of GeekCaps ), will likely take
waaaay too much discipline on the part of end users to maintain /
organize.

--
Boris Mann
http://www.bmannconsulting.com

On Tuesday, January 7, 2003, at 10:37  AM, Pete Prodoehl wrote:

>
> I'd recommend you take a look at Drupal. It sounds like it might do
> just
> what you want. It supports multiple users with different levels of
> access, (each user would have their own blog) and you could create the
> taxonomy to organize everything. It's also searchable.
>
>     http://drupal.org/
>
> It's a PHP/MySQL (or PostgreSQL) application. even if you don't use it,
> you might get some good ideas from it.
>
> Pete
>
> Drew Shiel wrote:
>>
>> Hi folks;
>>
>> I'm about to start a new project, which is for work, but done on my
>> own
>> time. It's to be a weblog-based knowledge management tool.

>> <snip>

>> It'll be written in Cold Fusion and use a SQL Server database - more
>> because that's what we have in house and what I want to learn more
>> about
>> than because of any inherent suitability.
>>
>> So... I'd like some suggestions as to how to go about this. Should I
>> build
>> some kind of index from the blogs, get users to tag them with
>> keywords, do
>> a plain grep-for-that-text, or what? Are there any extra features I
>> could
>> or should build in? Would comments be useful on this? Should I allow
>> for
>> "personal" as well as work entries?
>>
>> This'll probably be a long-term project, since it's coming out of my
>> own
>> time.
>>