This timeout value, in minutes, defines the time during which an
item that has been soft deleted from the
Duplicate
Detect details table is
still considered a duplicate if it is received again. In an item processing
system, an item that was previously processed by
Duplicate
Detect and added
to the
Duplicate
Detect database may need to be returned to the originator
of the item. When the item is returned, a message to remove the item
from the
Duplicate
Detect database is sent to the
Duplicate
Detect engine. The item
is not actually removed from the details table, but a timestamp is
added to a column in the database table indicating that the item was
soft deleted. It is normal for a returned item to be resent to
Duplicate
Detect for
duplicate checking, but the item is not expected until representmentThreshold
minutes after the delete occurs. If the item is resent to
Duplicate
Detect after
the returned item's soft delete timestamp, but before the representmentThreshold
expires,
Duplicate
Detect marks the item as a potential duplicate of the previously
returned item.
Note: This element is optional.
The following scenario describes how representmentThreshold works:
Item X is sent to Duplicate
Detect. Item X is not a duplicate of any previous
item and is stored in the details table of the Duplicate
Detect database.
Item X is returned and Duplicate
Detect is called to remove the item. The
current timestamp, 1:00, is added to a column in the details table
in the row for item X to mark it as soft deleted. The representmentThreshold
is 30 minutes. If a new item is received for duplicate checking at
1:15 and the item contains the same values as item X, the new item
is marked as a potential duplicate. If it is 1:45 when the item is
received for duplicate checking and the item contains the same values
as item X, the item is not marked as a duplicate.