Topic: [APPROVED] Making room for a new Zelda character

Posted under Tag Alias and Implication Suggestions

The bulk update request #4784 is active.

mass update rauru -> rauru_(ocarina_of_time)
change category rauru_(ocarina_of_time) (6) -> character
change category rauru_(disambiguation) (0) -> invalid
create implication rauru_(tears_of_the_kingdom) (783) -> tears_of_the_kingdom (2941)

Reason: There are multiple versions of the same character and I'm afraid it might lead to mistagging Currently, I don't see any post under rauru that should be on rauru_(tears_of_the_kingdom), but i reckon it would be best to prevent a problem rather than to having to clean up after it.

Will make another bur with alias rauru -> rauru_(disambiguation) at a later date.

EDIT: The bulk update request #4784 (forum #364902) has been approved by @gattonero2001.

Updated by auto moderator

Watsit

Privileged

You can't update and alias a tag at the same time. They aren't guaranteed to happen sequentially in order, causing some, none, or all posts to be updated to a new tag and the remaining to be aliased.

More importantly, OoT Rauru isn't human, he's an elf/humanoid. Using a species as a character suffix should be avoided when possible too, in case they're drawn as an alternate species like post #566748. Aliasing rauru_(ocarina_of_time) to kaepora_gaebora doesn't seem appropriate either, since they're different names for different forms (and that they're the same character isn't mentioned in-game, only in supplemental material, so many people won't know).

It would make more sense to me to mass update rauru -> rauru_(ocarina_of_time), keep kaepora_gaebora separate, and implicate rauru_(tears_of_the_kingdom) -> tears_of_the_kingdom. Then in a followup BUR, disambiguate and invalidate Rauru.

Updated

  • 1