|
PROPAGATION FIELDS (PRICE, PUBL, ...)
| Which fields are explained on this page? |
inxforbidden
isslang
numbersarefake
pages (of an issue)
price
printrun
publ
size
|
| |
| What are these fields about? |
This page describes the propagation fields on header lines. These fields can be propagated from h1 to h2 and from h2 to h3.
In other words:
If a field is used on an h1 header, this means that all issues covered by this header have the same field value, unless this is overruled by this field on an h2 or h3 header.
If a field is used on an h2 header, this means that all issues covered by this header have the same field value, unless this is overruled by this field on an h3 header. |
| |
| In which input files are these fields used? |
On h1 header lines: in DBI files, w.dbi.
On h2 header lines: in DBI files, w.dbi.
On h3 header lines: in DBI files, w.dbi.
|
|
inxforbidden
| What should the field look like? |
Syntax: [inxforbidden:yes]
|
| |
| What does the field contain? |
| If this field is yes, new on-line indexes can not be done for the issue(s) covered by the header line. |
| |
| Which log messages are related to this field? |
|
None.
|
| |
| Which CSV field(s) use this field? |
Table inducks_issue, field inxforbidden
Table inducks_publication, field inxforbidden
|
| |
|
isslang
| What should the field look like? |
Syntax: [isslang:xx]
|
| |
| What does the field contain? |
The language of an issue.
If no language is used, the default language of the DBI file is taken. This is specified in countries.dbx, see defaultlanguage. |
| |
| Which checks are done? |
| The language should be mentioned in languages.dbx. See abbrev. |
| |
| Which log messages are related to this field? |
Log1 (serious)
110: unknown language <...>
113: No language defined on h1/h2/h3 line, and no default language in countries.dbx (assuming English)
Log2 (error)
114: more than one language <...> is not possible, only 1st language used
|
| |
| Which CSV field(s) use this field? |
Table inducks_publication, field languagecode
|
| |
| How is the data used in the rest of Inducks? |
| This information is used for filling the lang fields of the entries in that issue. |
| |
|
pages (of an issue)
| What should the field look like? |
Syntax: [pages:xxx]
|
| |
| What does the field contain? |
The number of pages of an issue.
At the moment only specified in some of the DBI files, if the indexer thinks it's useful information.
No checks are done that the field is an even positive number. |
| |
| Which log messages are related to this field? |
|
None.
|
| |
| Which CSV field(s) use this field? |
Table inducks_issue, field pages
|
| |
|
numbersarefake
| What should the field look like? |
Syntax: [numbersarefake:yes]
|
| |
| What does the field contain? |
| If yes, the issues in a series have no number. We may have added numbers in Inducks. |
| |
| Which log messages are related to this field? |
|
None.
|
| |
| Which CSV field(s) use this field? |
Table inducks_issuerange, field numbersarefake
Table inducks_publication, field numbersarefake
|
| |
|
price
| What should the field look like? |
Syntax: [price:CUR xxx.xxx(comment),CUR xxx.xxx(comment)] or [price:-] or [price:0] or [price:free]
|
| |
| What does the field contain? |
The price(s) of an issue.
CUR is a three-letter code following ISO_4217, and
xxx.xxx is a number with a dot ('.') as decimal separator (also numbers without '.' are allowed. We do NOT use commas!).
The value '0' or 'free' is used when the comic is free, and the value '-' means no price is printed.
Some examples:
[price:USD 4]
[price:EUR 1.95(in DE),EUR 2.50(in AT/CH),EUR 2.95(in BE/NL/LU)]
[price:YUN 20.50] -> Yugoslavian dinar used between 1990 and 1992
[price:FRF 5,CAD 3.5,free(subscribers)] -> French francs and Canadian dollars, free to subscribers
|
| |
| Which log messages are related to this field? |
Log2 (error)
296: Amount in price field (...) is not numeric (with a decimal point), like 99 or 99.99
- for the moment we do not log this
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).
|
| |
| Which CSV field(s) use this field? |
Table inducks_issue, field price
Table inducks_issueprice, field amount
Table inducks_issueprice, field comment
Table inducks_issueprice, field currency
Table inducks_issueprice, field sequencenumber
|
| |
|
printrun
| What should the field look like? |
Syntax: [printrun:xxx]
|
| |
| What does the field contain? |
The printrun of an issue.
Only specified in some of the DBI files, if the indexer thinks it's useful to list it. |
| |
| Which log messages are related to this field? |
|
None.
|
| |
| Which CSV field(s) use this field? |
Table inducks_issue, field printrun
|
| |
|
publ
| What should the field look like? |
Syntax: [publ:xx(xx),xx(xx)]
|
| |
| What does the field contain? |
| The publisher(s) of the issue(s). |
| |
| Which log messages are related to this field? |
|
None.
|
| |
| Which CSV field(s) use this field? |
Table inducks_publisher, field publishername
Table inducks_publishingjob, field publishingjobcomment
|
| |
|
size
| What should the field look like? |
Syntax: [size:xxx]
|
| |
| What does the field contain? |
The size of an issue, for instance in centimetres.
Only specified in some of the DBI files, if the indexer thinks it's useful to list it. |
| |
| Which log messages are related to this field? |
|
None.
|
| |
| Which CSV field(s) use this field? |
Table inducks_issue, field size
Table inducks_publication, field size
|
| |
|
|
|
|
