The LEO-Event DuplicateRadar

Events are a kind of service. But what happens if data is being captured twice during collection or import? There is always the risk of mistakes that slip in. And it may take some time to revise them. From the beginning of 2012 there will be a new module that makes the clearing up easier: the DuplicateRadar. This module shall not only detect duplicates, but also make the clearing up of data easier. The following functional areas are available:

Recognition of duplicates
There are duplicates in each data base. Quite often it is difficult to find these data. The DuplicateRadar has got an integrated search that compares the data sets according to strict criteria and marks them as duplicate candidates. In order not to overload the system, the system runs only at night during fix times that can be configured by the customer – if necessary, several successive nights until the data base has been combed through completely. When all data are checked, the duplicates can be overworked and merged.

Merging of duplicates
When the duplicate candidates are marked, the reworking can start. For that purpose the duplicate candidates may be approved. Afterwards, LEO-Event clears the system automatically, the double data sets are being deleted and references are being transferred to data set IDs and foreign key allocations. If the DuplicateRadar has mistaken, the duplicate candidate can be declined. This processing is also being saved so that the duplicate candidate does not appear any more – neither in the data collection nor in the import. A third possibility is the merging of data sets to a master data set. If not only a data set from the data base shall be deleted, but if also certain data parts, like e. g. text or pictures shall be taken over by another set for merging data the data sets can be brought together in a special mask. Also in that case all data IDs, foreign key allocations or references are being combined in data set. All other duplicate data sets are deleted. When the merging took place, also in the further processing of the data, the data set is being used correctly as all references show the merged data set. Thus, even online requests via ID are no problem.

Reporting of duplicates
The data base is being overworked, all duplicates have been deleted out of the system. However, what happens with the next possible duplicates? The DuplicateRadarcontains an integrated reporting. So duplicate candidates are marked during the collection, the import or during input via interface and are being reported to a certain user group that can be defined freely. A search run is not necessary any more. The duplicates can be overworked directly. Thus, the data base remains clean – and the service remains good in all publication channels without too much effort.