Our clustered/related documents section is crafted to keep things as simple and straightforward as possible, even when the relationships between documents get tricky. The most convoluted situations are often the result of duplicate documents being loaded. Normally that pain can be alleviated by detecting and removing the duplicates (you can “Request Document Deduplification” in the sidebar of your “Imports/Exports” section), but when de-duping at a sufficiently aggressive level isn’t an option – the result can be some tricky threads.
Here is an example where two copies of the email “FW: Spread sheets” have been loaded — each with the 2 spreadsheets that had been attached.
We know that we have one email “Freight Charges” that has 2 separate replies loaded into the system (the 2 copies of “FW: Spread sheets”). Each of the duplicates is a valid document, so we need to display them “under” the email that they answer.
We flag this (hopefully unusual) situation in your dataset with a header: “Duplicate Message ID (2)” and a dotted border encompassing the duplicates and their attachments.
We always recommend (and are happy to help with) de-duping across your dataset (or a subset, like by-Custodian), but when not everything can be cleaned up — our interface shows you what you’re dealing with in as clean a way as possible.
[...] arrows in recent posts on our clustered/related documents section (Clarify of Review & Dealing with Duplicate Emails) and what they’re actually seeing in the [...]