Page Comparison

Term fields

See languages section after this table

Language <langSet xml:lang="??">

No exact match, we can match custom field or TBX
(Picklist with values Approved and New)
Set export field name to status

Status <termNote type=status
possible values are: Approved or New

Usage status (TBX) – value preferred

Preferred <termNote type=preferred
possible values are: true or false

Usage status (TBX) – value notRecommended

Forbidden <termNote type=forbidden
possible values are: true or false

Usage status (TBX) – value obsolete

Forbidden <termNote type=forbidden
possible values are: true or false
Also added to Note as Acceptability: obsolete

Usage status (TBX) – other values including custom values

Will be added to Note as Acceptability: other value

No exact match, we can map custom field or TBX
(Picklist with values True and False)
Set export field name to caseSensitive

Case sensitive <termNote type=caseSensitive
possible values are: true or false

No exact match, we can map custom field or TBX
(Picklist with values True and False)
Set export field name to exactMatch

Match type <termNote type=exactMatch
possible values are: true or false

Usage note (TBX)
Text field, max length: customizable from 1 to 65535

Usage <termNote type=usageNote
Text field, max length: ~7700

Part of speech (TBX)
TBX values:

• noun

• verb

• adjective

• adverb

• properNoun

• other

Users may add their own values too

Part of speech <termNote type=partOfSpeech
Not all TBX values supported

• NOUN

• VERB

• ADJECTIVE

• ADVERB

All other non-matching values will be added to Note

Gender (TBX)
TBX values:

• neuter

• masculine

• feminine

• otherGender

Users may add their own values too

Gender <termNote type=grammaticalGender
Not all TBX values supported

• NEUTRAL

• MASCULINE

• FEMININE

All other non-matching values will be added to Note

Grammatical number (TBX)
TBX values:

• singular

• plural

• dual

• massNoun

• otherNumber

Users may add their own values too

Number <termNote type=grammaticalNumber
Not all TBX values supported

• SINGULAR

• PLURAL

All other non-matching values will be added to Note

No exact match, we can map custom field value

Short translation <termNote type=shortTranslation
possible values are: true or false

Term type (TBX)
TBX values:

• fullForm

• acronym

• abbreviation

• shortForm

• variant

• phrase

Users may add their own values too

Term type <termNote type=termType
Phrase values:

• FULL_FORM

• ACRONYM

• ABBREVIATION

• SHORT_FORM

• VARIANT

• PHRASE

All other custom values will be added to Note

Note

By default Memsource adds here all fields which are not matching other fields (including concept level fields)
Xml element: <note/>

All other TBX or custom fields

Will be added to Note

Concept fields

Definition (TBX)

Definition <descrip type=conceptDefinition

Custom field with ExportSettings mapping to Memsource type
Set export field name to conceptNote

Concept note <descrip type=conceptNote

Section

Will be added to Concept note

Domains

Domain/Subdomain Not implemented.
By request we can implement it but with limitations to map only two levels of TermWeb domains.
Memsource expects <descrip/> elements with type conceptDomain or conceptSubdomain

Custom field with ExportSettings mapping to Memsource type
Set export field name to conceptUrl

URL <descrip type=conceptUrl

All other TBX or custom fields

Will be added to Concept note