|
STORYCODE
| Which fields are explained on this page? |
storycode
|
| |
| In which input files are these fields used? |
On story lines: in DBS files, FSB files, y.dbs and z.dbs, yzsuper.dbs, w.dbi, DBI files, DPG CSV files.
On story header lines: in DBS files, y.dbs and z.dbs, yzsuper.dbs, w.dbi.
On entry lines: in DBI files, w.dbi.
On movies.dbs lines: in movies.dbs.
|
|
storycode
| What should the field look like? |
Syntax: fixed position, or [storycode:xx]
In FSB files: First line, everything before the first '('.
Duplicate spaces can be omitted. The storycode is converted so that the '-' is in the 10th position.
If there is a '-' at position 9 or higher, the code is not modified at all. This probably only occurs for I AO, I NRT and I POP.
The tag [storycode:] currently occurs (approximately) 3173 times in the input files.
|
| |
| What does the field contain? |
A normalised code, the connection between a Story and the Entries that refer to the Story.
(With Story, in this context we also mean movies, covers, illustrations, articles, etc.)
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).
See also printedcode.
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).
If a storycode in an issue index is unknown, the storycode field can contain incomplete information, or it can even be entirely empty.
The story codes should match (i.e. start with) the storycode of the corresponding h2 header, or h1 header (if no h2 header present).
An h2 storycode should match (i.e. start with) the storycode of the corresponding h1 header.
An h1 storycode should match (i.e. start with) the storycode of the corresponding h0 header.
But these things are not fully checked. |
| |
| Which checks are done? |
If a storycode in an issue index seems to indicate a newspaper strip, the date in the storycode is checked: Z-codes should have a Sunday, while Y-codes should not have a Sunday in their code.
If a storycode is a subcode, the code is replaced with the corresponding supercode. See superref.
|
| |
| Which log messages are related to this field? |
Log1 (serious)
202: Storycode is too short or otherwise too irregular!
- A proper storycode must be at least 4 characters, or 5 characters if it starts with Y or Z. A proper storycode must start with one of the letters ABCDEFGHIKMPQSUWXYZ. It must not contain a '*'.
216: storyitem has no proper storycode <...>
- The storycode should be at least 4 characters, and start with one of the storycode-starts that are allowed for this country.
232: code <...> contains non-ASCII characters
- Only printable ASCII characters are allowed.
410: Two story records with the same code
414: Two movie records with the same code
830: Italian story code has no '-' <...>
839: Italian story code has no space between 'I ' and the '-' <...>
Log2 (error)
235: code <...> is an old code for <...>
- If a storycode is an old code (in oldcodes.dbx), this is logged and the code is replaced with the new code.
412: Two story records with the same code
425: No fitting h0 header line that matches story code <...> - nearest lower h0 line is <...>
475: Use a different story code: <...>
- The story maintainer marked the storycode as not-to-be-used.
501: More than one story record in stories file!
- This message can occur when the "get unsolved stories" option is used.
Log3 (info)
281: ... <...> should be, but is not, a Sunday (but WOULD be a Sunday if day and month swapped!)
282: ... <...> should be, but is not, a Sunday
283: ... <...> is, but should not be, a Sunday (but WOULD be a non-Sunday if day and month swapped!)
284: ... <...> is, but should not be, a Sunday
411: Story not in story file
413: Story code should be <...> (packed:...)
Log4 (pedantic)
236: code <...> is a subcode of <...> (part ...)
- If a storycode is a subcode, the code is automatically replaced with the new code. Also part and startdate are filled.
415: Secundary story entry is ignored, there already is a story with the same code
C43: Storycode contains '?'
|
| |
| Which CSV field(s) use this field? |
Table inducks_entry, field guessedcode
Table inducks_entry, field storyversioncode
Table inducks_entryurl, field storycode
Table inducks_herocharacter, field storycode
Table inducks_log, field logkey
Table inducks_log, field storycode
Table inducks_movie, field moviecode
Table inducks_moviecharacter, field moviecode
Table inducks_moviejob, field moviecode
Table inducks_moviereference, field moviecode
Table inducks_statcharacterstory, field storyheadercode
Table inducks_statpersonstory, field storyheadercode
Table inducks_story, field originalstoryversioncode
Table inducks_story, field storycode
Table inducks_story, field storyheadercode
Table inducks_storycodes, field alternativecode
Table inducks_storycodes, field storycode
Table inducks_storyheader, field storyheadercode
Table inducks_storyreference, field fromstorycode
Table inducks_storyreference, field tostorycode
Table inducks_storysubseries, field storycode
Table inducks_storyurl, field storycode
Table inducks_storyversion, field storycode
Table inducks_substory, field originalstoryversioncode
Table inducks_substory, field storycode
Table induckspriv_entryurl, field storycode
Table induckspriv_story, field storycode
|
| |
| 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 xref.
To make searching for, and matching of, story codes as flexible as possible, story codes are also packed.
The idea is that someone types a story code, for instance "w Wdc 12-00".
This code is then translated into a packed code: "wwdc12-00".
The official story code was "W WDC 12-00", which also has a packed code of "wwdc12-00". So a search on packed code will find the story.
The current packing algorithm is as follows:
- make all letters lower case ('a'..'z');
- remove all spaces.
The packed code is a unique identification of a story, with some exceptions like "I PK3 1-1" and "I PK 31-1" which are different stories with the same packed code.
For these special cases, special arrangements were made. |
| |
|
|
|
|
