[Tickets #7269] Re: Replace categories and groups with tags

bugs at horde.org bugs at horde.org
Sun Aug 31 17:36:58 UTC 2008


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

Ticket URL: http://bugs.horde.org/ticket/7269
------------------------------------------------------------------------------
  Ticket             | 7269
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | Replace categories and groups with tags
  Queue              | Turba
  Version            | HEAD
  Type               | Enhancement
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2008-08-31 13:36) wrote:

> It's already possible to have groups with contacts from different
> sources, if I'm not wrong, so that argument is moot. I share the
> concerns with external sources though. OTOH, the groups could
> probably be mapped to the tags attributes in these cases.

Yes, but if we replace the current contact group implementation with  
tags, we won't be able to add contacts from one source to a group  
within another without some trickery with the tags - like appending  
the source key to the tag. Again, unless I'm missing something which  
is entirely possible. :)

The other concern isn't so much contacts from different sources but  
knowing exactly which groups/tags a particular source contains. My  
thought process is: Individual contacts are tagged, placing them in a  
"group".  When you browse an individual address book source, to know  
what "groups" to display in that source we would need an additional  
query to the tag table/backend to find out which contacts in the  
current address book are tagged with what.

Another thought, what would happen if you have PERMS_READ on a source,  
but want to include a contact from that source in one of your groups?   
You would need to tag that contact, but don't have access to. Another  
issue is how to deal with sources that multiple people have PERMS_EDIT  
on. Tags would have to be per user, since I may not want a contact in  
the same group that someone else with access to that contact does.   
Again, just my observations, and I may be missing something here..





More information about the bugs mailing list