Manual post-editing serves to verify and if need be, correct the results of a function. In the case of matching functions, the addresses that are recognised as being duplicates are presented in the form of duplicate groups. Besides the data which is relevant for the comparison, the program also displays the contents of all other columns of the table that are not involved in the comparison. Based on this information, the user can then decide which of the addresses that were recognised as duplicates should really be deleted.
With the matching functions, the deletion log is the printable version of the matching results and duplicate records. Two different forms of the deletion log are available, the first being relatively short and compact, and the other form being significantly longer but therefore easier to read. In both forms, the output can be saved as different file types: besides PDF, you may also select HTML, Text, CSV, MHT, EXCEL, RichText (rtf) and graphics. Furthermore, in the above-mentioned file formats, the output can also be printed or sent as an attachment per email.
With the matching functions, the results log is basically the printable form of the matching results. The options to print, save and send as an email are similar to those of the deletion log.
Deleting in the Source Table
With all functions that are capable of deleting records, the results of the function can also be applied directly to the source table. In the case of matching functions, the records that are recognised as being duplicates are then deleted out of the source table.
All the records from the source table are saved in the results file according to the results of the function. In the case of matching results, this includes all records with all columns which were NOT deleted in the source table. With functions that merge data or change the contents of data fields, the results file includes all records with all columns of the source table and also the additional information or altered data fields. The format of the results file can be selected in the process, either as a CSV, XLS or XLSX-file.
All records with all columns from the source table that would be deleted by the application of the results of a function are saved in the archive file. In the process, one can select whether the archive file should be saved as a CSV, XLS or XLSX file. If a results file is also generated, then the results and the archive file contain together all the records from the source table.
In the duplicates file of the matching functions, the results are saved in a separate file. In doing so, one can select whether the duplicates file should be saved as a CSV, XLS or XLSX file. Based on this file, more advanced queries can be configured, e.g. in order to delete or transfer contact persons in a second table. The data can thereby be stored in two different forms. One option is a form where only the duplicates and address number of a single record is written in each row. In the other form, both the address number of the record to be deleted and that of the record to be maintained are saved in the row beside the duplicate number.
Flagging in the Source Table
With the matching functions, the records that are recognised as being duplicates can also be flagged directly in the source table, either with the duplicate number or with a simple deletion flag. Also here, this information can then be used to configure more advanced queries.
Processing Using a Stored Procedure
Finally, with the match functions, the results can also be further processed using a specific stored procedure in the database. Of course, this is only possible with database servers. Also here, this option can then be used to add further actions to the deletion process, such as for example a secondary deletion procedure or the transfer of information from the address that is to be deleted to the address that is to be maintained.
Enrichment in the Source Table
With the matching functions where deduplication is carried out between two tables/files, the matching results can also be used to transfer information from one table into another. The user can determine which data fields can be used for this purpose. For example, the data field that contains the telephone number can be entered as a source data field, and in the other table, a previously empty data field is designated as target data field, where the contents of the target data field can also be overwritten with data from the source table if necessary. If the target table is an Excel file, then either an existing target data field can be entered, or a new data field that would then be created by the program. With all other data formats, the target data field has to already exist in the table. In other words, the matching results establish a relationship between the individual records of both tables, which are then used to supplement information in certain data fields from one table into the other. With the deduplication between two tables/files, the information from the records that are flagged as not to be deleted is transferred to the records that are flagged for deletion.
By contrast, with the deduplication within one table/file, the corresponding function transfers the contents of one or more data fields from the record of a duplicate group that is flagged for deletion to the record(s) in the same duplicate group that are not flagged for deletion. This can be used to complete the records that are to be kept with the data from the records that are flagged for deletion.
Results File Including Enrichment
„Results File Including Enrichment“ also functions quite similarly to „Enrichment in the Source Table“. However, the results are not rewritten to the source table; rather they are written to a new file. In doing so, with the deduplication within one table/file, just like with the results file from the deletion functions, only the records that are not flagged for deletion are written, supplemented with the information from the records flagged for deletion that were selected for the enrichment. By contrast, with the deduplication between two tables/files, all records from the target table are written in the results file, irrespective of whether they are flagged for deletion or not, since precisely the information from the records that are not flagged for deletion in the second table are transferred to the records that are flagged for deletion in the first table.