This is Bolderbast.Inducks.org, part of the inducks.org website.

VARIOUS H2 HEADER FIELDS (NOTINOUTPUT, ...)

Which fields are explained on this page?
circulation
issuerangecode
notinoutput
 
In which input files are these fields used?
On h2 header lines: in DBI files, w.dbi.

circulation

What should the field look like?
Syntax: [circulation:xxx]
 
What does the field contain?
See also the h1 field.
 
Which log messages are related to this field?
None.
 
Which CSV field(s) use this field?
Table inducks_issuerange, field circulation
 

issuerangecode

What should the field look like?
Syntax: fixed position, or [entrycode:xx] (yes, entrycode)
 
What does the field contain?
A code indicating the issue volume (a.k.a. issue range).
 
Which checks are done?
The codes in a DBI file should be in exact alphabetical order.
An h2 issuerangecode should match (i.e. start with) the code of the corresponding h1 header, the publicationcode.
 
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.
 
Which CSV field(s) use this field?
Table inducks_issue, field issuerangecode
Table inducks_issuerange, field issuerangecode
Table inducks_log, field logkey
 

notinoutput

What should the field look like?
Syntax: [notinoutput:yes]

The tag [notinoutput:] currently occurs (approximately) 54 times in the input files.
 
What does the field contain?
An indication that the h2 header line is only to be used for the propagation of fields like size and publisher.
This indication can also be used for h1 lines, but only on very few occasions!
 
Which log messages are related to this field?
None.
 
Which CSV field(s) use this field?
 

   
<< Previous page (This page was generated by AweGen 5.7 on 2017-07-08) Next page >>