[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-pim
Subject:    Re: [Kde-pim] Request for Comment - A Tag based information
From:       Volker Krause <volker.krause () rwth-aachen ! de>
Date:       2006-04-29 10:07:59
Message-ID: 200604291208.04707.volker.krause () rwth-aachen ! de
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Friday 28 April 2006 20:16, Punit Agrawal wrote:
> Thanks for the response Volker. Thought I'd been talking to myself(which
> in a way I was ;) ) for a bit.
>
> Volker Krause wrote:
> > A common (hierarchical) tagging system is something I would like to see
> > for Akonadi (http://pim.kde.org/akonadi). It could replace all the
> > various existing approaches (korganizer/kaddressbook categories, kmail
> > message status, knode scoring, ...) and would allow to retrieve all PIM
> > data having a certain tag. If this could be done by a even broader,
> > desktop wide system, even better.
> >
> > So yes, there is definitively interest in something like this :)
>
> The idea was to start small and integrate applications in a phased
> manner. And kdepim would be a an ideal place to test out the ideas out
> and refine the concept. Hence the post to kdepim. :) How does moving to
> Akonadi affect categories/classification? Wouldn't these now be
> stored/accessed via akonadi? And if so, then how does the akonadi+taggin
> system work? Does akonadi use the tagging system internally? Or do the
> applications use akonadi for storage but tagging system for classification?

There has been no work done in this area so far, so nothing is fixed yet.

My current idea about this is to have common base class for all data types 
stored in akonadi which provides a tagging API. Tags would be stored within 
the akonadi backend and could be used in queries.

But using a external tagging system would be possible as well since akonadi is 
supposed to provide unique and persistent ids for all items.

> Secondly, Tenor is attempting to do something similar. Though I am not
> sure if it'll fill the same space as what is being proposed. I am
> looking into it (basically talking to Scott and hearing what he has to
> say). In which case it would be better to concentrate effort than to
> dilute.
>
> Initially, when I started thinking of this, I wasn't thinking of a
> Summer of Code. But was wondering if anybody would be interested in
> mentoring such an effort. Or even just a common tagging system using
> akonadi?

I'm not an expert for tagging, contextual search etc., but I'm interested in 
co-mentoring akonadi projects.

> But if not, all is not lost. I would still like to work on this if there
> is interest.
>
> On further asking around/looking, it seems that a similar/same idea is
> already in playground/base/klabelbrowser. I was wondering if there was
> some reason why it is not being used. Any ideas?

regards
Volker

[Attachment #5 (application/pgp-signature)]

_______________________________________________
kde-pim mailing list
kde-pim@kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
kde-pim home page at http://pim.kde.org/

[prev in list] [next in list] [prev in thread] [next in thread]