GS 

When you created the termbase and defined the fields, you had to select the type of the field. If you define your field "Bild" as type "Multimedia file", you will be able to insert a picture into this field. 
But you need to do this when you create the termbase. 
Here is an example of the definition of a termbase with a picture type field:

Thank you very much for your explanation.

I've created a new termbase and added what you call type (Zahl, Ja/Nein, Datum, Pickliste, Multimedia).
Now I have a new problem. When I go to "add field" it only shows the following four fields:

Auftragsnummer
Boolescher Wert Ja/Nein
Datum
Kontext

These are missing:

Bild
Definition
Quelle
Genus

What should I do if I want to add an image?

Also the descriptive fields of the second group would be more important.

Kind regards,

GS

This depends on where you defined the field you want to add. A termbase entry is structured into three hierarchical levels: entry level, index or language level and term level. 
Here is an example:



It is very important that you define the fields on the correct level when you create the termbase. The illustration field, in my opinion, belongs to the entry level because it is language independent. 
Please check your termbase definition to see if it fits these guidelines. 
Once your definition is OK, when you want to add a field, e.g. a picture, you need to do this at the right level, in this case at the entry level.

Sorry, but creating termbases is a bit more complex than Translation Memories, because the structure can be personalized. It requires some preliminary knowledge about terminology.

Good luck!
Walter

I did it this way:

I did it this way:

I did it this way:

If you click on "Feld hinzufügen" at the top, below "Eintrags-ID", you will see the field "Bild" and be able to add your picture. 
The function "Feld hinzufügen" is available at all 3 levels, you need to choose the one where your field is located.

Found it! Thank you very much!

The definition would be inserted just below. Is it perhaps wrong there? I should perhaps insert the definition of the term in both languages? Then it should be inserted under "Termebene"?
Also, I can't paste the defnition via copy/paste. Is there perhaps a keyboard shortcut for this?

I would put the definition at the Index level (Sprachebene). If you want a separate definition per language, you may in addition also put it at the term level.

Also, I would remove "Quelle" from the entry level. This field only makes sense at the term level because you want to say where you found the translation of that term in that specific language. 
In addition, I can't see any use for the fields "Datum", "Auftragsnummer" and "Boolescher Wert". What purpose should they fulfil? The same applies to "Genus", which may be useful, provided the software is able to adapt terms to plural/male/female, which MultiTerm does not. 

"Kontext" is a very useful field, but there is no need to attach a "Quelle" to it.

Finally, I strongly suggest to add a picklist field called "Status" with values such as "Approved", "Forbidden", "Deprecated", etc. This will allow you to also store terms that should not be used in the translation (especially in conjunction with the Terminology Verification function of Studio).

Copy-pasting of text into a field worked fine for me (CTRL-C + CTRL-V).

I would put the definition at the Index level (Sprachebene). If you want a separate definition per language, you may in addition also put it at the term level.

Also, I would remove "Quelle" from the entry level. This field only makes sense at the term level because you want to say where you found the translation of that term in that specific language. 
In addition, I can't see any use for the fields "Datum", "Auftragsnummer" and "Boolescher Wert". What purpose should they fulfil? The same applies to "Genus", which may be useful, provided the software is able to adapt terms to plural/male/female, which MultiTerm does not. 

"Kontext" is a very useful field, but there is no need to attach a "Quelle" to it.

Finally, I strongly suggest to add a picklist field called "Status" with values such as "Approved", "Forbidden", "Deprecated", etc. This will allow you to also store terms that should not be used in the translation (especially in conjunction with the Terminology Verification function of Studio).

Copy-pasting of text into a field worked fine for me (CTRL-C + CTRL-V).

Good morning

Thank you very much for your answers. I have a new question:

Can I still import the terms I entered into a database without these "type" designations into this new database afterwards?

General question:
Can I merge databases?

What are the requirements? Do they have to be identical in structure for this to work?

Hi

There is no function to merge termbases. What you can do however is export the contents of termbase 1 and then import them into termbase 2. You obviously need to have either the same or at least partially same entry structure. On import (and also export) you can define which fields you want to import (export).

A very useful tool for this is the Glossary Converter, which you can find in the AppStore: RWS AppStore Plugin