• No results found

Considerations

In document Symantec ediscovery Platform (Page 95-102)

• For information on the available processing settings, refer to the “Configure processing parameters and features” section in the table “New Case: Processing Settings”.

• Gain insight and verify file integrity by comparing the results for File ID, Strong File Type, and File Extension. You can do so in the following reports:

– Not Processed Documents – Other Type - Extensions – Processing Reconciliation

Note: For Container File ID information, see “Supported Container Extraction File Types” on page 242.

Some of the reports have been renamed. The following table identifies the new names for the pre-7.1.3 reports.

Processing Reports

Report Name Description Pre-7.1.3 Report Name

De-duplication Generates a complete and

comprehensive list of every location for each duplicated document. Filter by ALL, Case Folder, or Custodian. Filtering by Case Folder can be done at the source or sub-source level.

Note: This report is not compatible with cases created prior to version 4.0.

Not applicable

De-duplication by Custodian

Generates a summary of duplicate document counts that are filtered on a per custodian or all custodian basis.

Not applicable

Discovery and Processing Options

Generates a list of the Discovery and Processing options

Note: This report is not available for cases processed before 7.1.3.

Not applicable

Discovery Errors Generates a list of documents that resulted in Discovery errors

Note: Run this report after processing for the most current list of file errors.

Not Processed Documents

Generates a list of documents that were processed but not discovered, or were excluded from Discovery and Processing (for example, items selected or excluded based on pre-processing options).

Notes:

• For loose message or EML files, the

Last Modified Time column displays the sent date for the message. If no sent date is found for the message, this column is intentionally left blank. • Checking the NIST option produces

the same NIST information as the pre- 7.1.3 “Pre-Processing Excluded Known Files” report.

• The Container Count column will be empty for pre-7.1.3 cases.

• The checkbox option “Include docu- ments that are ‘selected to process’ but no yet processed” option lets you toggle between processed data and data that is discovered but not yet processed.

“Pre-Processing Excluded Known Files” report (NIST list) “Pre-Processing Not Processed” report

Load File Discovery Errors

Generates a list of documents that resulted in Discovery errors during Load File Import

For more information, refer to the Load

File Import Guide. (Shows loose files

only.)

“Pre-Processing Load File Import” report

Other Type - Extensions Generates a summary and list of documents that are considered “Other Types” in Pre-Processing.

This report can be generated at the source or sub-source level.

When a source is selected, the report is generated for all its sub-sources. To generate the report at a sub-source level, only select the corresponding sub- source(s) and not its parent source.

Not applicable

Processing Reports (Continued)

Processed Documents Generates a list of the documents (PST, NSF, loose files) that were processed

“Already Processed Files” report

Processing Reports (Continued)

Processing Reconciliation

Generates a summary and list of files on disk and the corresponding document and items counts needed for

reconciliation.

This report can be generated at the source or sub-source level.

When a source is selected, the report will be generated for all its sub-sources. To generate the report at a sub-source level, only select the corresponding sub- source(s) and not its parent source. Consult the ReadMe.txt file included in the report zip file for more information about the layout and meaning of the various fields.

Note: This report is not available for cases processed before 7.1.3.

Considerations:

• Accurate reporting: Keep in mind that if data is being processed while running the Processing Reconciliation report or if data is processed after the report has been run, the report will not reflect the latest state. If data has been processed after or while the report was being run, rerun the report to ensure the latest information is included in your report.

• Any invalid characters in the directory structure that is created for the report are replaced with equivalent Unicode characters. This replacement also avoids collisions between two direc- tory names. The escape character used is '@'.

• Any file names that have invalid Windows characters are replaced with '_' (underscore).

• The Associated File column displays whether the file is associated with another file or not. Examples of associ- ated files include TIFF/text pairs, EML/ EMLXPART files, and LEF/L01 files. For TIFF/text pairs, text is accounted for under the Associated File column and its TIFF counterpart is listed under Documents Processed.

Not applicable

Processing Reports (Continued)

To generate reports

1. Under the Processing module for a selected case, click Reports. The Reports screen appears and lists available reports.

2. Choose one of the following report options:

Note: For additional report information, see “Processing Reports” on page 95 and “Step 7: Review Processing Results” on page 145.

– De-duplication

– De-duplication by Custodian – Discovery and Processing Options – Discovery Errors

– Not Processed Documents – Load File Discovery Errors – Other Type - Extensions – Processed Documents – Processing Reconciliation

3. Specify the information in the following table that is relevant to the report.

4. Click Create Report.

Report Settings

Field Description Report or Comment

File Format Specify the output format for the

report (CSV or XLSX).

CSV option is available for:

• DeDuplication • Discovery Errors

• Not Processed Documents • Load File Discovery Errors • Not Other Type - Extensions • Processed Documents

XLSX option is available for:

• DeDuplication by Custodian • Discovery and Processing Option

XLSX produces a very nicely formatted file but may take longer to generate, especially for reports that generate large lists of files from a large dataset.

The CSV option is faster but simpler.

Filter By Specify the filter for the report data: (All, Custodian, or Case Folder). “All” is the default.

Control what information is included in the report by designating a filter from the list.

Batch Label Select a label type from the drop-

down list, or “All Labels” is applied by default. The reports that use this setting are:

• De-duplication by Custodian • Discovery Errors

• Not Processed Documents • Processed Documents

These reports are useful in analyzing and preparing your data for processing, especially when the data can be easily identified by batch. Select the batch label and run a report for that specific batch.

Note: Batch-level reports are available for processing batches in cases created prior to version 6.6. For cases created in 6.6 and later versions, additional reports for discovery batches are also available.

Select Type: Select one of the options (“By

Discovery”, “By Processing” or “By Sources”)

For “Discovery and Processing Options” report

Discovery Time Select a label from the drop-down list, or “All Labels” is applied by default.

For “Discovery and Processing Options” report

Reason Code Select a reason that the document

was not processed from the drop- down list. The default is “All Errors”.

For “Discovery Errors” Report

Exclusion Criteria Select one or more exclusion criteria from the list.

For “Not Processed Documents” Report

The report is generated and the job becomes available in the Jobs window for download.

Note: If you need to submit multiple jobs of the same report, you can do so without waiting for the previous job to complete.

In document Symantec ediscovery Platform (Page 95-102)