create implication yuuki_yuuna_wa_yuusha_de_aru -> yuusha_de_aru
create implication washio_sumi_wa_yuusha_de_aru -> yuusha_de_aru
create implication nogi_wakaba_wa_yuusha_de_aru -> yuusha_de_aru
Posted under Tags
create implication yuuki_yuuna_wa_yuusha_de_aru -> yuusha_de_aru
create implication washio_sumi_wa_yuusha_de_aru -> yuusha_de_aru
create implication nogi_wakaba_wa_yuusha_de_aru -> yuusha_de_aru
create implication kusunoki_mebuki_wa_yuusha_de_aru -> yuusha_de_aru
Same series.
The bulk update request #1201 has been approved.
Updated by DanbooruBot
The bulk update request #1201 has been approved.
create implication yuuki_yuuna_wa_yuusha_de_aru:_hanayui_no_kirameki -> yuuki_yuuna_wa_yuusha_de_aru
Part of the Yuusha de Aru series, but is a subtitle of Yuuki Yuuna.
EDIT: This bulk update request has been rejected because it was not approved within 60 days.
EDIT: The bulk update request #1235 (forum #133854) has been rejected by @DanbooruBot.
Updated by DanbooruBot
G-SANtos said:
create implication yuuki_yuuna_wa_yuusha_de_aru:_hanayui_no_kirameki -> yuuki_yuuna_wa_yuusha_de_aru
Part of the Yuusha de Aru series, but is a subtitle of Yuuki Yuuna.
Anyone?
G-SANtos said:
create implication yuuki_yuuna_wa_yuusha_de_aru:_hanayui_no_kirameki -> yuuki_yuuna_wa_yuusha_de_aru
Part of the Yuusha de Aru series, but is a subtitle of Yuuki Yuuna.
@NWF_Renim Please?
NWF_Renim said:
I'd reject the implication right now because the tag only has 4 posts under it. If there were more posts under the tag it would be fine, but as it currently stands it's not enough to justify an implication.
But it's part of the same franchise. I thought those were automatically accepted. The Kusunoki Mebuki implication was accepted with only 1 post, and there's currently only 2 of them.
G-SANtos said:
But it's part of the same franchise. I thought those were automatically accepted. The Kusunoki Mebuki implication was accepted with only 1 post, and there's currently only 2 of them.
If the tag's population is really low and there isn't any reason to expect significant usage of the tag (in this case it's been 4 months since the last upload), then we typically just let it be manually tagged until a time when it reaches a point where it'd justify giving it an implication.
Not sure why The Kusunoki Mebuki implication was approved, but we're normally not supposed to approve such implications.
NWF_Renim said:
If the tag's population is really low and there isn't any reason to expect significant usage of the tag (in this case it's been 4 months since the last upload), then we typically just let it be manually tagged until a time when it reaches a point where it'd justify giving it an implication.
Not sure why The Kusunoki Mebuki implication was approved, but we're normally not supposed to approve such implications.
Because it's part of the same franchise. I once requested digimon adventure tri. to have implication to digimon when there were very few images and it was accepted. Actually, I think I'm the one who created the digimon_adventure_tri. tag.
Furthermore, every time I request implications using the "same franchise" argument it is accepted very quickly. In fact, you're the first one I see saying the "too few images" rule also applies for copyright tags.
4 images is a very small number of posts to warrant any kind of implication though, regardless of if it's a copyright tag or not. The series can easily be linked in the wiki of the parent tag, and if no one is using the implication, it's kind of a waste to be dedicating resources to its existence. It's existence also doesn't really assist in tagging when the tag is actually not being used.
I still think it's better to wait for a time when the tag has more posts before proceeding with giving it an implication. Past instances where it was approved probably should have waited until it was clear the tags were being used. Although perhaps they expected the tags would be used, but in this case it seems rather clear the tag is currently not really being used.
The bulk update request #1235 (forum #133854) has been rejected by @DanbooruBot.