|
CHANGE FIELDS (CHANGES, PART, IDC, ...)
changes
| What should the field look like? |
Syntax: [changes:xxx] or [changes:-]
|
| |
| What does the field contain? |
Changes in a (re)print of a story, as compared to the original.
Very minor changes are not listed this way. For that we have the minorchanges field.
When a newspaper strip is printed in a comic, it's very usual that the layout has changed. In such cases, if nothing was changed, we use [changes:-].
Though it can be detected automatically that a story was changed if the page count differs, we prefer
an explicit mention of this in a changes or cut field, to better detect possible errors. |
| |
| Which log messages are related to this field? |
|
None.
|
| |
| Which CSV field(s) use this field? |
Table inducks_entry, field changes
|
| |
| How is the data used in the rest of Inducks? |
| If changes is filled in (and not '-'), lots of automatic copying of data from story to entry and vice versa is NOT performed. |
| |
|
cut
| What should the field look like? |
Syntax: [cut:xx] or [cut:xx(explanatory text)] or [cut:yy/zz(explanatory text)] or [cut:xx yy/zz(explanatory text)], where xx, yy, and zz are numbers
|
| |
| What does the field contain? |
The number of missing pages in a reprint.
While the page count of a story is divided over the fields pages and brokpg,
the cut field can contain both entire and broken page count (with one space inbetween).
This field was introduced in 2013, and is not very much used yet. Differences in page count are usually stated in the field changes. |
| |
| Which log messages are related to this field? |
Log1 (serious)
256: cut <...> should be a number or in the form yy/zz, or xx yy/zz
|
| |
| Which CSV field(s) use this field? |
Table inducks_entry, field cut
|
| |
|
idc
| What should the field look like? |
Syntax: [idc:xxx]
|
| |
| What does the field contain? |
idc = identification (un)certainty.
This field should be nonempty if the story code is not 100% sure. The exact contents of the idc field is not used.
The idc field must only be used if a valid story code is used. (This is currently not checked.) |
| |
| Which log messages are related to this field? |
|
None.
|
| |
| Which CSV field(s) use this field? |
Table inducks_entry, field identificationuncertain
|
| |
| How is the data used in the rest of Inducks? |
| If idc is filled in, lots of automatic copying of data from story to entry and vice versa is NOT performed. |
| |
|
minorchanges
| What should the field look like? |
Syntax: [minorchanges:xxx]
|
| |
| What does the field contain? |
Minor changes in a (re)print of a story, as compared to the original.
Major changes should go in the changes field or the cut field.
Examples of minor changes are: splash panel enlarged, bottom rows of panels trimmed a few millimetres, text balloons changed in shape. |
| |
| Which log messages are related to this field? |
|
None.
|
| |
| Which CSV field(s) use this field? |
Table inducks_entry, field minorchanges
|
| |
|
mirrored
| What should the field look like? |
Syntax: [mirrored:yes]
|
| |
| What does the field contain? |
The item was mirrored in this print.
Only the first character of the contents of the field is used ('y'). All other characters and values are ignored.
Values starting with Y, j, J, or 1 are also regarded 'yes'. |
| |
| Which log messages are related to this field? |
|
None.
|
| |
| Which CSV field(s) use this field? |
Table inducks_entry, field mirrored
|
| |
|
missing
| What should the field look like? |
Syntax: [missing:xxx]
|
| |
| What does the field contain? |
The amount of panels of the original story that are missing in a reprint, but that don't affect the page count of the story.
Usually the panels are replaced by a text caption ("what happened so far") or different artwork.
If an entire row is replaced, but we don't know how many panels were in the original, we use 'r'. |
| |
| Which log messages are related to this field? |
Log1 (serious)
255: missing panels <...> should be a number or 'r'
|
| |
| Which CSV field(s) use this field? |
Table inducks_entry, field missingpanels
|
| |
|
part
| What should the field look like? |
Syntax: fixed position, or [part:xxx]
|
| |
| What does the field contain? |
| The part of a sequence. One or more digits, or the text "final". |
| |
| Which log messages are related to this field? |
Log1 (serious)
254: part field <...> should be a number or 'final'
|
| |
| Which CSV field(s) use this field? |
Table inducks_entry, field part
|
| |
| How is the data used in the rest of Inducks? |
| If the part field is filled in, the page count may differ from the original. |
| |
|
|
|
|
