Skip to main content
replaced http://ux.stackexchange.com/ with https://ux.stackexchange.com/
Source Link

Today, I manually removed the misspelled tag from two separate questions. While this was an easy thing with only two questions having the tag, either making the misspelling a synonym or deleting it and putting it on the blacklist will prevent it from happening again. And it is an easy misspelling to make and a hard one to notice when gazing at the word.

While I changed the tags, I also noticed that there is a tag. While we could make a case that if you nitpick it, can be used for questions which refer to both, and should be reserved to questions which are only about signon, it seems that the users are not nitpicking. They frequently use in combination with either or . When it is used alone, such as in Password field in cleartextPassword field in cleartext, one of the other two would obviously be also appropriate, in this case .

So my second suggestion is to burninate , as its usage shows that it is redundant. The separate words, and , could be created as new tags and be made synonyms of and respectively. Simply making the double tag a synonym does not seem possible, as it is usually applied to questions which refer to only one of the two concepts.

It would make sense to also manually assign either or to questions which have before burninating. I'm extrapolating this to touch 30 to 35 questions. If they are considered too many to bump, maybe at least do it for the 3-4 questions which have no other tag applied.


Update I went and manually edited 7 questions which had no tag at all beside [signup-signon]. I also checked the search syntax and noticed that you can exclude a tag :) so now I know that we have exactly 45 questions left which have [signup-signon] but neither [registration] nor [login]. We could either

  • simply burninate the tag and accept that 45 questions will have inferior tagging
  • gradually edit the 45 questions by hand, so we get only a few bumps per day, then burninate
  • do a big bang edit action and live with the front page being overtaken for a few hours. The initial disruption shouldn't last too long, 45 questions are quickly edited and we get many other bumps from normal activity. But of course, people will start reanswering, so the results will probably linger for days.
  • only manually edit the questions which need instead of . From my experience with the first 7, I expect them to be less than half. Then ask the team if they can automatically replace the tag for the others without bumping.

Which alternative is the best? Or is there a solution I've overlooked?

Today, I manually removed the misspelled tag from two separate questions. While this was an easy thing with only two questions having the tag, either making the misspelling a synonym or deleting it and putting it on the blacklist will prevent it from happening again. And it is an easy misspelling to make and a hard one to notice when gazing at the word.

While I changed the tags, I also noticed that there is a tag. While we could make a case that if you nitpick it, can be used for questions which refer to both, and should be reserved to questions which are only about signon, it seems that the users are not nitpicking. They frequently use in combination with either or . When it is used alone, such as in Password field in cleartext, one of the other two would obviously be also appropriate, in this case .

So my second suggestion is to burninate , as its usage shows that it is redundant. The separate words, and , could be created as new tags and be made synonyms of and respectively. Simply making the double tag a synonym does not seem possible, as it is usually applied to questions which refer to only one of the two concepts.

It would make sense to also manually assign either or to questions which have before burninating. I'm extrapolating this to touch 30 to 35 questions. If they are considered too many to bump, maybe at least do it for the 3-4 questions which have no other tag applied.


Update I went and manually edited 7 questions which had no tag at all beside [signup-signon]. I also checked the search syntax and noticed that you can exclude a tag :) so now I know that we have exactly 45 questions left which have [signup-signon] but neither [registration] nor [login]. We could either

  • simply burninate the tag and accept that 45 questions will have inferior tagging
  • gradually edit the 45 questions by hand, so we get only a few bumps per day, then burninate
  • do a big bang edit action and live with the front page being overtaken for a few hours. The initial disruption shouldn't last too long, 45 questions are quickly edited and we get many other bumps from normal activity. But of course, people will start reanswering, so the results will probably linger for days.
  • only manually edit the questions which need instead of . From my experience with the first 7, I expect them to be less than half. Then ask the team if they can automatically replace the tag for the others without bumping.

Which alternative is the best? Or is there a solution I've overlooked?

Today, I manually removed the misspelled tag from two separate questions. While this was an easy thing with only two questions having the tag, either making the misspelling a synonym or deleting it and putting it on the blacklist will prevent it from happening again. And it is an easy misspelling to make and a hard one to notice when gazing at the word.

While I changed the tags, I also noticed that there is a tag. While we could make a case that if you nitpick it, can be used for questions which refer to both, and should be reserved to questions which are only about signon, it seems that the users are not nitpicking. They frequently use in combination with either or . When it is used alone, such as in Password field in cleartext, one of the other two would obviously be also appropriate, in this case .

So my second suggestion is to burninate , as its usage shows that it is redundant. The separate words, and , could be created as new tags and be made synonyms of and respectively. Simply making the double tag a synonym does not seem possible, as it is usually applied to questions which refer to only one of the two concepts.

