The bulk update request #3997 is active.

remove alias badges (1) -> badge (3315)
mass update con_badge -> character_badge_(artwork)
mass update conbadge -> character_badge_(artwork)
mass update name_badge -> character_badge_(artwork)
change category character_badge_(artwork) (675) -> meta
create alias id_badge (4) -> id_card (534)
mass update id -> id_card
mass update identification -> id_card
create implication pin_button (693) -> pin_accessory (810)
create implication pin_accessory (810) -> accessory (143617)

Reason: The badge tag is a mess of pin type badges and furry con badge art. Name_badge is almost exclusively used for furry conbadge art, but not quite. That tag's name is vague enough that I don't think it should be the furry conbadge tag, when regular ID badges such as the one linked also exist.

My proposed idea is:

• character_badge_(artwork), a meta tag, for furry con character badge art.
• character_badge_(object) for furry con character badges depicted in the scene like post #2968952
• id_card includes in-scene, professional looking lanyard badges like post #3809961 as well as other ID cards
• pin_button, which already exists, for in-scene pin badges like post #3809639. It should imply pin_accessory, which I think should imply accessory?
• police_badge, already exists, for police badges
• merit_badge, which exists but is undertagged, for (typically iron-on) merit badges used in contexts like scouting organizations.
• event_badge for official con badges (the kind the con gives you) depicted in-scene

IMO identification and id are vague enough that they shouldn't be aliased, just updated.
Badge will need a lot of manual cleanup after its disambiguation - tagme.dev will be good for this. I'll need to clean con_badge and name_badge a little before the mass update, I just didn't want to risk tag vandalism in case this doesn't end up getting approved.

I would very much appreciate feedback on this! I know it's gonna need changes before it could be approved, this is just what I came up so far.

EDIT: The bulk update request #3997 (forum #355902) has been approved by @spe.

I can't find what's blocking transitive relationships :/ there was one badges -> badge alias but that was approved years ago.

You cannot alias a tag to something until its aliases are removed. You need to undo the aliases first.

As for this idea, sorting the amount of stuff in the badge tag will be a lot of work. It might be worth it as long as every concept can be sorted somewhere.

thevileone said:
You cannot alias a tag to something until its aliases are removed. You need to undo the aliases first.

Whoops! Fixed, thanks

As for this idea, sorting the amount of stuff in the badge tag will be a lot of work. It might be worth it as long as every concept can be sorted somewhere.

For sure - e6 tagging is practically one of my hobbies at this point though haha, I ain't scared

cloudpie said:
mass update name_badge -> character_badge_(artwork)

There are a number of posts that depict a name badge, but aren't themselves one:
post #3700052 post #3710099

And some that are just the character's name with a depiction of the character, and no indication it's someone's persona or for a real-life badge:
post #3130195 post #2067320

A name badge can also just have a name, with no character (though this would fall under the first examples, depicting one in art rather than the image being one itself).

watsit said:
There are a number of posts that depict a name badge, but aren't themselves one:
post #3700052 post #3710099

Yes, it's a very small amount of them though, currently the vast majority of name_badge (as far as I saw) is character badges. I'll clean those out manually if people like this BUR or if a different solution to the badge issue is approved. I just didn't want to tag vandalize in case this isn't what ends up happening - I wanted to get people's opinions first

And some that are just the character's name with a depiction of the character, and no indication it's someone's persona or for a real-life badge:
post #3130195 post #2067320

These would probably not belong in the character badge tag, I'll clean 'em out if this looks like it's gonna get approved

A name badge can also just have a name, with no character (though this would fall under the first examples, depicting one in art rather than the image being one itself).

I think this would probably fall under either identification_badge or name_tag depending on the style. No character means it's not a character badge. I'm not saying to alias name badge to character badge, just mass update it once to get all those character badge images into their new tag

There are no rules against two character tags. You shouldn't be aliasing tags to invalid anyways. We have an invalid category.

thevileone said:
There are no rules against two character tags.

I checked it out and you're right, tf is even aliased to transformation. Not sure why I thought that was the case, I'm fixing it though 👍

You shouldn't be aliasing tags to invalid anyways. We have an invalid category.

Just FYI Kira in the discord said:

To expand a little on invalid category VS aliases. The items that are going to stay aliased are the ones that should never be allowed to show up on posts to avoid encouraging their use. Things like slurs, really common typos that cannot convey information, and otherwise things that shouldn't be searchable, like cute. People would abuse that it still worked for search if not aliased away.
The category is for tags that convey intent and require actionable cleanup.
So there is purpose to the alias and the category isn't a complete replacement for it. Nor should all aliases be converted to categories.

So that was my reasoning, I assumed two letter tags would be included in that since for some reason I thought they weren't allowed for being likely to come up as typos, but since they are allowed you're totally right and I'll change it

• Changed identification_card to id_card, don't know what I was thinking with that one
• Added event_badge for official con badges (the kind the con gives you) depicted in-scene

Working on cleanup
Edit: Should be all clean and ready for the mass updates

The bulk update request #3997 (forum #355902) has been approved by @spe.

The bulk update request #9087 is pending approval.

create alias con_badge (0) -> badge_(disambiguation) (0)
create alias badge (3315) -> badge_(disambiguation) (0)
create alias badges (1) -> badge_(disambiguation) (0)
create alias conbadge (0) -> badge_(disambiguation) (0)
create alias name_badge (0) -> badge_(disambiguation) (0)
create alias id (0) -> id_(disambiguation) (0)
change category id_(disambiguation) (0) -> invalid

Reason: Admins will be badgered until this BUR is approved

Also any ideas on what to do with id? it's been mass updated in the BUR above but will that be enough?

Edit: disambiguating the tag

snpthecat said:
Also any ideas on what to do with id? it's been mass updated in the BUR above but will that be enough?

Disambiguate. It can refer to an ID badge (either as an in-image object, or the image itself being a name badge), a game developer, or the part of the psyche "that is completely unconscious and is the source of psychic energy derived from instinctual needs and drives" (which can be depicted as a primeval demonic entity that's in everyone's subconscious, that typically wants to fulfill the three "F"s: feed, fight, and fuck).

Uh oh, now we have explorer_badge implying badge. I can think of 2 options here:

1) Keep badge as an umbrella tag and imply various things to it. Perhaps just police_badge, merit_badge, and event_badge, but maybe also character_badge_(object)?
Pros: better to avoid disambiguations when possible
Cons: the word "badge" can refer to so many different items... In the UK it means pin_buttons too. Do we include those?

2) Go ahead with disambiguating badge, and have explorer_badge only imply pokemon_mystery_dungeon

Thoughts?

there's also verified_badge

but that could probably be aliased to twitter_verification

but there's also only 7 posts so ¯\_ (ツ)_/¯

The bulk update request #9298 is pending approval.

remove implication explorer_badge (97) -> badge (3315)

Reason: i'm leaning towards option B