Hi,

As I have asked my end-users to test my site, they almost unanimously agree that the original Author of a node must also have the ability to delete not only his own tags, but also the tags that were given to his post by other users.

There are 2 main reasons for this:
(A) that's the whole concept of "Authorship"!
and
(B) What if a user tags another user's node wrongly, or with a typo, or even with a derogatory word (like "Bullsh*t" or "hippie ramblings of a lunatic") ???

The node Author must be able to delete these tags on his node with AJAX just as easily as users can delete their own "My Tags". I'd say this is Critical!

Another great feature would be to also create a Role-based ability to delete community tags. So that moderators and editors can also delete other users tags through AJAX if they wish.

Thanks again for a great module!

Comments

patchak’s picture

patchak commented

I think for that kind of community interaction you should use community managed taxonomy module instead of this one maybe???

Patchak

WildBill’s picture

WildBill commented

I'm with drupalina, this would be a very nice feature to have.

WildBill’s picture

WildBill commented
Title: Node Author must be able to detele the unwanted tags » Node Author must be able to delete the unwanted tags
Version: 5.x-1.0-beta1 » 6.x-1.0-beta1

Changing to 6.x-1.0 as it's been a while since the original ticket was opened, and the feature doesn't exist yet.

TC44’s picture

TC44 commented

+1 for this feature.

entrigan’s picture

entrigan commented

Just to clarify: the node author can delete tags using the normal node/edit form. The issue is allowing for the management through the nifty ajax interface.

I think this issue begs for a look at 2 of the main use cases:
1) Content is tagged by community members to facilitate tagging and categorization for the content relative to the site
2) Content is tagged by community member for use by themselves.

This feature helps with case 1, but would hurt case 2, hence it would have to be an optional feature to be turned on per vocabulary in the com tags admin page.

Designing the UI will be another challenge. I think the easiest implementation would be just to add delete functionality to the "all tags" section of the com tags form. We would probably also need to think hard about the permissions issue. Can anyone who has edit permission on the node edit the tags? perhaps only the node author? or perhaps anyone in a certain role?. Not sure the best way to tackle permissions.

Thoughts?

WildBill’s picture

WildBill commented

@entrigan - I could be wrong, but it seems to me that case #2 falls outside the original scope of this module. If the administrator wanted to facilitate users tagging for their own use only (i.e. bookmarking) then they would just use the Flag module or something better suited to that purpose...

entrigan’s picture

entrigan commented

@wildbill: I am curious more about your thoughts on this issue. Specifically I think flag module does not allow for "custom" tags, and I am not aware of a module that is better suited for this purpose.

For example if someone wants to replicate delicious style tagging, where each user has their own set of tags for a node, that are mainly intended for personal categorization.

At its core I think Community Tags is about recording info about who tagged what when. (that is pretty much what the community_tags db table is). However I think you are right that the way the UI is currently designed it is more or less directed towards the public tagging use case.

WildBill’s picture

WildBill commented

According to http://drupal.org/project/flag (haven't actually used it myself) the administrator is able to create as many custom flags as they want, and they can be per-user or global. Or did you mean that the user is not able to create their own flag/tag "on the spot"? That might be true, I'm not sure...

chaps2’s picture

chaps2 commented
Version: 6.x-1.0-beta1 » 6.x-2.x-dev
Priority: Critical » Normal

@drupalina - I agree: having the ability to quickly remove other users' tags without having to edit and re-save the node would be a good thing. However I don't think this should happen on the community tags AJAX form. Trying to include administration functionality on the tagging form would be confusing, clumsy, and make it far too easy to remove a tag by mistake.

What I propose is a "tag admin" tab on the node page which lists all tags, counts, (users) etc and available operations. Operations would include "remove tag" to satisfy this feature request but considering other feature requests may also include things like "ban", "approve" etc. (try and get all those on the AJAX tagging form!)

This is obviously an old issue but still relevant - hopefully there is still some interest...?

chaps2’s picture

chaps2 commented

@wildbill - The flag module can't be used for personal tagging in the way that Community Tags can. @entrigan's use case #2 is well within the scope of this module but could be better supported.

chaps2’s picture

chaps2 commented
Status: Active » Needs work

I have added a "Tag Management" tab to the node page which is visible to any user with "manage tags" permission or node authors with "manage tags on own content" permission. Currently the only operation available is "remove" which asks for confirmation before actually removing all tags from the node for the selected term.

chaps2’s picture

chaps2 commented
Status: Needs work » Fixed

Marking as fixed as the original feature request has been functionally fulfilled, just that tags are "managed" on a separate tab. Also, the new Unitag integration goes some way to preventing bad tags either automatically or via a moderation queue. Admittedly the moderation queue is global and it might be nice to have a per-node moderation queue on the node's "manage tags" tab. But that's another feature request...

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.