EDIT

First implementation with d955087e . However, it may not yet work due to generics (the current DefinedTermDaoImpl.deduplicateResult() method maybe works only for CdmBase objects) but we work with DTOs here. Once this is tested we may also adapt other DTO based methods in TermVocabularyDaoImpl as there are lots of methods being DTO based but still loading the representation(s) as model objects.

The method used is a DTO method VocabularyService.findVocabularyDtoByTermType() or finally on DTO level TermVocabularyDaoImpl.findVocabularyDtoByTermTypes(). This method already implements deduplication server side as the new test (259c70d2e105) shows.
The DTO stores both representations in the result. So I guess the problem is somewhere on client side. Katja, can you check this.

Andreas Müller wrote:

The method used is a DTO method VocabularyService.findVocabularyDtoByTermType() or finally on DTO level TermVocabularyDaoImpl.findVocabularyDtoByTermTypes(). This method already implements deduplication server side as the new test (259c70d2e105) shows.
The DTO stores both representations in the result. So I guess the problem is somewhere on client side. Katja, can you check this.

Sorry it was the wrong method, it is the find(UUID) which gives back two vocabularies for the uuid.

Applied in changeset cdmlib|e3538034fba60c336b797d1ba58fbca89db817f8.

Should be solved now. Can you please review?

I tested on rem_conf_am and everything seems to work as expected.