|
VARIOUS STORY/ENTRY FIELDS (SER, PRINTEDCODE, ...)
creationdate
| What should the field look like? |
Syntax: [creationdate:yyyy-mm-dd] or [creationdate:yyyy-mm-dd(writ),yyyy-mm-dd(art)]. In w.dbi on a fixed position (for story-items).
|
| |
| What does the field contain? |
| The creation date(s) of a story, or a close estimate of that. This information is usually given by the writer or artist of a story.
For instance, Carl Barks kept vouchers with dates, telling us when he delivered his stories. |
| |
| Which checks are done? |
Standard date field checks:
The field always has the (international standard) format "yyyy-mm-dd".
If the day is unknown, the field has no "-dd" ("yyyy-mm"). If the month
is unknown too, the date is simply a 4-digit year.
If only the quarter of the year is known, the date format is "yyyy-Qx" where x is 1,
2, 3, or 4. For instance "1998-Q3" = 3rd quarter of 1998.
A date field can be followed by a '?'.
If a date contains a letter 'y', 'm', or 'd', the rest of the date, starting with this letter, is ignored.
This allows dates like "1978-mm-dd" and "1978-03-dd". (This feature was added to make the input more readable.
Use it with care!)
Note that the full 4-digit year is mentioned in the date.
The checking on real dates is not done completely, for instance February 29th is allowed in all years.
|
|
| |
| Which log messages are related to this field? |
Log1 (serious)
271: ... <...> format should be yyyy-mm-dd
272: ... <...> non-digit
273: ... <...> wrong month
274a: ... <...> wrong day of month (31)
274b: ... <...> wrong day of month (30)
276: ... <...> wrong format
277: ... <...> wrong day
|
| |
| Which CSV field(s) use this field? |
Table inducks_storycreationdate, field creationcomment
Table inducks_storycreationdate, field creationdate
|
| |
| How is the data used in the rest of Inducks? |
| If the DBS field has a value, and a DBI field has no value, the DBS field is copied to the DBI field. |
| |
|
printedcode
| What should the field look like? |
Syntax: [printedcode:xxx] or [printedcode:-] or [printedcode:none]
In FSB files: On line 5 (or subsequent): [codice:xxx]
|
| |
| What does the field contain? |
The story code as it is actually printed in the issue. This is usually only listed when the printed code is very different from the Inducks story code. It helps in identifying stories.
If a story was printed without code, [printedcode:-] or [printedcode:none] can be used.
We don't list this if it is "normal", for instance a reprint in the 1950s seldom had a printed code.
The FSB also gives information about printed codes. Some other DBS files also have this information (though that is not logical). |
| |
| Which log messages are related to this field? |
|
None.
|
| |
| Which CSV field(s) use this field? |
Table inducks_entry, field printedcode
Table inducks_storycodes, field alternativecode
Table inducks_storycodes, field codecomment
Table inducks_storycodes, field unpackedcode
|
| |
|
ser
| What should the field look like? |
Syntax: [ser:xx(xx),xx(xx)] or [ser:-]
In FSB files: On line 5 (or subsequent): [serie:xxx].
Italian subseries names are converted to Inducks identifications.
Italian subseries names can contain a comma. Multiple subseries should be separated by a semicolon ';' (!)
|
| |
| What does the field contain? |
Indication of sub-series, like "A Goofy Look At..", "Goofy through History".
[ser:-] means the story is not in an subseries (even if it is stated elsewhere that it is).
The name of the subseries can be followed by a chapter comment between (), like:
[ser:Life of Scrooge(chapter 6B)]
|
| |
| Which log messages are related to this field? |
Log1 (serious)
287: Field ... contains an item (...) more than once
- Every name or abbreviation should occur only once.
289c: ser <...> should not be used here
- Posters cannot have [ser:]
Log2 (error)
453: Mismatch in ser:... with data from story file <...>
456: ser:... removed because story file says no ser!
834: subseries <...> is an ambiguous Italian name
Log3 (info)
291: ... <...> is not in the dbl file
- Every name or abbreviation should be mentioned in the legend (with the exception for one-time characters).
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.
452: ser:... not in story file (source ...)
|
| |
| Which CSV field(s) use this field? |
Table inducks_storysubseries, field storysubseriescomment
Table inducks_storysubseries, field subseriescode
|
| |
| How is the data used in the rest of Inducks? |
If an item was not in the subseries legend, it is added with status "unknown".
If the story field has no value, but an entry has a value, a log message ("...not in story file") is given.
If the story field has a value (but not '-'), and an entry has no value, the field is copied to the entry.
If the story field is not '-' and differs from an entry (not looking at the order of the subfields), a log message is given. |
| |
|
superref
| What should the field look like? |
Syntax: [superref:xx]
In FSB files: [supercodice:xx]
|
| |
| What does the field contain? |
A reference (story code) to another story, which is in fact the whole story. For instance, individual newspaper strips can have
a superref to an item that represents the newspaper sequence.
Superref should ONLY be used in newspaper story files (y.dbs, z.dbs), in w.dbi, and in FSB files. In all other files the field is ignored!
In the case of FSB, all information from the substories is transferred to the superstory.
There are 3 cases for the various fields:
- Value is taken from the first part only:
title,
hero,
desc,
Italian description,
pagel,
pubdate.
- Values are merged:
pages,
brokpg,
printedcode,
xref,
creatorref,
app,
xapp,
plot,
writ,
art,
ink,
ser,
creationdate,
comment.
- Values are ignored:
storycode,
descriptions other than English or Italian,
part (in storyitems).
brokpg are only merged if the denominators are the same. |
| |
| Which log messages are related to this field? |
Log1 (serious)
232: code <...> contains non-ASCII characters
- Only printable ASCII characters are allowed.
238: superref field only allowed in w.dbi and dbs files!
289b: superref <...> should not be used here
- Q-items cannot have [superref:]
310: Story in [superref:...] not found, is start or end date wrong?
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.
421: unresolved superref - super-story does not exist
840: Story has supercodice but no part number
842: Code of story in FSB does not start with an 'I'
Log3 (info)
422: substory has different ... <...> from superstory <...>
Log4 (pedantic)
237s: superref <...> is not a plausible story code
- If this error occurs, this storycode in the superref is ignored.
|
| |
| Which CSV field(s) use this field? |
Table inducks_storycodes, field codecomment
Table inducks_substory, field superstorycode
|
| |
| How is the data used in the rest of Inducks? |
| Several fields are copied from substories to the superstory. |
| |
|
|
|
|
