|
DESC FIELDS (DESC, DESC-XX)
desc
| What should the field look like? |
Syntax: [desc:xxx]
|
| |
| What does the field contain? |
| A short English description of the story. |
| |
| Which log messages are related to this field? |
Log3 (info)
432: Story has no desc. Desc in ...: ...
- This message is not given for I-coded stories (FSB).
470: desc:... ignored because the story already has it as a title
Log4 (pedantic)
474: Different descs <...> and <...>
|
| |
| Which CSV field(s) use this field? |
Table inducks_storydescription, field desctext
Table inducks_storyversion, field keywordsummary
|
| |
| How is the data used in the rest of Inducks? |
The Dizni program tries to compare various descriptions from various DBI files.
It gives warning messages if the descriptions don't seem to match.
If the story's desc was empty, the descriptions from the various DBI indexes are concatenated into one large desc for the story. |
| |
|
desc-xx
| What should the field look like? |
Syntax: [desc-XX:xxx] (where XX can be any valid language code except "en")
In FSB files: Fourth line, between the 1st and 2nd '/'. Only Italian descriptions are possible there.
|
| |
| What does the field contain? |
A description of a story in the specified language.
We recommend to put descriptions in non-English languages in a file that is maintained by someone who can read the language.
The most logical place for non-English descs is in a DBI file.
|
| |
| Which log messages are related to this field? |
|
None.
|
| |
| Which CSV field(s) use this field? |
Table inducks_storydescription, field desctext
Table inducks_storydescription, field languagecode
Table inducks_storyversion, field keywordsummary
|
| |
| How is the data used in the rest of Inducks? |
The contents from DBI desc-xxs are copied to the corresponding DBS desc-xx.
The "main language" of a country is defined by the field defaultlanguage in the country table. |
| |
|
|
|
|
