...
TermWeb field | Memsource field |
---|---|
Term fields | |
See languages section after this table | Language |
No exact match, we can match custom field value or TBX | Status |
Usage status (TBX) – value | Preferred |
Usage status (TBX) – value | Forbidden |
Usage status (TBX) – value | Preferred Forbidden |
Usage status (TBX) – other values including custom values | Will be added to Note as |
No exact match, we can map custom field value or TBX | Case sensitive |
No exact match, we can map custom field value or TBX | Match type |
Usage note (TBX) | Usage |
Part of speech (TBX)
Users may add their own values too | Part of speech
All other non-matching values will be added to Note |
Gender (TBX)
Users may add their own values too | Gender
All other non-matching values will be added to Note |
Grammatical number (TBX)
Users may add their own values too | Number
All other non-matching values will be added to Note |
No exact match, we can map custom field value | Short translation |
Term type (TBX)
Users may add their own values too | Term type
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) | |
All other TBX or custom fields | Will be added to Note |
Concept fields | |
Definition (TBX) | Definition |
Custom field with ExportSettings mapping to Memsource type | Concept note |
Section | Can’t be mapped and Memsource inserts it into Term’s Will be added to Concept note |
Domains | Domain/Subdomain Not implemented. |
Custom field with ExportSettings mapping to Memsource type | URL |
All other TBX or custom fields | Will be added to Concept note |
Languages
Memsource supports language tags with separators as dash ‘-' and underscore '_’.
...