Summary | linking faces to addresses from turba |
Queue | Ansel |
Queue Version | HEAD |
Type | Enhancement |
State | Rejected |
Priority | 1. Low |
Owners | |
Requester | bigmichi1 (at) bigmichi1 (dot) de |
Created | 07/31/2009 (5876 days ago) |
Due | |
Updated | 08/10/2009 (5866 days ago) |
Assigned | |
Resolved | 07/31/2009 (5876 days ago) |
Milestone | |
Patch | No |
Summary ⇒ linking facs to adresses from turba
don't work really together and information must be looked up
everytime on my one.
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,
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.
don't work really together and information must be looked up everytime
on my one. 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, permissions must then only
be checked when detail information are queried
State ⇒ Rejected
Version ⇒ HEAD
this would be of limited value and would complicate an already
complicated permissions issue when dealing with faces and personal
and/or non-share enabled address book sources.
I'd be willing to look at any patches, but I don't plan on implementing this.
Priority ⇒ 1. Low
Type ⇒ Enhancement
Summary ⇒ linking face names to adresses from turba
Queue ⇒ Ansel
Milestone ⇒
Patch ⇒ No
State ⇒ New
adresses from turba, so that when viewing a pic we can jump directly
to the adress in turba to get more details from the person