summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorYorhel <git@yorhel.nl>2011-12-29 14:10:32 +0100
committerYorhel <git@yorhel.nl>2011-12-29 14:10:32 +0100
commitc673a8e06abae7e12724b2815c03431190ffe3f8 (patch)
tree164ab5e8597095891f28bb86e3a2444d8a90e6e5
parentd346fc5072de24300ab5edec965efa1fcab814b1 (diff)
docs: Added lots of stuff on the character db & misc things
-rw-r--r--data/docs/10112
-rw-r--r--data/docs/12146
-rw-r--r--data/docs/22
-rw-r--r--data/docs/524
-rw-r--r--data/docs/index2
5 files changed, 248 insertions, 38 deletions
diff --git a/data/docs/10 b/data/docs/10
index 1840dc8e..442be47a 100644
--- a/data/docs/10
+++ b/data/docs/10
@@ -1,41 +1,65 @@
-:TITLE:Tagging system
-:INC:notfinished
+:TITLE:Tags & traits
:INC:index
:SUB:Introduction
-<i>TODO</i>
+<p>
+ VNDB has a system for tags and one for traits. Tags are used to categorize
+ <b>visual novels</b>, while traits tell something about <b>characters</b>. This
+ also makes them somewhat different in use. This page describes some general
+ guidelines and tips on using tags and traits.
+</p>
+
-:SUB:Tag voting
+:SUB:Tags
<p>
- While everyone is pretty much free to link any tag to any visual novel, please keep the following
- in mind while voting:
+ Tags can be assigned to visual novel entries using a voting system. Every user
+ can add a tag to a visual novel by going to the "modify tags" tab of a visual
+ novel page.
+</p>
+
+:SUBSUB:Tag voting
+<p>Tags can be assigned a vote from -3 to 3. This vote should be interpreted as
+ follows:</p>
+<ol style="list-style-type: none; margin-left: 15px">
+ <li><b>-3</b>: This tag really doesn't apply to the VN.</li>
+ <li><b>-2</b> and <b>-1</b>: These not very often used, but can be useful to
+ show that you disagree, but are not 100% sure.</li>
+ <li><b>0</b>: It is possible to change your vote to '0' to remove it.</li>
+ <li><b>1</b>: The tag does apply to the visual novel, but is not too apparent
+ or only plays a minor role.</li>
+ <li><b>2</b>: The tag certainly applies to the visual novel.</li>
+ <li><b>3</b>: The tag applies and is very apparent or plays a major role.</li>
+</ol>
+<p><br />
+ While everyone is pretty much free to link any tag to any visual novel, please
+ keep the following in mind while voting:
</p>
<ul>
- <li>Read the description of each tag before you link it to a VN, some tags may not always mean what
- you think they do.</li>
- <li>Try to be as specific as you can. For example, if a game has drama elements, rather than voting
- on the "Drama" tag, try to look for a more specific child tag that describes what kind of drama a
- player can expect.</li>
- <li>A rating between -3 and 3 can be given to a tag. A negative rating indicates that you disagree
- with a tag, with -1 being "I wouldn't say this tag really applies" and -3 meaning you fully disagree
- and the tag really doesn't apply at all. A positive rating works the opposite way, and indicates
- that you do agree with it.</li>
- <li>Some tags can act as spoilers for the plot of a VN, this can be indicated by voting on the spoiler
- status. It is highly recommended to not leave this as "Neutral", and really try to give an indication
- of whether the tag is not a spoiler at all or does spoil a bit.</li>
- <li>Tags are supposed to reflect the things you'll be experiencing as you play the game, even if
- some things might get revealed to be lies or illusions towards the end of the story. In cases like this,
- add both the (arguably incorrect) tags and the tags describing the situation after the truth has been
- revealed, making sure mark the "correct" tags as spoilers.</li>
+ <li>Read the description of each tag before you link it to a VN: some tags may
+ not always mean what you think they do.</li>
+ <li>Try to be as specific as you can. For example, if a game has drama
+ elements, rather than voting on the "Drama" tag, try to look for a more
+ specific child tag that describes what kind of drama a player can expect.</li>
+ <li>Some tags can act as spoilers for the plot of a VN, this can be indicated
+ by voting on the spoiler status. It is highly recommended to not leave this as
+ "Neutral", and really try to give an indication of whether the tag is not a
+ spoiler at all or does spoil a bit.</li>
+ <li>Tags are supposed to reflect the things you'll be experiencing as you play
+ the game, even if some things might get revealed to be lies or illusions
+ towards the end of the story. In cases like this, add both the (arguably
+ incorrect) tags and the tags describing the situation after the truth has been
+ revealed, making sure to mark the "correct" tags as spoilers.</li>
</ul>
-:SUB:Tag guidelines
+:SUBSUB:Tag creation guidelines
<p>
- New tags can be requested by everyone, but they'll have to be accepted by a moderator before
- the tags will be browsable. The following rules apply:
+ New tags can be requested by everyone, but they'll have to be accepted by a
+ moderator before the tags will be browsable. Applying the following guidelines
+ significantly increases the chances that your tag will be accepted and lowers
+ the workload of the moderator team.
</p>
<ul>
<li>Tag names should be self-describing. While the meaning of a tag can be obvious if you look
@@ -51,3 +75,41 @@
covered by VNDB, like staff or licensed state in a country.</li>
</ul>
+
+
+:SUB:Traits
+<p>
+ Traits can be assigned to characters. Contrary to tags, traits can't be voted
+ on. Instead, traits are part of the editing system, and modifying the traits
+ for a certain character involves editing the character entry itself.
+</p>
+
+:SUBSUB:Assigning traits
+<p>
+ Unlike tags, traits don't have any "levels": a trait either applies to the
+ character or it does not. Here are some guidelines and tips when assigning
+ traits to characters:
+</p>
+<ul>
+ <li>If no traits are present yet and you're the first person to add traits,
+ please try to be as complete as possible. Browse through the <a
+ href="/i">trait tree</a> and try to find as many traits that apply to the
+ character as possible.</li>
+ <li>Spoilery traits should *always* be marked as such.</li>
+</ul>
+
+:SUBSUB:Trait creation
+<p>
+ Anyone can request new traits to be added to the database. However, these need
+ to be approved by a moderator before they can actually be assigned to a
+ character.<br /><br />
+ Traits are categorized into "groups", the top-most trait in the tree
+ defines in which group a trait is. Unlike tags, traits don't need to have a
+ globally unique name, but they must be unique and self-describing within the
+ same group. For example, there can be multiple traits with the name "Blue",
+ but one is in the "Hair" group while the other is in the "Eyes" group. So
+ make sure to keep the group in mind when naming a trait.<br /><br />
+ Read the descriptions of the various trait groups and meta traits to get a
+ feel on how they are supposed to be used.
+</p>
+
diff --git a/data/docs/12 b/data/docs/12
index 50bd98bc..e19db5d4 100644
--- a/data/docs/12
+++ b/data/docs/12
@@ -1,5 +1,149 @@
:TITLE:Adding/Editing Characters
:INC:index
+:INC:notfinished
-<i>to-do</i>
+
+:SUB:Introduction
+<p>
+ Characters represent persons, animals and things within a visual novel. Any
+ character in a visual novel, no matter how obscure their role is, may be added
+ to the database, although it is recommended to at least add the more important
+ characters first. When adding characters, try to be complete: That is, try to
+ add as many characters of a single visual novel, rather than adding a single
+ character to many VNs.
+</p>
+
+
+:SUB:Instances
+<i>todo: when and how to use instances.</i>
+
+
+:SUB:General info
+<dl>
+ <dt>Name (romaji)</dt><dd>
+ Name of the character, in the latin alphabet. Check out the <a
+ href="/d5">general editing guidelines</a> for information on name order and
+ romanization. Try to use the full name when known. If the full name is not
+ known, then use either the first or last name. If even that isn't known, use
+ the name that is most commonly used to refer to this character in the story.
+ In the case the character is never referred to with a name or title (e.g.
+ it's the protagonist), "Unnamed" can be used as name.<br />
+ In some cases the full name is a spoiler, see the chapter on instances above
+ for some ways to handle that.
+ </dd><dt>Original name</dt><dd>
+ The actual name of the character, in the case it is not officially in the
+ latin alphabet. Leave empty if it's the same as the "Name (romaji)". If
+ possible, try to include a space between the given name and the surname.
+ </dd><dt>Aliases</dt><dd>
+ Other names this character is known by, such as nick names used by other
+ characters within the story. Since this field does not have any option to
+ hide spoilers, you shouldn't include spoilery names here. It is possible to
+ mention such aliases with a [spoiler] tag in the description.
+ </dd><dt>Description</dt><dd>
+ A short description of the character. While it is advised to keep the
+ spoilers to a minimum, you can use the usual <a href="/d9.3">formatting
+ codes</a> such as [spoiler] to include spoilers while hiding them by default.
+ When using a description from external sources, check out the <a
+ href="/d5.5">general editing guidelines</a> for quoting rules.
+ </dd><dt>Gender</dt><dd>
+ Gender of the character. This is usually rather straightforward, but there
+ are some odd cases: (Reverse) traps should have their biological gender
+ filled out here. Futanari should be marked as "both".<br />
+ If the real gender is a spoiler, which is sometimes the case with traps,
+ leave this field at "Unknown". See the chapter on instances above if the
+ character "transforms" between a male and female version.
+ </dd><dt>Birthday</dt><dd>
+ Month and day of the character's birthday. Note that a year is not included.
+ </dd><dt>Bust / Waist / Hips</dt><dd>
+ <a href="http://en.wikipedia.org/wiki/BWH">BWH</a> measurements, if known.
+ This information should either come from the game itself or from a reliable
+ source (usually the official homepage). Don't try to guess these!<br />
+ If the official source does not provide this information as a natural number,
+ the number should rounded to allow its use in the database. If the official
+ information is not in the metric system, convert the numbers and round them
+ before entering.
+ </dd><dt>Height</dt><dd>
+ Height of the character, in cm. The above note on natural numbers and the
+ metric system also applies here.
+ </dd><dt>Weight</dt><dd>
+ Weight of the character, in kg. The above note on natural numbers and the
+ metric system also applies here.
+ </dd><dt>Blood type</dt><dd>
+ Blood type, if known and applicable. This makes little sense if the character
+ isn't a human.
+ </dd>
+</dl>
+
+
+:SUB:Image
+<p>
+ There is a lot of freedom with regards to uploading an image to a character
+ entry, but the following is a list of things to keep in mind:
+<ul>
+ <li>The image must be "safe for work", according to the <a href="/d2#4">VN
+ image guidelines</a>. You may add creative sensoring to make an image safe if
+ otherwise no image for the character is available.</li>
+ <li>The image must be official, i.e. it must be extracted from the VN itself
+ or from the official homepage. Fan art is definitely not allowed!</li>
+ <li>This image should be chosen from an image that is showing the most common
+ clothing and facial expression the character wears through the game.</li>
+ <li>Images using the in-game sprites (tachi-e) are preferred; Otherwise cuts
+ from CGs are also allowed.</li>
+ <li>The image must at least include the head (assuming it has one) and
+ shoulders of the character. Full-body shots are fine, but legs are generally
+ not that interesting yet cause the overall image to shrink dramatically.</li>
+ <li>The image will be cropped to 256x300, but it is recommended to do this
+ cropping manually before uploading to ensure that all character images of the
+ same VN have the same width. This consistency looks better on the character
+ listing on the VN page.</li>
+</ul>
+
+
+:SUB:Traits
+<p>
+ See the <a href="/d10">Tags &amp; traits</a> page for guidelines on the traits.
+</p>
+
+
+:SUB:Visual Novels
+<p>
+ A character should always be linked to at least one visual novel entry, but may
+ be linked with more when it appears in multiple visual novels.<br />
+ If a character appears in all releases of the visual novel, with the possible
+ exception of trial releases, then simply keep one release and leave it at "All
+ / others". In other situations, mention explicitely in which releases the
+ character appears and which role they have in that release. Multiple releases
+ can be added with the same role and spoiler information.<br />
+ If a characters' role or the entire existance of that character in the visual
+ novel is a spoiler, make sure to mark it as such.<br />
+ The following roles are available:
+</p>
+<dl>
+ <dt>Protagonist</dt><dd>
+ The (or "a") protagonist. The person through which the story is told. Note
+ that a significant portion of the story has to be told through the eyes of
+ the character for it to be considered a protagonist. Some visual novels may
+ switch perspectives for a (relatively) short amount of time, but this does
+ not always make the character a protagonist.
+ </dd><dt>Main character</dt><dd>
+ A character that plays a major role in the story or gets a lot of screen
+ time. In general, a herione with an own route always qualifies and so do
+ sidekicks/classmates that are very often seen.
+ </dd><dt>Side character</dt><dd>
+ A character that plays a minor role or does not get a lot of screen time.
+ This is often the case for characters that appear only in a single branch or
+ a single part of the story, although this is not a mandatory.
+ </dd><dt>Makes an appearance</dt><dd>
+ This role is used for characters that only appear in the story for a short
+ while and have only very little to no lines of dialog. Often used for <a
+ href="http://en.wikipedia.org/wiki/Cameo_appearance">cameo appearances</a>.
+ </dd>
+</dl>
+<p>
+ Note that there is no distinct line between these roles, and one could have
+ endless (and often rather pointless) discussions about the actual role of a
+ character. Simply assign the role that you think most naturally fits the
+ character. To get some inspiration, look around for characters in other visual
+ novels that play a somewhat similar role.
+</p>
diff --git a/data/docs/2 b/data/docs/2
index be5c4e5a..295fc21d 100644
--- a/data/docs/2
+++ b/data/docs/2
@@ -105,6 +105,8 @@
<li>If multiple characters are portrayed and they are engaged in physical contact
that may be considered as (a precursor to) sexual contact, then it's NSFW as well.
</li>
+ <li>NSFW is solely determined by the graphics: Images that contain suggestive
+ text but are not otherwise NSFW are safe.</li>
</ul><p>
Even with these guidelines it may not always be easy to determine whether an image
is safe or not. When in doubt, it's often best to go for NSFW.
diff --git a/data/docs/5 b/data/docs/5
index ee938f3a..fbe8dd47 100644
--- a/data/docs/5
+++ b/data/docs/5
@@ -72,16 +72,18 @@
:SUB:Descriptions From External Sources
<p>
- It is possible to add a description or notes to visual novel, producer and release entries
- in the database. While original descriptions are preferred, using descriptions from external
- resources is allowed, provided the source is properly credited. The preferred form to credit
- external resources is by adding the following template to the bottom of the description:<br />
+ It is possible to add a description or notes to visual novel, producer,
+ release and character entries in the database. While original descriptions are
+ preferred, using descriptions from external resources is allowed, provided the
+ source is properly credited. The preferred form to credit external resources
+ is by adding the following template to the bottom of the description:<br />
[From [url=<b>URL</b>]<b>title or author</b>[/url]]<br />
- This would result in, for example, '[From <a href="http://en.wikipedia.org/Wiki/Ever17">Wikipedia</a>]'
- for descriptions taken from Wikipedia. If the description is not literally taken from the
- source but has some modifications, the 'From' should be replaced with something similar,
- indicating that it's modified, e.g. 'Edited from', 'Based on'.<br />
- As it is not allowed to provide links to websites providing or promoting illigal downloads,
- the URL part should be left out for such descriptions.
+ This would result in, for example, '[From <a
+ href="http://en.wikipedia.org/Wiki/Ever17">Wikipedia</a>]' for descriptions
+ taken from Wikipedia. If the description is not literally taken from the
+ source but has some modifications, the 'From' should be replaced with
+ something similar, indicating that it's modified, e.g. 'Edited from', 'Based
+ on'.<br />
+ As it is not allowed to provide links to websites providing or promoting
+ illigal downloads, the URL part should be left out for such descriptions.
</p>
-
diff --git a/data/docs/index b/data/docs/index
index 24d67213..e189934c 100644
--- a/data/docs/index
+++ b/data/docs/index
@@ -5,7 +5,7 @@
<li><a href="/d3">Releases</a></li>
<li><a href="/d4">Producers</a></li>
<li><a href="/d12">Characters</a></li>
- <li><a href="/d10">Tags</a></li>
+ <li><a href="/d10">Tags &amp; traits</a></li>
<li><a href="/d13">Capturing screenshots</a></li>
<li><b>About VNDB</b></li>
<li><a href="/d9">Discussion board</a></li>