Posted under Tags
Considering how connected the series is, and the many crossovers and in-universe media that require implications, why not make one big category for this?
It would contain:
Chaos;Head
Steins;Gate
Robotics;Notes
Chaos;Child
Occultic;Nine
Anonymous;Code
BUR #42193 is pending approval.
create implication chaos;head -> science_adventure_series
create implication steins;gate -> science_adventure_series
create implication robotics;notes -> science_adventure_series
create implication chaos;child -> science_adventure_series
create implication occultic;nine -> science_adventure_series
create implication anonymous;code -> science_adventure_series
category science_adventure_series -> copyright
As above.
The word "series" is not part of the title, so it should be science adventure (series), or even science adventure (mages) if you wanna remove all ambiguity.
Also, I think BURs are done from top to bottom, so it won't work unless the category change is put at the top.
BUR #42195 is pending approval.
create implication chaos;head -> science_adventure
create implication steins;gate -> science_adventure
create implication robotics;notes -> science_adventure
create implication chaos;child -> science_adventure
create implication occultic;nine -> science_adventure
create implication anonymous;code -> science_adventure
category science_adventure -> copyright
The first result when searching "Science Adventure" is the Wikipedia page, which does, in fact, list it only as "Science Adventure". A lot of results, however, call it the "Science Adventure Series", including Anonymous;Code's Steam page and the official website's about page.
I don't believe anyone's going to confuse it with anything else... so here's an alternative without the "series" part.
Updated by hasu no tokimeki
BaiserLaVerite said:
Also, I think BURs are done from top to bottom, so it won't work unless the category change is put at the top.
You are right that BURs happen top-to-bottom, but that's exactly why the category change is at the bottom. You can't change the category of a tag that doesn't exist, the implications will apply it first so it does exist to change its category.
hasu_no_tokimeki said:
You are right that BURs happen top-to-bottom, but that's exactly why the category change is at the bottom. You can't change the category of a tag that doesn't exist, the implications will apply it first so it does exist to change its category.
That last line is still unnecessary, though. BURs automatically create tags in the appropriate category, because cross category implications aren't allowed. A category change would only be necessary if the tag already existed, at which point that line would actually need to be at the top for the whole thing to even work.
blindVigil said:
That last line is still unnecessary, though. BURs automatically create tags in the appropriate category, because cross category implications aren't allowed. A category change would only be necessary if the tag already existed, at which point that line would actually need to be at the top for the whole thing to even work.
Do they, though? I've seen time and time again tags created from implications that... start as gentags. Stuff like topic #27078, where the osomatsu (series) tag had things implied into it, and it was a gentag until I BUR'd it in BUR #25915.
Maybe I should just open an issue or something.
Danbooru doesn't block implications if either the antecedent or consequent are empty in case a tag gets populated from another line in an update. It just calls save on all the posts that match the query antecedent -consequent which is what gets the newly implied tag added to those posts, much like how when you add a tag that implies another and then you press save, it will also add that tag for you.
CMIIW, people who know the source code better.
Do we really need an umbrella tag here? Asking as someone who only watched Steins;Gate a million years ago. A cursory googling is not showing any evidence of this being a connected universe that would require an umbrella. This looks more like a company_connection proxy to me.
