

Relativity Processing is the recommended method of importing RSMF files into Relativity. Using processing ensures that the appropriate metadata header fields are extracted and families and attachments within the RSMF file are properly linked to give you the best near-native review experience.
One recommended workflow is to use Import/Export to bring in multiple RSMF files zipped together as Raw (Unprocessed) Data and immediately processing the data. Another option is to prepare your RSMF files to be processed into Relativity using RelativityOne Staging Explorer to get the data ready.
If you are using a non-Relativity processing tool, attachments need to be manually tied to the appropriate messages following the guidelines below with modifying the Relativity Attachment ID and Family (Group) fields. RSMF is wrapped in an EML so other processing tools should be able to process the other aspects of the RSMF file.
Processing largely handles RSMF files like any other Internet Message Format such as EML. To learn more, see Relativity Short Message Format.
We recommend doing the following before you process an RSMF file:
Feature | Steps needed to prepare |
---|---|
Processing profiles |
|
RSMF Header fields |
Ensure the X-RSMF-Version is included in the RSMF Header of the RSMF file. The X-RSMF-Version is required in both RSMF 1.0 and 2.0. To learn more about Headers, see Relativity Short Message Format. |
Note: RSMF files greater than 2GB are not supported and may be unable to process. We recommend creating and processing RSMF files no greater than 2GB.
The following subsections describe how different parts of RSMF are handled during processing. To learn more about how the RSMF file is constructed, see Relativity Short Message Format.
An RSMF will contain a set of headers that is specific to the RSMF file and they begin with the prefix X-RSMF-. These headers are generated at the time of file creation when converting from the source of chat data. The headers are extracted automatically during processing to the following mappable fields. This includes the set of fields highlighted below as part of Relativity as well as any custom headers.
The optional headers that begin with X-RSMF are extracted automatically during processing to the following mappable fields:
RSMF header | Metadata field | Field Type |
---|---|---|
X-RSMF-BeginDate | Rsmf/BeginDate | Date |
X-RSMF-EndDate | Rsmf/EndDate | Date |
X-RSMF-EventCount | Rsmf/MessageCount | Whole Number |
X-RSMF-Version | Rsmf/Version | Long Text |
X-RSMF-Generator | Rsmf/Generator | Long Text |
X-RSMF-Application | Rsmf/Application | Long Text |
X-RSMF-Custodian | Rsmf/Custodian | Long Text |
X-RSMF-Participants | Rsmf/Participants |
Long Text Caution: Only use the Long Text field type for mapping the X-RSMF-Participants header. Selecting Multiple Choice for this header can lead to hundreds of unique choices which negatively impacts performance. |
X-RSMF-AttachmentCount | Rsmf/AttachmentCount | Whole Number |
X-RSMF-EventCollectionID | Rsmf/EventCollectionID | Long Text |
Since the RSMF file type is an open format, custom headers are supported as well. They are extracted automatically to the mappable fields using the following:
X-RSMF-CustomHeader → Rsmf/CustomHeader.
The phrase CustomHeader can be replaced with any name less than 255 characters. For example, you can use X-RSMF-IdentificationCode to assign an identification code to each RSMF at the time of creation.
Note: RSMF headers are extracted as metadata fields. They become available for mapping after they are first discovered in a file. If you don't see the particular headers from the list above in your workspace, make sure you are processing RSMF files containing them.
For metadata to be extracted from fields they should be created before processing. As with metadata fields in Relativity, when setting up new headers, you will be required to discover new headers first during processing, establish mapping with fields and then publish the metadata. To learn more, Mapping processing fields.
Since the RSMF file is an EML file, it will also have the To, From, Subject, and Sent headers generated at the time of file creation. These headers will be populated at the time of file creation to adhere to the EML specification.
In addition to the four fields, the X-RSMF-BeginDate and X-RSMF-EndDate headers are commonly mapped into the Relativity Fields below.
Header | Relativity Fields Mapping | Description |
---|---|---|
To |
|
Usually all participants in the conversation including From sender |
From |
|
Usually the sender of first message in conversation |
Subject |
|
Usually a combination of chat name, date, etc. |
Sent X-RSMF-BeginDate |
|
Sent date of the first message in the conversation |
X-RSMF-EndDate |
|
Sent date of the last message in the conversation |
Note: Similar to email messages, you can extract all of the headers into a long text field using the Message Header as a source. The Message Header field should exist prior to processing an RSMF file. This field will be populated with all of the metadata stored in the EML header of the RSMF file.
To learn more about what should be included in the header and body, see Requirements for RSMF head and body.
Within the attached RSMF.zip file is the rsmf_manifest.json, which includes all message content and metadata, and the attachments. The rsmf_manifest.json file is not discovered as a publishable file.
For any other file within the rsmf.zip, the following rules apply:
The deduplication of RSMF files is based on the same method as the deduplication of emails. Relativity is calculating the hash based on the contents of the file and comparing this hash between files, based on the following factors:
To learn more about this algorithm, visit Deduplication considerations.
If the RSMF file exceeds the limit of 2 GB and is reported as error during processing:
If it appears that Processing is ignoring the Sent Date field or Last Modified field, you can do the following:
If all of your data is populated accurately in the Group Identifier field, but your attachments are still not showing up, then verify that the Group Identifier field has the correct GUID. If you have SQL access, query for where the GUID is 1F036749-A691-4AA8-8CF7-5EEB80C36CAF. Otherwise, please contact Relativity Support for assistance.
If the Short Message Viewer shows an error on the attachments, you can also, download and run the RSMF validator for bulk groups of files or use the validator in the Viewer to see issues for a single file. To download, see RSMF validator. The results of the validator will be available using the RSMF Validation icon to the right of the Viewer.
Use the validator and look for these errors that may result in errors with attachments:
Why was this not helpful?
Check one that applies.
Thank you for your feedback.
Want to tell us more?
Great!