We (Sakai) do a very similar thing. [1] Only we don't store the path too the tag on the tagged node but we store the UUID of the tagnode. This way we should be able to move tags around and get the same flexibility as storing a path. A tag can just as easily be deleted.
Regards, Simon [1] http://confluence.sakaiproject.org/display/KERNDOC/KERN-554+File+Content+Tags+and+Hierarchy On 6 Jul 2010, at 10:42, Alexander Klimetschek wrote: > On Tue, Jul 6, 2010 at 11:22, [email protected] > <[email protected]> wrote: >> Hi all, >> I thought about a possible implementation of the tagging system. >> My idea is that an article can have a multi value node where can be saved >> the tags. This is useful because when I read an article I haven't to read >> another resource to know the related tags. >> In addition to this node, it's possible to create a parallel structure, with >> the tag value as root node and as children the UUIDs of the articles. >> In this way there is a duplication of information but it's easier to >> manipulate tags information in the system (for example tag clouds or search >> by tag could be processed in a very fast way). >> What do you think about? > > http://dev.day.com/content/ddc/blog/2009/04/cq5tags.html (built on > JCR) might give you some ideas ;-) > > Regards, > Alex > > -- > Alexander Klimetschek > [email protected]
