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

List:       kde-bugs-dist
Subject:    [Bug 128533] Why nested tags? What about freeform/freestyle tagging?
From:       Dragan Espenschied <drx () a-blast ! org>
Date:       2006-06-04 18:24:36
Message-ID: 20060604182436.26839.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=128533         




------- Additional Comments From drx a-blast org  2006-06-04 20:24 -------
I strongy encourage you to try out del.icio.us and flickr to see how tagging works \
there. You might also want to look at the Video/Audio editing software "Vegas" by \
Sony that uses such a tagging system to organize its library of sound and video \
clips.

For digiKam i suggest to use a similiar approach: Place a text input field under \
every picture. Tags should be entered separated by spaces. If a tag does not exist \
yet, it will be automatically created.

In a tag view, the user should see all the tags. By clicking on a tag, the pictures \
tagged like this should be visible, with their tags as "links" below them. When such \
a link is clicked, all the pictures with the first selected tag and the second \
selected tag should be visible ... like this you can easily refine your view. It is a \
nested structure on demand.

Like it is now made, tagging is very similiar to nested folders. What i can actually \
do is to place a picture into several nested "tag folders". The creation of new tags \
is as complicated as it is to manage hierarchical folders ... you have to chose your \
hierarchy level, select a menu entry "new tag" etc ... this is quite clumsy.

Tagging is only useful when the user does not spend most time organizing hierarchies, \
as it is already the case with the hierarchical file system.

I would recommend to adapt this "popular" tagging approach of flickr, del.icio.us \
etc, not only because it is very practical, but also because it is becoming a \
standard of what users expect when they hear the word "tagging".


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