|
VARIOUS H1 HEADER FIELDS (CATEGORY, ALTNAMES, ...)
altnames (of a publication)
| What should the field look like? |
Syntax: [altnames:xxx,yyy]
|
| |
| What does the field contain? |
| One or more alternative names of the publication. For instance used in alphabetic lists. |
| |
| Which log messages are related to this field? |
|
None.
|
| |
| Which CSV field(s) use this field? |
Table inducks_publicationname, field publicationname
|
| |
|
category
| What should the field look like? |
Syntax: [category:xxx,yyy]
|
| |
| What does the field contain? |
| One or more category names. Used to group publications. |
| |
| Which log messages are related to this field? |
|
None.
|
| |
| Which CSV field(s) use this field? |
Table inducks_publicationcategory, field category
|
| |
|
circulation
| What should the field look like? |
Syntax: [circulation:xxx]
|
| |
| Which log messages are related to this field? |
|
None.
|
| |
| Which CSV field(s) use this field? |
Table inducks_publication, field circulation
|
| |
|
publicationcode
| What should the field look like? |
Syntax: fixed position, or [entrycode:xx] (yes, entrycode)
|
| |
| What does the field contain? |
| A code indicating the publication (series of issues). |
| |
| 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 issuenumber
Table inducks_issue, field publicationcode
Table inducks_issuerange, field publicationcode
Table inducks_log, field logkey
Table inducks_publication, field publicationcode
Table inducks_publicationcategory, field publicationcode
Table inducks_publicationname, field publicationcode
Table inducks_publicationurl, field publicationcode
|
| |
|
|
|
|
