Not sure if this re-tag request needs to get resurrected from the original "Great Tagging Reog" discussion, but as someone who still eats, sleeps, and breathes Classic ASP (well, Classic ASP pays for the food and the roof) its bothered me that there's an asp and asp-classic tag.

While I can understand that some of the questions (~20% based on sloppy math and random sampling) are from people too lazy to finish ASP with a .NET, it would probably help to sort those out from the Classic questions.

Is there a way to selectively re-tag? i.e. if it has other tags like vbscript change it to asp-classic and if it has other tags like c# change it to asp.net and then see how many are left.

I have insomnia, and may just undertake some manual work, but 531 questions is likely to cure my sleep issues before I finish...

Thoughts?

Edit

Just bringing this back up as the asp tag is fairly useless since it doesn't differentiate between classic and .net. Or is this something that's going to have to wait until there's a blacklist for tags?

This question appears to be off-topic. The users who voted to close gave this specific reason:

"This question pertains only to a specific site in the Stack Exchange Network. Questions on Meta Stack Exchange should pertain to our network or software that drives it as a whole, within the guidelines defined in the help center. You should ask this question on the meta site where your concern originated." – psubsee2003, Martijn Pieters, Danubian Sailor, Aziz Shaikh, Gilles

Not that many as I was taking my time. I read the posts to make sure I didn't mis-tag, and I was watching TV so my attention tended to wander... especially on some of the more convoluted, poorly worded questions. Made me wish I had the rep to help 'em out.
–
AnonJrOct 22 '09 at 13:34

Certainly, once all questions are moved out of there it should be blacklisted, because it's completely ambiguous.

I was working on this just now, and it seems that most of the questions tagged [asp] deal with Classic ASP topics.

Now, since this question was originally posted, the [asp] tag has ballooned quite a bit to 859 questions. I cut that down to 773 by eliminating the combination of [asp] + [.net], mostly into [asp.net] (some of the questions actually dealt with Classic ASP topics).

After that, I did a search for [asp]-[asp.net]-[c#]-[asp.net-mvc], which resulted in 600 questions. That means by eliminating the ~173 questions (roughly 2x what I just did) that don't deal with Classic ASP, and then manually going through the remaining 600 questions to filter out anything not Classic ASP, then a mass rename can proceed. I hope my assumption (3rd paragraph) actually holds true!

Hi all, I realise classic asp is old news to most people, but still used by some :)

There appears to be 685 questions tagged 'asp' and 875 questions tagged 'asp-classic', could these be merged to asp-classic? I recognise that some tagged asp may actually be referring to asp.net and need to be merged with that tag.

Will this kind of clean-up need to be done every six months, or is there a feature on the way to prevent this kind of issue?

I hope not... especially since it was never finished the first time. A fair number of the questions tagged asp were in fact asp.net (and in some cases, tagged with both) - and that's just the start of the fun.
–
AnonJrFeb 15 '10 at 21:21

Is there a way to blacklist a tag such as 'asp' because it is too vague and open to being mis-interpreted? I can only imagine this problem is going to grow bigger as the site grows bigger.
–
akashicFeb 16 '10 at 16:14