SUMMARY
When importing a kim file you first match the exported categories to those in the current database: e.g. "Places" might be matched to "Ort" or "Location", which is OK. This report is concerned with the next step:

Then the single entries in each category are matched to existing entries in the current database or new entries are created. This matching process could/should be improved by a filter.

STEPS TO REPRODUCE
1. start the import process until you arrive at the entries for a category (eg. "People")
2. a possibly longish list appears with names in the import file and names in the current database

OBSERVED RESULT
3. Most names match 1:1 but it is not obvious, whether a name gets added to the database or it matches an existing name.
4. Some of the names are matched to different values - often incorrectly.

EXPECTED RESULT
* Exact 1:1 matches to *existing* names should be unlisted by default (with the option to make them visible). These names do not need any action.
* Names with an approximate match need special attention and should be highlighted. Example 1 below.
* Names with no match will be created in the current database. Those should be listed as well, but there should be an option to filter them out as they rarely need any interaction (but sometimes they do). Example 2 below.

Example 1:
*.kim -> current database
John Doe -> John
"John" could be the son and "John Doe" could be the teacher, so the name must be corrected

Example 2 (importing a file, my son made for me):
*.kim -> current database
Mother > Mother
"Mother" should be "Johanna" in my database

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: 
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
This is a feature request, not a bug :-)