Implications and tag relationships are separate things. If that’s not obvious, uh…
What tag relationships aim to do I’m not quite sure. I just see it as filler information you can get on a given tag. You may want to contact System about this.
ALAKTORN said:
What tag relationships aim to do I’m not quite sure. I just see it as filler information you can get on a given tag. You may want to contact System about this.
Hi Alak,
I've seen sections for tag relationships in the wiki, such as "Related" and "See Also". If the parent/child sections in the wiki have nothing to do with tag implications, I wonder what they are used for.
How would I go about contacting System about this? I'm sure they're a busy person, like we all are.
Find his profile and send him a private message. He may or may not respond.

Dropout Drops More Than Just Studies
Sword Art Online Becomes A Reality: “VRMMO Announced!”
Dead or Alive Extreme 3’s Hitomi Hotter Than Ever
Tomori Ero-Cosplay by Komugi Caught on Camera
Conan O’Brien Korean Drama Appearance Quite Fishy
Mayasein
5 months ago[Outdated] Implications and wiki pages - parent/child tag sections confusing
EDIT: Since posting this, after learning more about the features discussed here I realize now that the ideas in this post are not well founded. You can still see the conversation below.
Hello administration!
Let's talk for a minute about tag implications, wiki pages, and the parent/child fields in the tag edit menu. When I first found these fields, I believed I could use them to edit a tag's implication structure directly, saving admin some time. (As I learned later, this isn't the case--The Tag implication help page is clear on admin's involvement, and how to propose implication edits.) What these fields do instead is to publish parent/child information to the tag's wiki page, with no respect to the tag's actual, source implication structure.
Users who are confused by the tag edit menu like I was are, misguidedly, spreading misinformation among tag wiki pages.
The above illustrates two problems, and an opportunity to kill two birds with one stone. The problems:
If tag wiki pages could be systematically populated with parent/child documentation as it's laid out in the system, there would be no need for the parent/child fields in the tag edit menu, and each of these problems would be solved.
A quicker fix might be to document the function of the parent/child tags on the tag edit screen--that is, updating the tag's wiki page--and to guide users on that page as to how they can properly propose implication changes.
Admins - Thank you for taking the time to check out this post! What are your thoughts on this issue? How would you deal with it?