CloudNine Analyst: Importing Sender and Recipient(s) Field Values

Importing Sender and Recipient(s) Field Values

Sender and recipient fields can be provided via a load file for importation into CloudNine Analyst for a multitude of communication types. Values can be free-form text, email, phone numbers, or other unique identifiers that are used in the communication application. Many applications may use their own identifier or it may be a common format such as an email address or a phone number. When uploading these values, to ensure consistency, CloudNine Analyst will pare down the value depending on the communication type being imported. For example, a phone number may include several different types of separators such as a "(", "-", "." or "+". These values will be removed if the value mirrors that of a phone number. Examining the following phone number formats, here are examples of how each one would be displayed within CloudNine Analyst:
For email values, CloudNine Analyst will identify the email address within a string value, for example:
For all other formats that are not matching to either a phone number format or email value, CloudNine Analyst will leave those "as-is" and not perform any filtering. This normalization process is to assist with Actor profile correlation to the communication metadata. 
Note: If you are importing through CloudNine Analyst, Sender is a Required Field

Recipient Values (multiples)

For items with multiple recipient values, these can be provided as a semicolon-delimited string. For example, an email with multiple recipients can be provided as follows in the load file field:
The same applies for  CC and BCC fields with multiple values when importing email using the metadata import functions via the UI in CloudNine Analyst (ESI Desktop will parse these automatically from the source container)