It would make sense to also manually assign either or to questions which have before burninating. I'm extrapolating this to touch 30 to 35 questions. If they are considered too many to bump, maybe at least do it for the 3-4 questions which have no other tag applied.


Update I went and manually edited 7 questions which had no tag at all beside [signup-signon]. I also checked the search syntax and noticed that you can exclude a tag :) so now I know that we have exactly 45 questions left which have [signup-signon] but neither [registration] nor [login]. We could either

  • simply burninate the tag and accept that 45 questions will have inferior tagging
  • gradually edit the 45 questions by hand, so we get only a few bumps per day, then burninate
  • do a big bang edit action and live with the front page being overtaken for a few hours. The initial disruption shouldn't last too long, 45 questions are quickly edited and we get many other bumps from normal activity. But of course, people will start reanswering, so the results will probably linger for days.
  • only manually edit the questions which need instead of . From my experience with the first 7, I expect them to be less than half. Then ask the team if they can automatically replace the tag for the others without bumping.

Which alternative is the best? Or is there a solution I've overlooked?

Tweeted twitter.com/#!/StackUX/status/590486334525071360
more numbers, suggestions how to handle the retag
Source Link
Rumi P.
  • 6.3k
  • 11
  • 5

Today, I manually removed the misspelled tag from two separate questions. While this was an easy thing with only two questions having the tag, either making the misspelling a synonym or deleting it and putting it on the blacklist will prevent it from happening again. And it is an easy misspelling to make and a hard one to notice when gazing at the word.

While I changed the tags, I also noticed that there is a tag. While we could make a case that if you nitpick it, can be used for questions which refer to both, and should be reserved to questions which are only about signon, it seems that the users are not nitpicking. They frequently use in combination with either or . When it is used alone, such as in Password field in cleartext, one of the other two would obviously be also appropriate, in this case .

So my second suggestion is to burninate , as its usage shows that it is redundant. The separate words, and , could be created as new tags and be made synonyms of and respectively. Simply making the double tag a synonym does not seem possible, as it is usually applied to questions which refer to only one of the two concepts.

It would make sense to also manually assign either or to questions which have before burninating. I'm extrapolating this to touch 30 to 35 questions. If they are considered too many to bump, maybe at least do it for the 3-4 questions which have no other tag applied.


Update I went and manually edited 7 questions which had no tag at all beside [signup-signon]. I also checked the search syntax and noticed that you can exclude a tag :) so now I know that we have exactly 45 questions left which have [signup-signon] but neither [registration] nor [login]. We could either

  • simply burninate the tag and accept that 45 questions will have inferior tagging
  • gradually edit the 45 questions by hand, so we get only a few bumps per day, then burninate
  • do a big bang edit action and live with the front page being overtaken for a few hours. The initial disruption shouldn't last too long, 45 questions are quickly edited and we get many other bumps from normal activity. But of course, people will start reanswering, so the results will probably linger for days.
  • only manually edit the questions which need instead of . From my experience with the first 7, I expect them to be less than half. Then ask the team if they can automatically replace the tag for the others without bumping.

Which alternative is the best? Or is there a solution I've overlooked?

Today, I manually removed the misspelled tag from two separate questions. While this was an easy thing with only two questions having the tag, either making the misspelling a synonym or deleting it and putting it on the blacklist will prevent it from happening again. And it is an easy misspelling to make and a hard one to notice when gazing at the word.

While I changed the tags, I also noticed that there is a tag. While we could make a case that if you nitpick it, can be used for questions which refer to both, and should be reserved to questions which are only about signon, it seems that the users are not nitpicking. They frequently use in combination with either or . When it is used alone, such as in Password field in cleartext, one of the other two would obviously be also appropriate, in this case .

So my second suggestion is to burninate , as its usage shows that it is redundant. The separate words, and , could be created as new tags and be made synonyms of and respectively. Simply making the double tag a synonym does not seem possible, as it is usually applied to questions which refer to only one of the two concepts.

It would make sense to also manually assign either or to questions which have before burninating. I'm extrapolating this to touch 30 to 35 questions. If they are considered too many to bump, maybe at least do it for the 3-4 questions which have no other tag applied.

Today, I manually removed the misspelled tag from two separate questions. While this was an easy thing with only two questions having the tag, either making the misspelling a synonym or deleting it and putting it on the blacklist will prevent it from happening again. And it is an easy misspelling to make and a hard one to notice when gazing at the word.

