Rename the "stump" tag

I miss the show so much

We have two often-used stump tags:

Guess which one people often use when they mean the other? It’s not fun to clean up and it’s been going on for years now.

I already asked about this here and proposed that stump is renamed to either “stump (amputee)” or “stump (limb)”, and received positive feedback. But which one shall be the new name for the amputated limb tag? I’m personally okay with either.

But there’s a problem. As far as I understand it, the old tag cannot be aliased into the new, because then the problem remains as people will continue to use “stump” when they meant “tree stump” and the system adds the wrong tag. It has to be explicit. So when someone starts typing “stump”, the autocomplete will show these:

stump (amputee) (or stump (limb))
tree stump

This forces the user to choose the right one. The plain “stump” tag does not exist anymore.

(The renamed tag should also have a description. In fact, both tags should have a description.)

Posted 1 months ago Report

Link Quote Reply

LightningBolt

Senior Moderator

Undead inside

@JP
Stump can just be aliased into the new name and then IT can be aliased into TREE stump. Or would that still not help?

Posted 1 months ago Report

Link Quote Reply

Background Pony #08A9

@JP

either “stump (amputee)” or “stump (limb)” […] But which one shall be the new name for the amputated limb tag?

It depends whether the tag should include birth defects, right? Presently, “stump” implies “amputee” so I guess not.
(Plus, trees have limbs. ;P)

But there’s a problem. As far as I understand it, the old tag cannot be aliased into the new, because then the problem remains as people will continue to use “stump” when they meant “tree stump” and the system adds the wrong tag. It has to be explicit. So when someone starts typing “stump”, the autocomplete will show these:

stump (amputee) (or stump (limb))
tree stump

This forces the user to choose the right one. The plain “stump” tag does not exist anymore.

If it is aliased, the autocomplete dropdown will still only show “stump (amputee)” and “tree stump” - that’s not a problem it would cause. You’re correct that for someone who types “stump” and absent-mindedly completes the tag with comma or enter, it would automatically replace the tag with “stump (amputee)” which obscures that a mistake happened.

Actually, that brings up that “tree stump” is NOT in the autocomplete list if one starts by typing “stump”. It would need an alias added that begins with “stump” - for example, “stump (tree)” could be created and then aliased into “tree stump” to make that happen.

Moreover, I wonder if a new tag paradigm ought to be formulated for tags that someone might type blindly (not looking at the autocomplete list, or skipping it altogether due to submitting via a 3rd party tool like PostyBirb). In this case, “stump” would get aliased to something like “stump (ambiguous tag)” or more anviliciously “stump (use a different tag instead of this)”, which in turn would imply a new error-classified tag “ambiguous tag”.

Posted 1 months ago Report

Link Quote Reply

I miss the show so much

@LightningBolt
@Background Pony #08A9
Yeah, it’s obvious to me now that I didn’t think enough about the implication problem. It’s not really a problem.

As long as it’s obvious which kind of a stump gets added if you just type “stump”, I’m okay with it. But let’s please rename the amputated limb stump tag.

Posted 1 months ago Report

Link Quote Reply

LightningBolt