|
VARIOUS ENTRY FIELDS (NAMES, INCLUDEDIN, ...)
entrycode
| What should the field look like? |
Syntax: fixed position, or [entrycode:xx]
|
| |
| What does the field contain? |
A code indicating the issue plus the position of the story in the issue.
An entry code should be unique within one country (but it is not necessarily globally unique).
The position is indicated with one or two lower case letters, the rest of the EntryCode should not contain lower case letters.
(Entry codes in w.dbi, for USA comics before 1985, are an exception to this.)
Alternatively, an entry code can consist of the issue code, followed by a 'p' and a page number. This page number indicates the starting page of the entry.
If more than one entry start on the same page, an extra 'a', 'b', etc. is added.
Example: DDA 12b [the 2nd entry in Gladstone's Donald Duck Adventures #12]
Example: CBL 10p321 [the entry in CBL 10 that starts on page 321]
Example: CBL 7p329b [the second entry in CBL 7 that starts on page 329]
If a cover of an issue is not indexed, we don't use "a" as position letter for the first indexed item (but e.g. "b"). |
| |
| Which checks are done? |
The entry codes should be in exact alphabetical order in a DBI file.
(For issues that are not entirely indexed, identical entry codes are allowed - but not recommended.)
The entry code should match (i.e. start with) the issuecode of the corresponding h3 header. |
| |
| Which log messages are related to this field? |
Log1 (serious)
220: Lines are not properly sorted (... should be after ...)
221: Identical entrycodes
- Dizni tries to repair this error by making up a unique code.
229: Entry code [...] does not start with h3 issue code [...]
- All entries must start with the code of the h3 line of the issue. Maybe a h3 line is wrong or missing?
|
| |
| Which CSV field(s) use this field? |
Table inducks_entry, field entrycode
Table inducks_entry, field includedinentrycode
Table inducks_entry, field issuecode
Table inducks_entry, field position
Table inducks_entry, field storyversioncode
Table inducks_entrycharactername, field entrycode
Table inducks_entryjob, field entrycode
Table inducks_entryurl, field entrycode
Table inducks_log, field logkey
Table inducks_logocharacter, field entrycode
Table induckspriv_entry, field entrycode
|
| |
|
includedin
| What should the field look like? |
Syntax: [includedin:x] (where x is a letter). In w.dbi: [includedin:-xx] (where xx is 2 digits)
|
| |
| What does the field contain? |
The position of the entry where this item actually belongs to. Example:
CBJUL 1c Qno/CBJ 1 5 a -- Advent i Andeby
CBJUL 1d CB OIL 16 0+i -- [brokpg:1/6] [includedin:c]
In this example, a 1/6-page painting is actually part of a 5-page article.
Included entries should be listed directly after the "main" entry. (This is not fully checked.)
The page count of the "main" entry should be the total page count. |
| |
| Which log messages are related to this field? |
Log3 (info)
249: includedin <...> should be a previous entry position
|
| |
| Which CSV field(s) use this field? |
Table inducks_entry, field includedinentrycode
|
| |
| How is the data used in the rest of Inducks? |
| If includedin is used, the page count is not checked (it can differ from the original pages of an item). |
| |
|
lang
| What should the field look like? |
Syntax: [lang:xx]
|
| |
| What does the field contain? |
| The language of the text of the item, if this is different from the language of the issue. |
| |
| Which log messages are related to this field? |
Log1 (serious)
C08: Unknown language <...>
Log2 (error)
C10: More than one language <...> is not possible
Log4 (pedantic)
214: character <...=...> appears in ... comic but has no name in that language
|
| |
| Which CSV field(s) use this field? |
Table inducks_entry, field languagecode
|
| |
| How is the data used in the rest of Inducks? |
| It is used to determine what the names field actually means. If the lang field is empty, Dizni uses the language of the issue. |
| |
|
names
| What should the field look like? |
Syntax: [names:translatedname(officialname),translatedname(officialname!),-(officialname)]
|
| |
| What does the field contain? |
Translations of characters in a specific story.
We use this for translations of characters that occur rarely, or for rare translations of normal characters.
The normal translations of normal characters are specified in the heroes-xx.dbl files.
If a character is not named at all in a translation, we use a '-'. |
| |
| Which checks are done? |
Every officialname should occur in the xapp field for this story. (This xapp field doesn't need to be specified as xapp in the DBI file.)
Except when an exclamation mark is used:
In the case of [names:translatedname(officialname!)] the officialname does not need to be in the xapp.
This is used in cases where a character is mentioned in a story, but not actually visible. |
| |
| Which log messages are related to this field? |
Log2 (error)
213: character in names-field <...> for <...> does not appear in xapp <...> (add ! if this is intentional)
Log4 (pedantic)
214: character <...=...> appears in ... comic but has no name in that language
|
| |
| Which CSV field(s) use this field? |
Table inducks_entrycharactername, field charactercode
Table inducks_entrycharactername, field charactername
|
| |
| How is the data used in the rest of Inducks? |
| The translatednames are added to the translations in the character legend. Except when '-' is used. |
| |
|
phero
| What should the field look like? |
Syntax: [phero:xxxx]
|
| |
| What does the field contain? |
The actual printed name of the title hero of a story, if that is different from the usual name of that character in the entry's language.
If a story has more than one hero, the phero field still has one value.
For instance: [hero:DD,DA] [phero:Donald and Daisy]. |
| |
| Which log messages are related to this field? |
|
None.
|
| |
| Which CSV field(s) use this field? |
Table inducks_entry, field printedhero
|
| |
|
re
| What should the field look like? |
Syntax: [re:xxx]
|
| |
| What does the field contain? |
This field is used for a reprint of a story that has no known Inducks story code.
If the story code is known and correct, the re-field is supposed to be empty. This is not checked. |
| |
| Which log messages are related to this field? |
|
None.
|
| |
| Which CSV field(s) use this field? |
Table inducks_entry, field alsoreprint
|
| |
|
storycomment
| What should the field look like? |
Syntax: [storycomment:xxx]
|
| |
| What does the field contain? |
A comment that is actually only about the story and not about the publication of that story.
This is ONLY to be used for storyitems.
About storyitems, see the field storyitem. |
| |
| Which log messages are related to this field? |
Log2 (error)
350: storycomment should only be used for story-items
|
| |
| Which CSV field(s) use this field? |
Table inducks_story, field storycomment
|
| |
|
storyitem
| What should the field look like? |
Syntax: [storyitem:yes] or [storyitem:$STORYITEM$].
If an entry line in w.dbi starts with a W, it is a story item.
|
| |
| What does the field contain? |
Some story items are not listed in a story file, but only in an issue file. This is for convenience of the indexer.
For instance, all F-coded stories are defined as story items in the French DBI index.
If the story code does not "match" the issue code, the field storyitem needs to have
the contents "yes" or "$STORYITEM$".
This field should be used with care!
See also the fields allowedstoryitemstarts and autostoryitemstarts. |
| |
| Which log messages are related to this field? |
Log1 (serious)
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.
289a: storyitem should not be used here
- Q-items cannot have [storyitem:yes]
|
| |
| Which CSV field(s) use this field? |
|
|
| |
| How is the data used in the rest of Inducks? |
| If the storyitem field is nonempty, the line in the DBI file is also read as if it were a line from a DBS file, with
some of the fields discarded. |
| |
|
xref
| What should the field look like? |
Syntax: [xref:xx(reason),xx(reason)]
|
| |
| What does the field contain? |
| See xref |
| |
| Which log messages are related to this field? |
Log1 (serious)
232: code <...> contains non-ASCII characters
- Only printable ASCII characters are allowed.
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.
420: unresolved xref - story does not exist (packed ...)
455: Mismatch in xref:... with data from story file <...>
Log3 (info)
293: ... <...> is an ambiguous name
294: ... <...> should be indicated as <...>
298: ... <...> should be spelled as <...>
- The field is almost right: some spaces or capital letters differ.
352: xref to implausible code (...) ignored
- 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 '*'.
454: xref:... not in story file (source ...)
Log4 (pedantic)
236: code <...> is a subcode of <...> (part ...)
- If a storycode is a subcode, the code is automatically replaced with the new code (in any issue index). Also part and startdate are filled.
237: xref <...> is not a plausible story code
- If this error occurs, this storycode in the xref is ignored.
239: xref <...> has no reference-reason
|
| |
| Which CSV field(s) use this field? |
Table inducks_moviereference, field storycode
Table inducks_referencereason, field referencereasontext
|
| |
|
|
|
|
