Field types
There are the following types of field which determine the maximum number of characters in each case:
Numeric field (
N
)
Contains a number automatically assigned; therefore the field length is irrelevant
Date field (
D
)
Contains a date automatically assigned; therefore the field length is irrelevant
255-character text field (
255c
)
Allows up to 255 bytes of text -- this corresponds to 255 characters (correspondingly fewer with double-byte characters)
16KB text field (
16KB
)
Allows up to 16 kilobytes of text -- this corresponds to 16384 characters (correspondingly fewer with double-byte characters)
In the following tables, the field type is indicated by the abbreviation in brackets.
The lengths specified are the
maximum possible
field lengths. In practice, you should not need to utilise those theoretical capacities to their limits. Please bear in mind that the amount of data entered must be transferred over an Internet connection and processed by your computer and the database.
Header fields
The header fields belong to a complete data record. They do not therefore relate to an individual language entry but to the overall semantic unit.
WebTerm shows header fields with the prefix
H:
in option lists (e.g.
H:Status
).
Table 11-8 lists all the header fields with a description of what they do and an example of what they contain.
Table 11-8: Header fields
|
Field name
|
Description
|
Type
|
Example
|
|
Data record
number
|
Number which uniquely identifies each data record.
Automatically filled in
Cannot be edited
|
N
|
2905
|
|
Project
|
Name of the project to which the data record belongs
|
16KB
|
TermStar User's Guide
|
|
Dictionary
|
Name of the dictionary to which the data record belongs.
This is entered automatically when the data record is created.
Cannot be edited
|
255c
|
STAR
|
|
Status
|
Status of the data record
Example: Information on the reliability or the status of the data record
|
16KB
|
Revised
|
|
Graphic/Video/Sound
|
Link field for embedded multimedia files
|
16KB
|
|
|
User1
|
Open field for the data record.
The field can be renamed
|
16KB
|
|
|
User2
|
as
User1
|
16KB
|
|
|
User3
|
as
User1
|
16KB
|
|
|
User4
|
as
User1
|
16KB
|
|
|
Created by
|
Name of the user who created the data record.
Automatically filled in
Cannot be edited
|
255c
|
Carry Onn
|
|
Created on
|
Date when the data record was created
Automatically filled in
Cannot be edited
|
D
|
29 May 2002, 16:30
|
|
Last change by
|
Name of the user who last changed the data record
Empty as long as the data record has not been changed
Automatically filled in
Cannot be edited
|
255c
|
Carry Onn
|
|
Last change on
|
Date when the data record was last changed
Empty as long as the data record has not been changed
Automatically filled in
Cannot be edited
|
D
|
8. February 2006, 13:12
|
|
Created or changed by
|
Name of the user who created the data record or who last changed it
Never empty -- contains at least the name of the user who created the data record
Automatically filled in
Cannot be edited
|
255c
|
Carry Onn
|
|
Created or changed on
|
Date on which the data record was created or last changed
Never empty -- contains at least the date when the data record was created
Automatically filled in
Cannot be edited
|
D
|
8. February 2006, 13:12
|
|
Remark
|
General remarks on the entire data record
|
16KB
|
|
|
Subject
|
Subject(s) of the data record
|
16KB
|
Data processing
|
Language fields
The language fields relate to
all
entries
of a
language. You can, for example, use these fields to create a single description in English for several English entries in a data record.
Table 11-9 lists all the language fields with a description of what they do and an example of what they contain.
Table 11-9: Language fields
|
Field name
|
Description
|
Type
|
Example
|
|
Language
|
3-letter language code (see here)
Automatically filled in
Cannot be edited
|
16KB
|
ENG
|
|
Info1
|
Information which applies to all the entries in this language
Example: Descriptive text for
all
entries
in a
language
|
16KB
|
A field in a dialog box.
|
|
Info2
|
As
Info1
Example: Information on the source of the description
|
16KB
|
Styleguide 8.2.06
|
Entry fields
The entry fields record the data for each entry. WebTerm shows entry fields with the prefix
E:
in option lists (e.g.
E:Gender
).
Table 11-10 lists all the entry fields with a description of what they do and an example of what they contain.
Table 11-10: Entry fields
|
Field name
|
Description
|
Type
|
Example
|
|
Term
|
Term of the entry
WebTerm sorts the dictionary entries according to the contents of this field.
|
16KB
|
TermStar
|
|
Language
|
3-letter language code of the language of the entry (see here)
Automatically filled in
Cannot be edited
|
16KB
|
ENG
|
|
Created by
|
Name of the user who created the entry.
Automatically filled in
Cannot be edited
|
255c
|
Carry Onn
|
|
Created on
|
Date when the entry was created
Automatically filled in
Cannot be edited
|
D
|
29 May 2002, 16:30
|
|
Last change by
|
Name of the user who last changed the entry
Empty as long as the entry has not been changed
Automatically filled in
Cannot be edited
|
255c
|
Carry Onn
|
|
Last change on
|
Date of the last change made to the entry
Empty as long as the entry has not been changed
Automatically filled in
Cannot be edited
|
D
|
8. February 2006, 13:12
|
|
Created or changed by
|
Name of the user who created the entry or who last changed it
Never empty -- contains at least the name of the user who created the entry
Automatically filled in
Cannot be edited
|
255c
|
Carry Onn
|
|
Created or changed on
|
Date on which the entry was created or last changed
Never empty -- contains at least the date when the entry was created
Automatically filled in
Cannot be edited
|
D
|
8. February 2006, 13:12
|
|
Context
|
Context of the term
|
16KB
|
Terminology management
|
|
Context source
|
Source of the context
|
16KB
|
RefGuide
|
|
Part of speech
|
Part of speech of the entry
|
16KB
|
Noun
|
|
Gender
|
Gender of the entry
|
16KB
|
n.
|
|
Grammatical information
|
Grammatical features of the entry
|
16KB
|
Proper name
|
|
Status
|
Status of the entry
Example: Information on the reliability or the status of the entry
|
16KB
|
Revised
|
|
Data source
|
Source of the entry
|
16KB
|
STAR Terminology Department
|
|
Attributes
|
Attributes for the entry
|
16KB
|
New
|
|
Remark
|
General comments on the entry
|
16KB
|
Note the spelling!
|
|
Subject
|
Subject(s) of the entry
|
16KB
|
Translation, software
|
|
Phonetical information
|
Information on the pronunciation of the term
If necessary, the field can be associated with a phonetic transcription in the output
|
16KB
|
|
|
Cross-reference
|
Field for cross-reference
Examples:
Cross-reference to a related entry
Cross-reference to an Internet address
|
16KB
|
Transit
|
|
Definition
|
Definition of the entry
|
16KB
|
STAR's Translation Memory Tool
|
|
Source of the definition
|
Source of the definition
|
16KB
|
STAR brochure 2005
|
|
User1
|
Open field for the entry
The field can be renamed
|
16KB
|
|
|
User2
|
as
User1
|
16KB
|
|
|
User3
|
as
User1
|
16KB
|
|
|
User4
|
as
User1
|
16KB
|
|
Fields for subentries
Each subentry you append to an entry has its own fields.
Table 11-11 lists all the fields for subentries with a description of what they do and an example of what they contain.
Table 11-11: Fields for subentries
|
Field name
|
Description
|
Type
|
Example
|
|
Term
|
Term of the subentry
WebTerm sorts the dictionary subentries according to the contents of this field.
|
16KB
|
TS
|
|
Grammatical information
|
Information on grammatical features of the subentry
Please note: Subentries of the type User index
do not
have a
Grammatical information
field.
|
16KB
|
Abbr.
|
|
Status
|
Status of the subentry
Example: Information on the reliability or the status of the subentry
|
16KB
|
Revised
|
