|
CREDIT FIELDS (WRIT, ART, ...)
| Which fields are explained on this page? |
art
creatorref
ink
plot
writ
|
| |
| What are these fields about? |
These fields indicate persons who contributed to a story, or who are the subject of a story.
We don't include minor credits here (translating, lettering, colouring), because they are often different for different publications of a story.
Every person name or abbreviation must be mentioned in the persons legend, except in non-Disney or non-comics, like movies and articles.
The persons legend contains alternative names for the same person (like pseudonyms, misspellings) to make sure the person has the same name everywhere, as much as possible.
If a person was not in the legend, it is added with status "unknown".
If a DBS field has no value, but a DBI entry has a value, a log message ("...not in story file") is given.
(Unless one of the fields changes, cut, idc was used, or the field contains a '?'.)
If a DBS field has a value, and a DBI entry has no value, the field is copied to the DBI entry.
If a DBS field's contents differ from a DBI entry (not looking at the order of the persons), a log message is given.
(Unless one of the fields changes, cut, idc was used.)
If one of the fields changes, cut, idc was used in a DBI entry,
and a credit is different, a comment about the original credit is added to the DBI entry. |
| |
| In which input files are these fields used? |
On story lines: in DBS files, FSB files, y.dbs and z.dbs, yzsuper.dbs, w.dbi, DBI files, DPG CSV files.
On entry lines: in DBI files, w.dbi.
|
|
art
| What should the field look like? |
Syntax: fixed position, or [art:xx(xx),xx(xx)]
In FSB files: Third line, between the 2nd and 3rd '/'. Full name or surname will automatically be converted to Inducks abbreviation.
|
| |
| What does the field contain? |
Name (or abbreviation) of the artist of a story.
More than one person can be mentioned.
If empty: artist unknown.
If "-": the story was not drawn (or an text piece or article has no illustrations).
If uncertain, a '?' follows the name.
If a person's work was used, but was actually made for a different purpose, a ')' is added. For example: CB).
If the ink field has a value, then the art field contains the person who did the pencils only. |
| |
| 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.
299: ... <...> is not in the dbl file and suspiciously short
Log2 (error)
215: ink field is nonempty and not '-' (...) while art field is '-'
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.
450: ...:... not in story file (source ...)
451: ...:... overruled by data from story file <...>
|
| |
| Which CSV field(s) use this field? |
Table inducks_statpersoncharacter, field personcode
Table inducks_statpersoncountry, field personcode
Table inducks_statpersonperson, field copersoncode
Table inducks_statpersonperson, field personcode
Table inducks_statpersonstory, field personcode
Table inducks_storyjob, field doubt
Table inducks_storyjob, field indirect
Table inducks_storyjob, field personcode
Table inducks_storyjob, field plotwritartink
Table inducks_storyjob, field storyjobcomment
Table inducks_storyversion, field artsummary
|
| |
|
creatorref
| What should the field look like? |
Syntax: [creatorref:xx(xx),xx(xx)]
|
| |
| What does the field contain? |
Name (or abbreviation) of a creator who is mentioned in a story or article, but didn't contribute to it himself.
More than one person can be mentioned. |
| |
| 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.
299: ... <...> is not in the dbl file and suspiciously short
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.
450: ...:... not in story file (source ...)
451: ...:... overruled by data from story file <...>
|
| |
| Which CSV field(s) use this field? |
Table inducks_storyjob, field personcode
Table inducks_storyjob, field plotwritartink
Table inducks_storyjob, field storyjobcomment
Table inducks_storyversion, field creatorrefsummary
|
| |
|
ink
| What should the field look like? |
Syntax: fixed position, or [ink:xx(xx),xx(xx)]
In FSB files: Third line, behind the 3rd '/'. Full name or surname will automatically be converted to Inducks abbreviation.
|
| |
| What does the field contain? |
Name (or abbreviation) of the inker of a story.
More than one person can be mentioned.
If empty: Inker is equal to art.
If "-": the story was not inked (only pencilled, or not drawn at all).
If unknown (while the artist is known): "?".
If uncertain, a '?' follows the name.
If a person's work was used, but was actually made for a different purpose, a ')' is added. For example: CB).
|
| |
| 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.
299: ... <...> is not in the dbl file and suspiciously short
Log2 (error)
215: ink field is nonempty and not '-' (...) while art field is '-'
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.
450: ...:... not in story file (source ...)
451: ...:... overruled by data from story file <...>
|
| |
| Which CSV field(s) use this field? |
Table inducks_statpersoncharacter, field personcode
Table inducks_statpersoncountry, field personcode
Table inducks_statpersonperson, field copersoncode
Table inducks_statpersonperson, field personcode
Table inducks_statpersonstory, field personcode
Table inducks_storyjob, field doubt
Table inducks_storyjob, field indirect
Table inducks_storyjob, field personcode
Table inducks_storyjob, field plotwritartink
Table inducks_storyjob, field storyjobcomment
Table inducks_storyversion, field inksummary
|
| |
|
plot
| What should the field look like? |
Syntax: fixed position, or [plot:xx(xx),xx(xx)]
In FSB files: Third line, before the 1st '/'. Full name or surname will automatically be converted to Inducks abbreviation.
|
| |
| What does the field contain? |
Name (or abbreviation) of the creator who made the plot (but not the script) of a story.
More than one person can be mentioned.
If empty: Plot is equal to writ.
If unknown (while the writer is known): "?".
If uncertain, a '?' follows the name.
If a person's work was used, but was actually made for a different purpose, a ')' is added. For example: CB).
|
| |
| 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.
299: ... <...> is not in the dbl file and suspiciously short
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.
450: ...:... not in story file (source ...)
451: ...:... overruled by data from story file <...>
|
| |
| Which CSV field(s) use this field? |
Table inducks_statpersoncharacter, field personcode
Table inducks_statpersoncountry, field personcode
Table inducks_statpersonperson, field copersoncode
Table inducks_statpersonperson, field personcode
Table inducks_statpersonstory, field personcode
Table inducks_storyjob, field doubt
Table inducks_storyjob, field indirect
Table inducks_storyjob, field personcode
Table inducks_storyjob, field plotwritartink
Table inducks_storyjob, field storyjobcomment
Table inducks_storyversion, field plotsummary
|
| |
|
writ
| What should the field look like? |
Syntax: fixed position, or [writ:xx(xx),xx(xx)]
In FSB files: Third line, between the 1st and 2nd '/'. Full name or surname will automatically be converted to Inducks abbreviation.
|
| |
| What does the field contain? |
Name (or abbreviation) of the writer of a story, or in case of a cover/illustration: the person who gave the idea.
More than one person can be mentioned.
A writer can be doing the script of a story only, while someone else did the plot. In this
case, the person who did the plot is mentioned in the plot field.
If empty: writer unknown.
If uncertain, a '?' follows the name.
If a person's work was used, but was actually made for a different purpose, a ')' is added. For example: CB).
|
| |
| 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.
299: ... <...> is not in the dbl file and suspiciously short
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.
450: ...:... not in story file (source ...)
451: ...:... overruled by data from story file <...>
|
| |
| Which CSV field(s) use this field? |
Table inducks_statpersoncharacter, field personcode
Table inducks_statpersoncountry, field personcode
Table inducks_statpersonperson, field copersoncode
Table inducks_statpersonperson, field personcode
Table inducks_statpersonstory, field personcode
Table inducks_storyjob, field doubt
Table inducks_storyjob, field indirect
Table inducks_storyjob, field personcode
Table inducks_storyjob, field plotwritartink
Table inducks_storyjob, field storyjobcomment
Table inducks_storyversion, field writsummary
|
| |
|
|
|
|
