[Tickets #8470] Re: linking facs to adresses from turba

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/8470
------------------------------------------------------------------------------
  Ticket             | 8470
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
-Summary            | linking face names to adresses from turba
+Summary            | linking facs to adresses from turba
  Queue              | Ansel
  Version            | HEAD
  Type               | Enhancement
  State              | Rejected
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2009-08-01 16:01) wrote:

> i understand that it might be complicated, but so we have apps that  
> don't work really together and information must be looked up  
> everytime on my one.

I still don't see this as a mainstream use case, but that's just me.

> the permission issue isn't the problem from my point of view. if  
> someone doesn't have the permisson to read the information from  
> turba then don't provide a link or detail information, and if  
> available do it. every turba entry has its own id in database, so  
> only linking this id to the pic would be enough,

Yes, I'm aware of how the data is stored and how to link the data. To  
be exact, we would need to store both a source identifier and the  
contact's uid. Also, depending on the type of source you're using in  
Turba (not everybody uses a SQL based source), it's possible that only  
the user tagging the face would ever be able to see the tag. The  
comment about the permissions was referring to issues internal to  
Ansel in how gallery permissions are stored.

Linking the data is not the issue.  The issue is the overhead in  
performing the SQL queries in Ansel along with api calls for  
validation and permission checking for _each_and_every_ face. On an  
image view this may not be an issue, but for views that show multiple  
faces it can become a problem.

OTOH, I'd be more apt to include this if we allow ONLY the owner of an  
image to link a face to a contact AND to allow ONLY the owner of an  
image to see the link.

No, it's not impossible, but IMO it's not worth either the overhead or  
the time to implement it.  Like I said, if you (or anyone else)  
provides a patch, I'd be willing to look at it, and possibly add it as  
a feature that could be explicitly turned on.