Community Tags doesn't keep the tags separate
| Project: | Community Tags |
| Version: | 5.x-1.x-dev |
| Component: | User interface |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
This module claims that it keeps tags separate. This is not true.
Any other member can tag his peer's content, while all tags are thrown into the same pile of tags. Hence the author has no immediate control over the tags, unless he/she goes into the node/edit area and deletes those tags.
This pretty much defies the purpose of this module, because on a site with thousands of users, this could lead to a disaster.
It would be much better if either of the following options would be adopted:
A) user's own tags are visible only to him (like with the Anotate module), while Author's tags are visible to everyone.
B) Everyone can see the new community tags, but the author has the right to easily and quickly delete those tags immediately on screen through AJAX.
#1
The tags are put into the same pile but the user who created the tag is able to delete them. In that sense it keeps tags separate. The additional options you've described do sound like they'd be useful on some sites.
#2
Yes, if such small details in granularity of this module would be improved, I'd say this would be an awesome module used across a variety of sites. For me personally this little issue was a show-stopper. I guess the whole trick is to give the Administrators more options in chosing how this module behaves.
Right now the module functions ok for a small multi-user blog, where let's say we'll have 3 very close friends and who have very strict conventions on how they tag each other's content. But in its current state it won't work for a communty site where random indibiduals meet, post articles and tag each others' articles.
Option "A" would be awesome for something like a Social Bookmarking site if this module wishes to behave like Delicious' Folksonomy. Are you planning to implement feature "A" ???
(of course, when implementing something like this some thought would need to be given on whether the nodes tagged communnally should appear under that tag in a general view to everyone else. For instance, Mary posted an article, and Tom hates Mary's politcal views, so he tags all her articles as "Bullshit". Then Joe comes along and browses through the Tagadelic Tag clouds and notices a Giant tag "Bullshit", and when he clicks it, he sees all of Mary's articles, which causes embarrassment and friction. In an ideal situation Administrators should be able to choose whether nodes should appear only under Author's tags, or under the Folksonomy tags too)
My suggestion "B" if combined with suggestion "A" would make this module truely the superstar of Drupal's Taxonomy modules. As a follow up on the above scenario, once Tom has tagged Marry's content, only 2 people would be able to see those new tags: Tom (the tagger) and Marry (because she is the author) ... and maybe also the Admins and people with special permissions to oversee and moderate folksonomies. Then Mary will have the choice of either accepting some of Tom's tags (green tick) or deleting them (red X) directly from the screen. The tags that she accepts become Author's tags and therefore can be universally visible and her article can be also listed under that new tag for everyone else to see.
What do you think?