[dev] Ansel Tags

[Michael Rubinsky]

Quoting Chuck Hagenbuch <chuck at horde.org>:

> Quoting Michael Rubinsky <mike at theupstairsroom.com>:
>
>> Except that the tags that you already have choosen are not shown in
>> the related tags box...for instance I am browsing tags "birthday"
>> and  "fun".  I have an image tagged with both "birthday" and "fun"
>> so I see  that image. My friend has a image tagged with "birthday",
>> "fun" and  "naked" (thankfully this image is private).  In the
>> related tags  element, I would be shown only "naked" since I have
>> already browsed to  the "birthday" and "fun" images.
>
> Oh, okay. I think I get it now.
>
>> Anyway, I have already "fixed" this by checking the number of hits
>> each related tag would return - and that check DOES take into
>> account  permissions...but as I said in my commit message, it could
>> be a little  more resource intensive due to the extra queries...
>
> Sounds a -lot- more resource intensive. Perhaps related tags should be
> an optional feature?

I was thinking that as well, my thought was to make the entire tag  
implementation optional though...but I think limiting it to just the  
related tags would be better :)

So, just to walk through the process *without* related tags - since  
there would be no way to narrow the tag search, or "browse down' if  
you will, we'd have to add a 'view similar images' link (in addition  
to the individual tag links) to the image and gallery views. So, we'd  
be able to view both 1) all resources that match a single tag or 2)  
all the tags the resource is tagged with.

The permissions problem also expresses itself with the tag cloud.  
Since there is no way of knowing if the resources that are tagged with  
each tagged are viewable by the current user (witout checking *every*  
tagged resource) it's possible to be shown tags in the cloud that  
would result in no viewable images on the results page.  I think this  
one we will either have to live with, or just do without the cloud all  
together as I don't see any way of fixing that with the current  
permission code.


Sounds like the permissions checks should also be
> cached where possible. I think we need a concept of permission atoms,
> that can be individually cached and arbitrarily combined. But that's
> definitely a Horde 4/roles item.

This sounds interesting. Out of curiosity, how would that help in a  
case like this?  We'd still need to check the indivdidual permissions  
of each gallery that contains images that are tagged with our search  
tags....

> How about for now you turn related tags off by default (

OK.

since you
> should still be able to browse other images with the same tags - the
> related part is nice, but not essential), and we'll try and get this
> stable for a 1.0 release with Horde 3.2.

Cool! A 1.0 for Ansel!


Thanks,
mike

--
The Horde Project (www.horde.org)
mrubinsk at horde.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-keys
Size: 2013 bytes
Desc: PGP Public Key
Url : http://lists.horde.org/archives/dev/attachments/20070512/1f1a9679/attachment.bin