This is Bolderbast.Inducks.org, part of the inducks.org website.
previous page | next page
Main
How to index
   Beginners
   More detail
   Programmers
   Scanners
   File formats
   ISV files
   Field reference guide
     Overview
       DBI entry fields
       DBI header fields
       DBS fields
       Extra DBS fields for movies
       DBS header fields
       DBL fields
       Other fields
       Automatic fields
         lang
         country
         differentversion
         error
         herostatus
         internal
         inx
         issuecode
         owner
         pscode
         pubdate
         rp-xx
         westernl
         xrefd
         error
         issueseriescode
         issuevolumecode
         owner
         westernl
         key
         onlystory
         universemember
         xx
         pscode
         xrefd
         fullname
         key
         studiomember
         error
         herostatus
         internal
         owner
         pscode
         rp-xx
         superrefd
         t-xx
         xrefd
     Output overview
Credits/links
Producktion
Index of indexes
Various

ehOwner (owner)

In which input files is this field used?
The field is generated automatically, so not in an input file.
Where is the data coming from?
The eoOwner field in owner.dbx (this field is not documented separately).
What does the field contain?
An indication that an issue is owned. This is only used in private versions of Inducks.

Next is a detailed description of how to get the "owner" field to work. It is very technical stuff. If you don't know anything about DIZNI, please skip the rest of this page!

It basically works as follows:

1. A private DIZNI user creates a file owner.dbx containing
   the issues he owns.

2. He runs DIZNI with an extra option so it will add the owner information
   to Inducks.

3. DIZNI will determine the "owner" of every issue, and also of every story.

4. DIZNI adds an "owned"-marker in the standard output files.

5. DIZNI can make listings of owned or non-owned stories.

6. DIZNI can make a listing of all owned issues.

Note that this feature is meant for private users (like myself).
The public Inducks files will not contain any "owner" information.


Next are the details for every step.

1. A private DIZNI user creates a file containing the issues he owns.

The file's name must be owner.dbx.
The syntax of the file is:
country ^ issuecode ^ owner

- the file has no header line.
- country = 2-char abbreviation.
- issuecode = as used in the DBI files on h3 lines. Double spaces can be removed (so no
need to count spaces!).
- owner = anything. DIZNI will just copy the information.
DIZNI only uses the fact whether or not the field is empty.
- the order of the lines in the file is not important.

2. He runs DIZNI with an extra option so it will add the owner information to Inducks.

This is easily done by adding "-o" to the "dizni -xx" line in the batchfiles.

3. DIZNI will determine the "owner" of every issue, and also of every story.

So all INE and INS files will have an extra "owner" field (also for
headers!). The contents of the owner field is simply copied. If a story is
owned more than once, only one owner field is stored.

If an issue in "owner.dbx" can't be found in the Inducks database, DIZNI
will give a log message.

4. DIZNI adds an "owned"-marker in the standard output files.

In the standard output files, reprint information can have a #,
indicating that the specific reprint of the story is owned.

5. DIZNI can make listings of owned or non-owned stories.

6. DIZNI can make a listing of all owned issues.

Which CSV field(s) use this field?
The field owner in table inducks_issue
This page was generated on 2008-04-18 by DVEGEN 4.8d © Harry Fluks 2003.
For more information contact Harry Fluks (hfl at inducks.org - replace the at)