While I changed the tags, I also noticed that there is a tag. While we could make a case that if you nitpick it, can be used for questions which refer to both, and should be reserved to questions which are only about signon, it seems that the users are not nitpicking. They frequently use in combination with either or . When it is used alone, such as in Password field in cleartext, one of the other two would obviously be also appropriate, in this case .

So my second suggestion is to burninate , as its usage shows that it is redundant. The separate words, and , could be created as new tags and be made synonyms of and respectively. Simply making the double tag a synonym does not seem possible, as it is usually applied to questions which refer to only one of the two concepts.

It would make sense to also manually assign either or to questions which have before burninating. I'm extrapolating this to touch 30 to 35 questions. If they are considered too many to bump, maybe at least do it for the 3-4 questions which have no other tag applied.


Update I went and manually edited 7 questions which had no tag at all beside [signup-signon]. I also checked the search syntax and noticed that you can exclude a tag :) so now I know that we have exactly 45 questions left which have [signup-signon] but neither [registration] nor [login]. We could either

  • simply burninate the tag and accept that 45 questions will have inferior tagging
  • gradually edit the 45 questions by hand, so we get only a few bumps per day, then burninate
  • do a big bang edit action and live with the front page being overtaken for a few hours. The initial disruption shouldn't last too long, 45 questions are quickly edited and we get many other bumps from normal activity. But of course, people will start reanswering, so the results will probably linger for days.
  • only manually edit the questions which need instead of . From my experience with the first 7, I expect them to be less than half. Then ask the team if they can automatically replace the tag for the others without bumping.

Which alternative is the best? Or is there a solution I've overlooked?

added suggestion for manually assigning missing tags before burninating
Source Link
Rumi P.
  • 6.3k
  • 11
  • 5

Today, I manually removed the misspelled tag from two separate questions. While this was an easy thing with only two questions having the tag, either making the misspelling a synonym or deleting it and putting it on the blacklist will prevent it from happening again. And it is an easy misspelling to make and a hard one to notice when gazing at the word.

While I changed the tags, I also noticed that there is a tag. While we could make a case that if you nitpick it, can be used for questions which refer to both, and should be reserved to questions which are only about signon, it seems that the users are not nitpicking. They frequently use in combination with either or . When it is used alone, such as in Password field in cleartext, one of the other two would obviously be also appropriate, in this case .

So my second suggestion is to burninate , as its usage shows that it is redundant. The separate words, and , could be created as new tags and be made synonyms of and respectively. Simply making the double tag a synonym does not seem possible, as it is usually applied to questions which refer to only one of the two concepts.

It would make sense to also manually assign either or to questions which have before burninating. I'm extrapolating this to touch 30 to 35 questions. If they are considered too many to bump, maybe at least do it for the 3-4 questions which have no other tag applied.

Today, I manually removed the misspelled tag from two separate questions. While this was an easy thing with only two questions having the tag, either making the misspelling a synonym or deleting it and putting it on the blacklist will prevent it from happening again. And it is an easy misspelling to make and a hard one to notice when gazing at the word.

While I changed the tags, I also noticed that there is a tag. While we could make a case that if you nitpick it, can be used for questions which refer to both, and should be reserved to questions which are only about signon, it seems that the users are not nitpicking. They frequently use in combination with either or . When it is used alone, such as in Password field in cleartext, one of the other two would obviously be also appropriate, in this case .

So my second suggestion is to burninate , as its usage shows that it is redundant. The separate words, and , could be created as new tags and be made synonyms of and respectively. Simply making the double tag a synonym does not seem possible, as it is usually applied to questions which refer to only one of the two concepts.

Today, I manually removed the misspelled tag from two separate questions. While this was an easy thing with only two questions having the tag, either making the misspelling a synonym or deleting it and putting it on the blacklist will prevent it from happening again. And it is an easy misspelling to make and a hard one to notice when gazing at the word.

While I changed the tags, I also noticed that there is a tag. While we could make a case that if you nitpick it, can be used for questions which refer to both, and should be reserved to questions which are only about signon, it seems that the users are not nitpicking. They frequently use in combination with either or . When it is used alone, such as in Password field in cleartext, one of the other two would obviously be also appropriate, in this case .

So my second suggestion is to burninate , as its usage shows that it is redundant. The separate words, and , could be created as new tags and be made synonyms of and respectively. Simply making the double tag a synonym does not seem possible, as it is usually applied to questions which refer to only one of the two concepts.

It would make sense to also manually assign either or to questions which have before burninating. I'm extrapolating this to touch 30 to 35 questions. If they are considered too many to bump, maybe at least do it for the 3-4 questions which have no other tag applied.

Source Link
Rumi P.
  • 6.3k
  • 11
  • 5
Loading