Crystal Pool:Characters

This project page covers the convention on character entities.

Cat-like characters

Cat-like characters means any entity in the Warriors series that has affiliation, ancestry, mentorship, just like any normal cat characters dipicted in the book.

Examples

• Firestar (Q621): ThunderClan tom, formerly kittypet, first appeared in Into the Wild
• Graystripe (Q714): ThunderClan tom, first appeared in Into the Wild
• Sunpelt (Q3023): LionClan male lion, first appeared in Secrets of the Clans
• Fleetfoot (Q2759): LeopardClan leopardess, first appeared in Code of the Clans

Labels

Use the current cat name in Label field. Alternative name translations and old names should go to Also known as field. Do not add any disambiguation suffix (e.g. (SC)) in the label or alias.

Birth and death

Use birth time on timelime (P95) to denote when the character has been born. You may qualify the statement with timeline offset (P94) if there is some offset needed; see Firestar (Q621) for an example of this.

Use death time on timeline (P96) to denote when the character has died, or losing a life. You may qualify the statement with timeline offset (P94), manner of death (P97) and killed by (P109).

See Crystal Pool:Timeline for the entities you can use as value.

Affiliations

Use member of (P76) to specify the clans or groups the character belongs or used to belong to. You should specify a entity that is an instance or subclass of organization (Q4221) or fictional organization (Q4222).

• Use Nowhere (Q663) for cats that have deceased twice (the cat first goes to StarClan (Q634) or counterparts; then gets killed).
• Use loner (Q648) for living cats that have left the clan or current group, and do not belong to any other groups.
• Refrain from marking a cat as rogue (Q649), if the cat shows no animosity to the clan cats.
  • Especially, do not mark a cat as rogue (Q649) if the book does not mention so.
  • Ravenpaw (Q719) is marked as loner (Q648) even though he has been mentioned in the book as "rogue" once.
• Use unknown value for characters whose belonging is yet to be discovered.

Do not use no value for this statement.

You should qualify member of (P76) statement with start point on timeline (P92) and end point on timeline (P93) to annotate the time range a character belonging to a specific group. See Crystal Pool:Timeline for the entities you can use as value. For current affiliation, do not specify end point on timeline (P93). If the affiliation ends at a certain unknown point on timeline, specify unknown value for end point on timeline (P93).

Positions held

Use position held (P83) to specify the positions the character takes or used to take. You need to specify a entity that is an instance or subclass of fictional office, position, or title (Q669).

• Do not use kit (Q680) as value. This is not actually a position, but just a stage of life.
• Do not use no value for this statement.

Similar to affiliations, qualify position held (P83) statements with start point on timeline (P92) and end point on timeline (P93) to annotate the time range a character takes a specific position.

You should qualify position held (P83) statements with of (P21) to specify the clan or group of which they are taking the position.

Where appropriate, you may Qualify position held (P83) statements with replaces (P101) to specify the previous character taking this position.

Minor characters

The existence of an entity lies in its relation with other entities.

Minor characters means any cat-like character that

• only appears in the Affiliations part of the book throughout the whole series (thus is named), or
• only gets mentioned, depicted, or illustrated in the book, with out mentioning its name, and is different from any known entity on Crystal Pool so far, or
• never gets mentioned, depicted, or illustrated in the book, but has inferrable relation (such as kinship or mentorship) with a known entity on Crystal Pool.

warriors:Minor characters is a page dedicated for minor characters for sake of easier maintenance. On Crystal Pool, creating an entity is trivial, so we can use separate entity to designate every minor character. However, in most of the cases, unknown value may be more suitable to represent an entity that exists but we don't know.

For minor characters with their names mentioned, we may create the entity like other normal cat-like characters.

For unnamed minor characters, while creating the entity is effortless, such entity often make little impact on the whole database and could be a waste of contributor's energy. Considering creating the entity for an character…

• if such entity is needed for representing any high-order relations, such as sibling, grand-parent, grand-grand-parent, etc. For example, Thunderstar (Q2822) has two siblings. There is no way to represent "sibling" relation with father (P88) and mother (P89) if we do not have an explicit entity for these two siblings. So we have Lightning (Q3716) and Rumble (Q3717).
• Or if such entity represents a child of an existing cat in the database, such as Lightning (Q3716). We may be interested in how many children a couple have.
• Or if such entity is going to be named soon. Such as Bramblestar's impostor (Q3720).

When creating entity for unnamed minor characters, leave Label field blank, and make sure to include the notable traits of this character in Description field. You need to add statements for this entity, such as instance of (P3): fictional cat character (Q622), just like normal cat-like characters.

Other characters

For now we do not collect information about other characters, such as Midnight or Darrel, because the sample count in this category is not huge enough to make notable impact.