Email Threading Upgrade
You can allow emails to be grouped and collapsed and remove duplicates using email threading. These are the steps to setup and configure email threading as part of an upgrade to Habanero or newer.
These steps need to be applied to all sources regardless of whether they are structured or unstructured data sources.
If installing Aiimi Insight Engine Habanero or later, for the first time ignore these steps.
The Habanero release introduced two new elastic fields that are required for email threading.
CollapseID
The default CollapseID is {prefix}_{source}_{id}_{version}
. This is automatically populated by Aiimi Insight Engine at crawl time. The fields combined ensure every item has a unique collapseID even if it appears in multiple sources.
DeduplicationID
deduplicationID is only applied for Exchange and Mimecast sources. For Mimecast, Exchange and the File Extractor, deduplicationID is populated with the internet message ID of the email at crawl time. It reduces the number of times the same email, in different mailboxes, is displayed in Aiimi Insight Engine.
For emails in all other sources, the value will default to the unique_value and will need to be populated by Tika.
Upgrading Aiimi Insight Engine
After upgrading to Habanero or later there are a few upgrade steps required to apply the default collapseID to existing sources.
Check the path of all commands to ensure they match your installation before you run them.
Open PowerShell as an admin.
Run the following command
Run the following command to create an Alias for future commands.
Run the following command to create the mapping.
Run the following command to test the source.
Replace <id> with the source name.
Open Kibana Dev Tools.
Run the following command to check the collapse id has applied correctly.
Update the index name to match the source you used above.
If this has worked the collapseID should appear in the elastic index.
If the results are correct, apply the collapseID to the remaining sources. The following command loops through all the sourceID's and applies the collapseID command.
Within PowerShell run the following command to apply the collapseID to other sources.
This command uses the alias created earlier to find all the sources.
Exchange and Mimecast Only
After the upgrade, all emails will have a unique collapseID applied and the old method of viewing emails should still work. For Exchange and Mimecast sources an enrichment needs to be run to populate the deduplicationID and threadIDs.
Enrichment Configuration for Email Threading
See our Enrichment Configuration guide for help creating a new enrichment.
Required Steps
ContentRetrieval
TikaText extractor
Text Cleaner
Content Retrieval
Retrieve Content - Set to Always
This will ignore any content that already exists.
Tika Text Extractor
This can be left as default.
Text Cleaner
Cleaning Process - Select Remove Blank Lines.
This removes any empty lines.
Control Hub Email Threading Configuration
Once the enrichment is complete go to Control Hub> Search Settings > Search Performance.
Group Emails - Check this to Group Emails from a conversation together in a thread.
Enabling this will impact your search performance.
If not ticked, emails will behave as they did previously, no grouping or collapsing and all results including duplicate will be displayed.
Testing
Login to the Aiimi Insight Engine search application.
In the search enter one of the following:
_exists_:metadata.isParent
- This will show all results where an attachment exists._exists_:collapseId
- This will show all results where a collapseId exists_exists_:metadata.conversationId
- This will show all emails results where a conversationID existsSelecting a result will either open the inline or full screen preview.
Instead of displaying one email it will show the email chain. Any attachments in the email chain will be added to the bottom of the preview results.
Navigate through the chain by expanding the related results on the right hand side.
Last updated