medusa_(fate) aggregation

Posted under Tags

Arcana55

BUR #5533 has been rejected.

create implication gorgon_(fate) -> medusa_(fate)_(all)
create implication medusa_(rider)_(fate) -> medusa_(fate)_(all)
create implication medusa_(lancer)_(fate) -> medusa_(fate)_(all)

Aliases gorgon_(fate) to medusa_(avenger)_(fate), for consistency with medusa_(rider) and medusa_(lancer). Also adds implications to create a catchall tag for all three forms.

EDIT: The consensus seems to be to retain the gorgon name. The BUR has been amended to eliminate the alias and to implicate gorgon_(fate) to medusa_(fate)_(all) instead.

Updated by Arcana55

Reply
DeusExCalamus Veraducks Kodoku247 Bandog444 Astolfo uzheng MyrMindservant Talulah
Veraducks

I agree with the whole thing, but I'll raise one minor point:
With her in-game name being Gorgon and a community nickname being Medusa Gorgon, should it be tagged medusa_(gorgon)_(fate)?

I think either way is good, though.

Reply
Astolfo

I disagree with changing Gorgon and believe we should stick to the way characters are referred to rather than change it for consistency. Her name in that form is Gorgon, implication or not it should be Gorgon. Not Medusa (Avenger) or Medusa (Gorgon).

Reply
evazion

I'm not keen on adding more _(all) tags. I'd rather work towards getting rid of them. I would prefer using Medusa (Fate) instead of Medusa (Fate) (all) as the umbrella tag.

The only reason we have _(all) tags is that for some reason, we decided to use Artoria Pendragon (all) instead of Artoria Pendragon (Fate) for Artoria's umbrella tag. Then it became a meme to do the same for other characters.

The problem with _(all) tags is that we get tags like Nero Claudius (Fate) (all) and Nero Claudius (Fate) existing at the same time. This is confusing, it's not obvious what the difference is. If you saw Nero Claudius (Fate) by itself you would think it's the most generic Nero tag. But it's not, it's for one specific version of Nero. The _(all) tag is somehow more generic than the generic tag.

Reply
Veraducks

evazion said:
The problem with _(all) tags is that we get tags like Nero Claudius (Fate) (all) and Nero Claudius (Fate) existing at the same time. This is confusing, it's not obvious what the difference is. If you saw Nero Claudius (Fate) by itself you would think it's the most generic Nero tag. But it's not, it's for one specific version of Nero. The _(all) tag is somehow more generic than the generic tag.

In this particular instance, you could axe the _(all) and get the same effect given that the "base" Medusa already has the (rider) qualifier.

Reply
Arcana55

evazion said:

The problem with _(all) tags is that we get tags like Nero Claudius (Fate) (all) and Nero Claudius (Fate) existing at the same time. This is confusing, it's not obvious what the difference is. If you saw Nero Claudius (Fate) by itself you would think it's the most generic Nero tag. But it's not, it's for one specific version of Nero. The _(all) tag is somehow more generic than the generic tag.

That isn't completely Danbooru's fault though. For starters, you have the practice of referring to servants by class, so that each time a story about a new grail war came out there was a whole new different set of characters called the same things. Then on top of that, the whole Fateverse starts spawning variations of the same base character, with Arturia practically undergoing asexual reproduction at this point. Things were bound to get confusing eventually.

Personally, purely from a visual standpoint I think having multiple disambiguation parentheses just looks bad. I would have preferred medusa_(rider) and medusa_(lancer) to medusa_(rider)_(fate) and medusa_(lancer)_(fate), had it been up to me. Likewise, I have no problems with using medusa_(fate) as the parent tag instead of medusa_(fate)_(all). However, as I alluded to before, consistency is my highest goal. So naturally I followed precedent.

Reply
evazion

Veradux said:

In this particular instance, you could axe the _(all) and get the same effect given that the "base" Medusa already has the (rider) qualifier.

That's what I'm saying, there's no reason to use "character_(fate)_(all)" when we could just do "character_(fate)". The standard should be "character_(fate)" for the umbrella tag and "character_(class)_(fate)" for specific versions.

Reply
1