staff
235
edits
Content:Characters: Difference between revisions
→Character Relations
(→Character Relations: predecessor/successor) |
|||
| Line 61: | Line 61: | ||
==Character Relations== | ==Character Relations== | ||
As you have a parent, Sousuke might have one. Thus we have established the char-char relations. You can access them on every character page by clicking on the "Add Entitiy Relation" tab, if there is no relation yet present, or, accessing the "Related Entities" tab and clicking [add/edit relations], when somebody has added at least one relation. | As you have a parent, Sousuke might have one. Thus we have established the char-char relations. You can access them on every character page by clicking on the "Add Entitiy Relation" tab, if there is no relation yet present, or, accessing the "Related Entities" tab and clicking [add/edit relations], when somebody has added at least one relation. Should you need specific help concerning the relations of a character, look for [[User:Hinoe|Hinoe]] on [[IRC:anidb|our IRC channel]] or click "report this entry" in the "Contribution" tab on the character's main info block to issue a comment creq. | ||
There are many different kinds of relations that can be set and are self explanatory by the name or relation they carry | ===General notes on character relations=== | ||
There are many different kinds of relations that can be set and are self-explanatory by the name or relation they carry; others might need a comment to specify the relation a bit more. If on doubt, simply consider whether the relation type explains everything there is to be explained. Some relations will have standardized comments; others will require comments but not have a specific standard on them. When there is no standard currently set for the relation type, general rules and common sense apply; when examples are available, following them should be generally safe. Additionally, if a relation has ended, it is '''highly encouraged''' for the comment to specify the point in the timeline and the reason why the relation ended. | |||
Character relations are supposed to be '''lower case''', as well as '''short''' and as '''neutral''' as possible. They are furthermore '''always''' supposed to be two-sided; the vice versa option should '''always''' be marked. If a relation is truly one-sided (e.g. character A considers character B a rival, but character B doesn't think that way, or maybe doesn't even know character A exists), the comment should specify it as "on character A's part only". | |||
===is family of=== | ===is family of=== | ||
This is a perfect example for the 'in need of comment' category. Being part of a family can mean a lot of things, and many people have different ideas of how to put those into words. Beneath you'll find a list of preferred wording for those relations. | This is a perfect example for the 'in need of comment' category. Being part of a family can mean a lot of things, and many people have different ideas of how to put those into words. Beneath you'll find a list of preferred wording for those relations. | ||
While it should be as neutral as possible, the (usually) older family member should always be mentioned first. Even there are exceptions - an uncle can be born later than a nephew - this will still use the same template. There will be no distinction between fraternal or maternal grandparents, uncles, aunts, etc. | |||
While it should be as neutral as possible, the (usually) older family member should always be mentioned first. Even though there are exceptions - an uncle can be born later than a nephew - this will still use the same template. There will be no distinction between fraternal or maternal grandparents, uncles, aunts, etc. | |||
Relationships in families can be genetic or non-genetic. The latter includes marriages and adoptions. So if your mother's brother marries a woman, she will still be considered your aunt. | Relationships in families can be genetic or non-genetic. The latter includes marriages and adoptions. So if your mother's brother marries a woman, she will still be considered your aunt. | ||
| Line 102: | Line 104: | ||
* quadruplets | * quadruplets | ||
* multiplets ''(quintuplets, sextuplets, and above)'' | * multiplets ''(quintuplets, sextuplets, and above)'' | ||
* distant blood relatives ''(other distant blood relation such as distant cousins or branch families, when relevant. Please note that this is often a fallback relation; if unsure, ask | * distant blood relatives ''(other distant blood relation such as distant cousins or branch families, when relevant. Please note that this is often a fallback relation; if unsure, ask before adding this comment)'' | ||
* in-laws (parents) ''(this goes for any combination of mother/father/daughter/son-in-law)'' | * in-laws (parents) ''(this goes for any combination of mother/father/daughter/son-in-law)'' | ||
* in-laws (siblings) ''(this goes for brother/sister-in-law)'' | * in-laws (siblings) ''(this goes for brother/sister-in-law)'' | ||
As a final note, please note that couples are '''NOT''' valid family relations; please use the appropriate couple-centered relations instead. If, however, the relation is incestuous, both the couple relation and the regular family relation should be added. | Family relations never end, even after one person dies. The question of whether someone who's related through marriage (e.g. your aunt who's your mother's brother's wife) continues to be a family member following a divorce or the death of their spouse has not yet been settled; for now, please assume all relations existing at the time of the end of the marriage will stay so, and new additions to the family will not have the relation. This is not yet settled policy and is subject to change at any time. Also, it should go without saying, but family relations are never one-sided. | ||
As a final note, please note that couples are '''NOT''' valid family relations; please use the appropriate couple-centered relations instead. If, however, the relation is incestuous, both the couple relation and the regular family relation should evidently be added. | |||
===is killed by / kills=== | |||
On its own, that relation is entirely self-explanatory. A comment might elaborate on the circumstances, reasons, means employed, and so on; some examples might include "stabbed in the jugular vein with a ballpoint pen" or "accidentally shot on the forehead". Clearly, this relation is never one-sided and never ends. | |||
===is the predecessor of / is the successor of=== | ===is the predecessor of / is the successor of=== | ||
This relation type also requires a comment, as it always refers to an office, position, title, etc. You can be someone's successor as some company's CEO, as some country's king, as head of your clan, and so on; the comment should specify what role specifically one character succeeded the other in. | This relation type also requires a comment, as it always refers to an office, position, title, etc. You can be someone's successor as some company's CEO, as some country's king, as head of your clan, and so on; the comment should specify what role specifically one character succeeded the other in. Some reasonable examples might be "as family head", "as king", "as the King of England", or "as Nintendo's president". This relation is never one-sided, and it never ends. | ||
===is the rival of=== | |||
This relation type implies an object of rivalry between the rivals, which needs to be specified; when two people compete, they compete for something, and there is a need of a comment to specify what they are competing for. You can be someone's rival in the fight for someone else's love, in trying to be the fastest racer in town, in your goal of being the very best, like no one ever was, and so on; additionally, rivalries might end following some sort of event, and they may be one-sided, in that only one side recognizes the other as a rival. Reasonable examples might be "for Sakura's love", "for Sakura's love, until Tarou fell in love with Yuri", "for Sakura's love, until Tarou died", "for Sakura's love, only on Keiichi's part", "for Sakura's love, only on Keiichi's part, until Tarou died", "as fellow racers", and so forth. | |||
===other=== | ===other=== | ||
The "other" relation type '''always''' requires a comment, because otherwise people won't be able to understand what the relation is even supposed to cover. This may sound obvious, but "other"-type relations without a comment are very common, leading to much frustration when dealing with them. As such, please always describe the "other"-type relations you add. | The "other" relation type '''always''' requires a comment, because otherwise people won't be able to understand what the relation is even supposed to cover. This may sound obvious, but "other"-type relations without a comment are very common, leading to much frustration when dealing with them. As such, please '''always''' describe the "other"-type relations you add, and try to elaborate on any you find. Since this relation type is a catchall for anything not covered by any other type, it may be one-sided, and it may end, or it may not. Please exercise common sense to its fullest when adding an "other"-type relation and do not add foolish relations over inane things. | ||
[[Category:CharDB]] | [[Category:CharDB]] | ||