[Tickets #6494] Re: Tag cloud

bugs at horde.org bugs at horde.org
Tue Mar 18 13:51:41 UTC 2008


DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/6494
-----------------------------------------------------------------------
 Ticket             | 6494
 Updated By         | Michael Rubinsky <mrubinsk at horde.org>
 Summary            | Tag cloud
 Queue              | Ansel
 Type               | Enhancement
 State              | Feedback
 Priority           | 1. Low
 Milestone          | 
 Patch              | 
 Owners             | 
-----------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2008-03-18 09:51) wrote:

> After importing my galleries, I auto-generated tags from captions. I see
that
> words significantly differs from galleries and images so I keep them 
> separated
> . It can go as a separate page listed in Ansel menu.

I'm not sure I agree with having two seperate tag clouds. I'd much rather
integrate a filter to limit to galleries or images in either the existing
results view or a more general serach function (something I've been meaning
to do when I get the time).

> btw: listTagInfo not limits any results. So just having the cloud 
> block I am g
> oing out execution time. I still haven't got time to deal with this
issue but
> you should really limit any possible long results.

That function already takes an array of tags to limit the search by and
only returns the full tag list if it is omitted...however, I can see you
point with large tag sets.  It does make sense to limit to the first, I
don't know, 500 or so tags (by resource count) if there are none passed in.




More information about the bugs mailing list