Last modified: 2014-03-02 18:36:11 UTC
Currently there's no way to remove tags from edits or actions. If an AbuseFilter filter calls a legitimate edit (spam) or (possible civility issue) or something and it really isn't, there needs to be a way to remove the tag from the edit or action. Especially given that the tags are permanent.
Tags are permanent? Surely they're only needed in recentchanges table.
A way to directly create and delete tags would considerably improve the tagging interface. It would allow to choose the wanted tag in a scroll-down menu among existing tags in recent changes, histories, etc and the abuse filter interface, which is much preferable than having to type its name (and has negative effects in cases of mistakes or name changes, see bug 18908). Also, a tag should not be deletable if it is called by an abuse filter. I would agree that there is no need for tags to be visible after 30 days. For examples, the following tags are no longer active on enwiki, and can be deleted safely: "ref group removal" (1763 tagged changes), "removal of references" (460), "personal attack" (170), "possible conflict of interest spam" (259), "spam" (153), "link vandalism" (2)
(In reply to comment #2) > A way to directly create and delete tags would considerably improve the tagging > interface. > > It would allow to choose the wanted tag in a scroll-down menu among existing > tags in recent changes, histories, etc and the abuse filter interface, which is > much preferable than having to type its name (and has negative effects in cases > of mistakes or name changes, see bug 18908). > > Also, a tag should not be deletable if it is called by an abuse filter. > > I would agree that there is no need for tags to be visible after 30 days. > > For examples, the following tags are no longer active on enwiki, and can be > deleted safely: > > "ref group removal" (1763 tagged changes), "removal of references" (460), > "personal attack" (170), "possible conflict of interest spam" (259), "spam" > (153), "link vandalism" (2) > They can't be deleted, because they're applied to edits. When they are removed from all edits, they will disappear automatically.
(Batch change) These are low-priority miniprojects that I can mop up at some point when I'm doing general code work as opposed to working on a specific projects.
Un-marking this as an enhancement. I don't see how it's an enhancement to have the ability to remove tags.
[Expanding this to "add / remove tags" instead of just "remove tags". This seems very much like part of one feature.]
(In reply to comment #6) > [Expanding this to "add / remove tags" instead of just "remove tags". This > seems very much like part of one feature.] That might help with bug 28213.
Of note: there was a now-abandoned gerrit patch aiming to add an API module for this: https://gerrit.wikimedia.org/r/#/c/64650/
I abandoned that patch primarily because it would require writing multiple API modules (since our current API is terribly designed and is not RESTful), and I didn't have the time to do something like that. If you were to steal the ChangeTags.php part of my patch and then just write some API modules, making tags editable would be trivial.
I read all the comments and description, and I'm not sure that what I have in mind is included: being able to add a few tags directly when editing a page through the API. That would allow for example some tools to tag modifications made with them (like what Visual Editor is doing): I'd definitely use this in WPCleaner [1] if it was available. This allows to check on what a given tool is doing even if it's a multi user tool. Other example: when fixing specific errors for Check Wiki project [2], tools could add a tag for each kind of error that was fixed. [1] http://en.wikipedia.org/wiki/Wikipedia:WPCleaner [2] http://en.wikipedia.org/wiki/Wikipedia:WikiProject_Check_Wikipedia
(In reply to comment #10) > That would allow for example some tools to tag modifications made with them > (like what Visual Editor is doing): I'd definitely use this in WPCleaner [1] > if > it was available. This allows to check on what a given tool is doing even if > it's a multi user tool. OAuth will do this automatically, for tools that authenticate using OAuth rather than logging in with the user's username and password. > Other example: when fixing specific errors for Check Wiki project [2], tools > could add a tag for each kind of error that was fixed. If anyone picks up Tyler's patch along these lines, please read the comments on that patch. In particular, I'd suggest using a MediaWiki-namespace page so wiki admins can manage the allowed tags, rather than requiring that MediaWiki's configuration be updated for every change.
(In reply to NicoV from comment #10) See also: https://bugzilla.wikimedia.org/show_bug.cgi?id=4718
