Data transformation (Advanced Access)

Table of Contents (Advanced Access)

Use this table of contents to navigation Purview Sync during the Advanced Access phase.

Processing custodians

Purview Sync automatically organizes all imported files by custodians, with custodian definitions derived from the loadfile imported from Microsoft Purview. Custodians are automatically created by Purview Sync. You can find them after clicking into the Documents tab.

Each custodian is associated with a data source that includes the source path where the custodian's files are saved.

Currently, Purview Sync supports custodial data sources.

Automatic overlay and using Microsoft fields

Overlay in Purview Sync updates existing records in the review workspace by merging or replacing data from the source with corresponding fields in the workspace, based on the fields already existing in the Microsoft Purview loadfile.

Microsoft Purview creates an export object containing native files alongside a loadfile that holds all metadata information. Once files are processed into the workspace, Purview Sync overlays them with metadata from the loadfile, assuming that the workspace has the necessary fields created. These fields must match the column names in the load file exactly; Purview Sync will not create them automatically.

When creating the metadata fields in RelativityOne for overlay, we recommend to refer to Microsoft documentation. For more information, see Microsoft's documentation.

Relativity Short Messaging File conversion

We automatically convert HTML Teams data into Relativity Short Messaging File (RSMF). For more information about RSMF, see The Relativity Short Message Format .

Teams formats supported by Purview Sync are:

Teams format Description

Single chat between two users

 Supported
Group chat with three or more people Supported
Messages in Teams and channels Supported
Threads Supported
Deleted threads Supported

In Teams, when a thread is deleted, only the top (root) message is deleted, but replies retain their structure. In Purviews, they are classified as _Orphaned Replies_ and marked as deleted.
Deleted and edited messages Supported
Attachments Supported
Channels Supported
Deleted chat Supported
User leaving team Supported
User deleted Supported
Archived channel Supported
Add removed user back to chat Supported
Tag in chat Partially supported

Exported from Microsoft Purview as an email, processed correctly.
Reply in chat Supported
Channel name change Supported
Forwarded message Supported

RSMF is properly generated with user and message, but – following the same behaviour in Microsoft Purview - it is not indicated that this message was forwarded.
Chat with picture Supported
Chat with shared M365 docs Supported
Links Partially Supported

RSMF is properly generated with user and message, links are normal text
Chat from audio, video, meeting Partially Supported

RSMF is generated, but as of now user is "Unknown User".
Automatically created meeting recording Partially Supported

Video file is available, but extension is not visible i.e. making it more difficult to locate.
Scheduled messages Supported

RSMF is properly generated with user and message but – following the same behaviour in Microsoft Purview – it is not indicated that message was scheduled.
Translated messages Supported

RSMF is properly generated with user and message, but – following the same behaviour in Microsoft Purview – only in original language.
Modern attachments Partially supported

There is a link in Teams’ message, but family relation is not yet supported in Purview Sync.
Different alphabets Supported
   

 

RSMF is properly generated with user and message, but – following the same behaviour in Microsoft Purview – only in original language.

Modern attachments

Partially Supported

 

There is a link in Teams’ message, but family relation is not yet supported in Purview Sync.

Different alphabets

Supported