The Header Record
The inclusion of this record is mandatory. There is only one such record, and it must appear as the first record in the file. The values of this record provide field names for the records that follow. These field names are used by WorldServer to identify the meaning of the field data. The ordering of the field names is not specified, but of course, the ordering must be consistent with the field values in subsequent records.
There are some well-known field names. These correspond to WorldServer system defined attributes. Some are mandatory; others are optional with default values provided. These are described in the table below.
| Name | Meaning | Required | Default |
|---|---|---|---|
| Language | The Locale associated with the term value. | Yes | N/A |
| Term | The value (text) of the term. | Yes | N/A |
| Created On | Creation time of the term. | No | Current timestamp |
| Created By | User who created the term. | No | Current user |
| Modified On | Modification time of the term. | No | Current timestamp |
| Modified By | User who modified the term. | No | Current user |
| Created On-Entry | Creation time of the term entry. | No | Current timestamp |
| Created By-Entry | User who created the term entry. | No | Current user |
| Modified On-Entry | Modification time of the term entry. | No | Current timestamp |
| Modified By-Entry | User who modified the term entry. | No | Current user |
All other field names are assumed to be user-defined within WorldServer. Because user-defined attributes on term and term entries can have the same name, by convention all field names for term entry attributes must append a suffix of -Entry. For example, if there is a user-defined term entry attribute named MyAttribute then the corresponding field name in the header record must be MyAttribute-Entry. This is true regardless of whether or not there is a term attribute defined with the same name.