SUMMARY This happens on the import side of an export/import operation via *.kim: For keywords that are new for the existing database (coming from the import), the dialog often suggests some shorter form that is already there. e.g: Instead of using the tag from the *kim file: "Schweinslippfisch Bodianus diplotaenia" the suggested keyword is just "Schwein" (which is an existing one in the current DB). This happens with all the tags where a shorter part of the word is already present and the new tag isn't. This forces me to comb through the list and *manually* type in the long version again (there is no way to copy and paste from the left side of the dialog box to the right (?)). I would much prefer to have the new keyword inserted - maybe highlighted in red and maybe with the option to select from similar ones already in existence ... STEPS TO REPRODUCE 1. you need 2 separate databases with the same categories but (slightly) different tags 2. in one DB tag an image with "sky" 3. in the other DB tag an image with "skyfall" in the same category as before 4. select this image for export to a *.kim file 5. import this kim file into the first DB OBSERVED RESULT 6. when the dialog reaches the point where you can see the tags of the category above, the tag "skyfall" (in the *kim) will be shortened to "sky" EXPECTED RESULT alt-6a. the tag "skyfall" is suggested for import but highlighted (in red?) with the option to select from (a few!) similar tags that are already there. alt-6b. the list can be shortened to optionally only show tag mismatches SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: openSuse 15.1 with Plasma 64bit (available in About System) KDE Plasma Version: KDE Frameworks 5.55.0 Qt 5.9.7 (kompiliert gegen 5.9.7) ADDITIONAL INFORMATION KPA-version: v5.5-150-g323e2b29 (compiled from git master)