The bulk update request #1961 is active.

create alias unimpressive (0) -> unimpressive_(disambiguation) (0)
change category unimpressive_(disambiguation) (0) -> invalid

Reason: So, there's this artist called unimpressive. They currently have two tags, that one and unimpressive_(artist). The former tag has never had an issue with people tagging it for its literal meaning, with every instance of its removal being a replacement with the suffixed form.

With this in mind, I made an alias request to automatically remove the suffix. It was rejected on the grounds that unimpressive might, at some theoretical point in the future, be considered ambiguous. (I might add that the staff member who rejected it also happens to be the main uploader of Unimpressive's art, and exclusively uses the non-suffixed form to do so, so clearly she doesn't consider it ambiguous at all.)

So now there's this BUR. If this gets rejected, I guess I'll try the final option of aliasing the base tag to the suffixed form, but that to me seems like it would entirely defeat the point of the suffix in the first place.

EDIT: The bulk update request #1961 (forum #326326) has failed: Error: Antecedent name has already been taken (create alias unimpressive -> unimpressive_(disambiguation))

EDIT: The bulk update request #1961 (forum #326326) has been approved by @bitWolfy.

The bulk update request #1961 (forum #326326) has failed: Error: Antecedent name has already been taken (create alias unimpressive -> unimpressive_(disambiguation))

The bulk update request #1961 (forum #326326) has been approved by @bitWolfy.

Category needs an update again--seems like categories just like to change before the alias.

furrin_gok said:
Category needs an update again--seems like categories just like to change before the alias.

This is ridiculous.

I approved the BUR, went to check if the category was correct – and it was.
Then it changed back a minute later.

Tags in the invalid category should not get their category imported by an alias, simple as that.

bitwolfy said:
Tags in the invalid category should not get their category imported by an alias, simple as that.

I'm honestly not sure why a category would need to be imported by an alias at all, apart from when it's a general tag or being newly created by the alias.

If the target already has a category set it's most likely the correct one, since it's the primary tag. It feels very weird to import the category of the tag that's being aliased away to the target.