Posted under Tags
remove implication shantae_(cosplay) -> shantae
Seems to be an alias/implication that I'm not seeing; however I can't seem to get rid of the shantae tag.
EDIT: This bulk update request has been rejected because it was not approved within 60 days.
EDIT: The bulk update request #1065 (forum #126156) has been rejected by @DanbooruBot.
Updated by DanbooruBot
It's not a mistake, tags like those are automatically applied if they see anything *_(cosplay). You should probably tag that shantae_(character)_(cosplay) instead.
More info in cosplay.
Mikaeri said:
It's not a mistake, tags like those are automatically applied if they see anything *_(cosplay). You should probably tag that shantae_(character)_(cosplay) instead.
More info in cosplay.
Well then we have a problem, because this messes with single-word characters where the name isn't exclusive.
Do you have any examples of such characters? If a *_(cosplay) tag is ambiguous and could refer to several characters, then surely it should be made unambiguous. Ambiguity would cause problems regardless of autotagging.
If the problem is that shantae_(character)_(cosplay) is too long, then just change the character tag to shantae and leave shantae_(series) as the qualified tag. We don't need to qualify both tags.
When a character and a series share the same name the series gets the base tag, the character gets tagged x_(character) so cosplays would be x_(character)_(cosplay) it's been this way for years.
Looks like brokeneagle is running a script to autoadd the base tags but clearly it isn't foolproof. This is part of why I moderated the cosplay tags manually for 4 years until I burned out on it.
I'm not sure why Shantae is qualified as (series) in this particular case. Oh, this is an odd one, shantae should probably be base tag as character in this case.
Log said:
When a character and a series share the same name the series gets the base tag, the character gets tagged x_(character) so cosplays would be x_(character)_(cosplay) it's been this way for years.
Looks like brokeneagle is running a script to autoadd the base tags but clearly it isn't foolproof. This is part of why I moderated the cosplay tags manually for 4 years until I burned out on it.
I'm not sure why Shantae is qualified as (series) in this particular case.Oh, this is an odd one, shantae should probably be base tag as character in this case.
http://danbooru.donmai.us/tags?search[name_matches]=*_(character)_(cosplay).
Seems pretty common enough.
For now, I migrated all of the shantae_(cosplay) tagged posts to shantae_(character)_(cosplay), and removed the superfluous shantae tags...
The *_(cosplay) autotag was a response to an enormous amount of pictures missing the cosplay tag, which significantly hampered certain tag gardening efforts (and searches in general), such as topic #13313, due to the limitations of danbooru's wildcard search.
The discussion was done in topic #13367, and nobody objected at the time.
Not exactly a bug, but I have encountered an unthought of situation in regards to the *_(cosplay) tag. Whenever a character tag gets renamed, either manually or through an alias, it does not rename the corresponding *_(cosplay) tag.
In either case, it adds a tag that should not be added whenever the post gets updated. In the latter case, it adds the consequent to an alias, a tag that can not otherwise normally be added, and that can only be searched with with the raw addon.
Example of this: http://danbooru.donmai.us/posts?tags=bruno_bucciarati&raw=true
Perhaps it could be automated? Automatically create a antecedent_(cosplay) -> consequent_(cosplay) update job for aliases/mass updates if the antecedent is a character tag? (or make it a checkbox, perhaps, given the code seems to not look at the tag category for BURs)
Updated
The bulk update request #1065 (forum #126156) has been rejected by @DanbooruBot.
