meta.SE automatically suggests tags (pretty accurately, kudos!) (at least it just worked half an hour ago when I submitted a bug report. Curiously for this feature request here it didn't work for me.)

Why is this feature not available on other sites, e.g. aviation.SE?

  • It's incredibly helpful and a huge time-saver.

  • I have seen many inadequately tagged questions (at least on aviation.SE), because users are not willing to spend much time looking for the right tags. This feature would enhance cataloging of questions greatly.

I submit this hereby as a request for enhancement.

  • I don't understand why people downvote a feature unless the feature would be a nuisance for them (which in this case is not possible). If it's just something they don't need or use, then just don't use it, but why would you want to prevent others from using it ? – summerrain Dec 14 '18 at 17:57
  • 2
    @summerrain Features cost time of SE developers, and should be worth it. – πάντα ῥεῖ Dec 14 '18 at 18:04
  • 1
    not in this case. The feature is already working. It just needs to be greenlighted for other sites. – summerrain Dec 14 '18 at 18:05
  • 1
    Which still requires time from developers. It's not like it's an instant. Nor does it account for potential issues with porting it to other sites, like architecture changes, or aspects not accounted for. Engineering is not an easy process. – fbueckert Dec 14 '18 at 18:07
  • are you a dev or guessing ? – summerrain Dec 14 '18 at 18:09
  • 1
    I am a dev. I am not an SE dev. I'm pointing out that estimating effort is hard enough when you actually wrote and/or maintain the code. Someone who's not at all familiar with it trying to estimate effort is going to be entirely inaccurate. – fbueckert Dec 14 '18 at 18:16
  • Point taken. Can we agree then, that it might be lots of work or hardly any and that neither of us knows for sure. From my point of view, it's rather administrative greenlighting than code work, but I respect your different PoV. – summerrain Dec 14 '18 at 18:20
  • 2
    There's nothing wrong with making a feature request. But dismissing those against it because it takes devs away from other work, because it, "wouldn't be any work", is a false argument. Disagreeing with a feature request because they believe it would take work away from what they believe is more important is a perfectly valid argument. – fbueckert Dec 14 '18 at 18:24
  • 1
    In case it would actually require dev work, for which there is no evidence. – summerrain Dec 14 '18 at 18:26

I disagree with this feature request.

According to balpha, suggested tags are chosen by a "a somewhat-but-not-quite-bayesian classifier based on the words in text and title, trained on older questions."

The reasons are laid out in an older post about suggested tags:

A minimum of around 20k questions are required for accurate results

There is no substitute for material to learn from, so it can't be rolled out to all sites

For each individual stack, you'd have to pick at least 20,000 (old) questions to train the classifier. If you do not have enough questions, it would not be accurate enough.

An earlier feature request for Stack Overflow got the following reply from Tim Post:

I'd be all for it, as long as the system didn't suggest tags that we are working desperately to get rid of.

The conclusion is

  • It's too much work for the development team. The time should be spend more wisely.
  • Many of the smaller sites couldn't benefit from it anyway.
  • Auto-suggeting inappropriate or deprecated tags would cause more work for editors.
  • aviation.SE has 58k questions. And if the feature already exists and is working, it wouldn't be any work. – summerrain Dec 14 '18 at 18:00
  • 1
    re: "I'd be all for it, as long as the system didn't suggest tags that we are working desperately to get rid of." sorry, but that is the easiest thing to solve. Just blacklist unwanted tags. – summerrain Dec 14 '18 at 18:11
  • 2
    There's currently no way to do that without a CM interviening, so blacklisting is hardly simple. – Journeyman Geek Dec 14 '18 at 18:18
  • 1
    re: "It's too much work for the development team." That's purely speculation. – summerrain Dec 14 '18 at 18:22

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .