Term base entry information
Updated over a week ago

With LingoHub's new term base, a lot of information can be added to terms. This article describes, in depth, which information can be added to a term base entry.

## General information

General information

* **Name**: Add your new term here.

* **Language**: Select the term language from the drop-down menu. Or type to search for the language you are looking for.

* **Case sensitive**: Select from the following options.

`Yes`: Sets your term to case-sensitive. Terms will only be recognized if they exactly match the source.

**Example**: Your term is AT (language code for Austria), At, aT, or at will not be recognized as term.

`Permissive`: Your term is case-sensitive for capital letters, but not for lower case letters.

**Example**: Your term is At, then At and AT will be recognized as term, however, at and aT will not be recognized.

`No`: Sets your term to not case-sensitive. Terms will always be recognized, regardless of capitalization.

|| **Note**: The default value is `Yes`.

||| For imported terms, please ensure to set the case-sensitivity to No. Only then will your terms correctly be recognized. Often, external terms contain upper case letters at the beginning.

* **Description**: Add a description to your term. This will add more information on your term and can help translators when localizing your software. You can also specify the context in the additional information section.

* **Matching**: Select from the following options:

`Fuzzy`: Matches will be considered, regardless if it is a prefix, or suffix match.

**Example**: Your term is ball, then snowball and ballpark will be matched.

`Prefix`: Matches with the identical prefix will be considered.

**Example**: Your term is ball, then ballpark will be matched, but snowball will not be matched.

`Exact`: Only identical terms will be found.

**Example**: Your term is ball, then ball will be matched, but balls, ballpark, snowball will not be matched.

`Custom`: Matches will be considered, depending on predefined wildcards. You can use a pipe "|" and an asterisk "*" as wildcards. Pipes are used to define a part in a word that varies, e.g., for languages that are inflected, like German. The ending of a word will change based in grammar. You can also use an asterisk to define that anything afterwards should be matched.

**Example**: Your German term is Schwimmb|ad, then Schwimmbad and Schwimmbäder will be matched but Schwimmweste will not be matched.

**Example**: Your German term is Schwimm*, then any of the above-mentioned terms would be matched.

|| **Note**: The default value is `Prefix`.

* **Image**: Upload a context image for your term.

* **Translatable**: Select whether your term is translatable or not.

|| Note: If you already have existing translations for your terms in different target languages, you can add these in the advanced information section. This is step is optional.

## Advanced information (optional)

* **Context**: Add more context to your term. In addition to a description, this helps translators. Context can vary from more elaborative descriptions to example sentences and more.

* **Usage status**: Define the usage status of your term. You can select from four options.

`Preferred`: The term should be used in this form.

`Admitted`: The term can be used in this form.

`Not recommended`: The term should not be used in this form.

`Obsolete`: The term is obsolete and must not be used.

* **Part of speech**: Define if the term is either noun, verb, adjective, adverb, proper noun, or other.

* **Grammatical number**: Define if the term is either singular or plural form.

* **Grammatical gender**: Define if the term is either masculine, feminine, neuter, or other.

* **Term type**: Define if the term is either full form, acronym, abbreviation, short form, variant, or phrase.

* **Translations**: Add already existing translations for your term in this section. This option is only available, if your term is translatable.

Did this answer your question?