Main
How to index
Beginners
More detail
Programmers
Scanners
File formats
ISV files
Field reference guide
Overview
DBI entry fields
DBI header fields
DBS fields
app
art
brokpg
comment
creationdate
creatorref
desc
desc-xx
enddate
hero
hiddencomment
ink
pagel
pages
part
plot
allprintedcodes
pubdate
ser
storycode
superref
title
titlepref
usedifferentcode
writ
xapp
xref
Extra DBS fields for movies
DBS header fields
DBL fields
Other fields
Automatic fields
Output overview
Credits/links
Producktion
Index of indexes
Various
|
esStoryCode
(storycode)
| In which input files is this field used? |
|
In DBS files (and in story-items in DBI files) |
| What should the field look like? |
In the usual files: fixed position, or [storycode:xx]
In FSB files:
First line, everything before the first '('.
Duplicate spaces can be omitted. The storycode is converted so the '-' is in the 10th position.
But storycodes starting with "I AO" or "I NRT" are not converted in any way.
In the files y.dbs and z.dbs: fixed position
In the files y.dbs and z.dbs when the storycode starts
with YM 0, YM 1, ZM 0, ZM 1, YX 0, YX 1, ZX 0, ZX 1, or ZT: fixed position
|
| What does the field contain? |
A normalised code, the connection between a Story and the Entries thet refer to the Story.
We try to keep the StoryCode as similar as possible to the code
that is shown in the first panel of a Disney story (in its original printing).
There are some specific rules for normalising a code. They are described in the
story code chapter
of this web site.
For stories (and other items) that do not carry a story code at all,
we make up our own codes. We use specific rules for that.
For covers, illustrations, puzzle pages, games, etc.
we use the letter of the publisher (e.g. D = Denmark,
H = Holland) plus "C ", followed by the issue code, and optionally an
upper case letter.
Examples: HC DD1978-01, DC AA1949-01, HC DD1999-01, HC DD1999-01P.
Sometimes we also list items that are non-Disney or non-comics (like articles).
These items can have a "story code" as well, starting with a Q. The rules are:
Qxx/CODEZ
where
Q = 'Q'
xx = country
CODE = issue code (of the first publication of the item)
Z = UPPER CASE sequence letter (optional).
|
| Which checks are done? |
A valid storycode should be 6 characters or more.
Only printable ASCII characters are allowed.
If a storycode is an old code (in oldcode.dbx), this is logged and the code is replaced with the new code.
If a storycode starts with a 'Q', it should be a single Q, or in the form QMsomething (a movie item) or
Qxx/something where xx is a country.
|
| Which CSV field(s) use this field? |
The field storycode
in table inducks_herocharacter
The field moviecode
in table inducks_movie
The field originalstoryversioncode
in table inducks_story
The field storycode
in table inducks_story
The field storycode
in table inducks_storycodes
The field tostorycode
in table inducks_storyreference
The field storycode
in table inducks_storysubseries
The field storycode
in table inducks_storyversion
The field storycode
in table induckspriv_story
|
| How is the data used in the rest of INDUCKS? |
The storycode connects data about the Story with all known reprints of that Story.
See also
storycode,
xrefd,
superrefd,
pscode,
onlystory.
|
This page was generated on 2008-04-18 by DVEGEN 4.8d © Harry Fluks 2003.
For more information contact Harry Fluks (hfl at inducks.org - replace the at)
|
|