Problem

When importing a tbx-file into an existing TermCollection, there is a 'Delete terms older than current import' checkbox in import dialog, and user's expectation is that any already existing terms will be deleted. Internally, the import algorithm checks for each term inside tbx if the same term already exists in db, and if yes - just the existing term is kept and tbx's one is ignored to reduce the database overhead. However, this logic does not additionally compare attributes db vs tbx for that term, so that if db term have any attribute that tbx term does not have anymore - db's one is kept untouched, and this produces and impression for the user that the whole checkbox just does not work.

Also, we have an ability to define which attribute datatypes are enabled/disabled per each individual TermCollection, and this is respected well when adding attributes manually via UI or API, but is not respected on tbx import.

Solution

Implement an additional check so that attributes to be also compared tbx vs db, and the db's ones that do not exist anymore in tbx - should be removed from db

Also, the attributes of a disabled datatypes should be ignored during tbx import