[chandler-users] Keeping a knowledge base
mimi at osafoundation.org
Tue Feb 19 12:52:46 PST 2008
It's funny that you call it knowledge base. We've been toying with
the idea of re-framing Chandler as a 'knowledge management' tool.
It's true we don't help you keep track of documents and other
resource material. Today 'knowledge' in Chandler is manually entered
via typing or copy and paste into the Notes field of every item. But
the design of Chandler is anchored around the idea of keeping track
of and processing that knowledge. We think that improving the 'Notes'
field experience is central to showing users that we take knowledge
workflows seriously. https://bugzilla.osafoundation.org/show_bug.cgi?
Can I re-frame what you're asking for as: A way to differentiate
between transient / ephemeral knowledge (meeting notes) and
persistent resource knowledge (articles, documents). We've talked
about adding a 'Resource Kind' which would essentially allow you to
do that. The 'Resource Kind' would provide users with 2 affordances:
1. The ability to mark any note, event, message as a Resource,
essentially a way to 'Archive' stuff you know has information you'll
find useful in the future.
2. The ability to attach other resources to the item (e.g. documents,
web pages, etc).
We've also talked about implementing a bookmarklet web widget that
would allow you to send web pages to your Chandler Hub account with
the click of a bookmark button.
You can track the 'Resource Kind' feature here: https://
It's a feature users ask for frequently and it would certainly help
us build a case for Chandler as a 'knowledge manager'.
On Feb 19, 2008, at 10:31 AM, Marcelo de Moraes Serpa wrote:
> Chandler does a great job on keeping track of tasks, appointments
> and quick-notes (even though quick-notes are not formalized kinds
> yet). However, there's other kind of data that also needs a secure,
> standards-compliant and open platform to be stored: Knowledge.
> By knowledge, I mean articles, tutorials, self-written material,
> documents and maybe even a journal (maybe a developer journal).
> I often find myself going to google more than I should do because
> things get forgotten. If I had stored the knowledge in a system
> that I trusted, I could just search it and find the information in
> What do you guys think we could use for such a system? Maybe the
> Chandler platform could be extended to support this dimension
> through a plugin? Maybe an online wiki? Tomboy?
> Hope you could share your views and experiences regarding this
> chandler-users mailing list
> chandler-users at osafoundation.org
More information about the chandler-users