• Compacting the Database
• Reviewing Errors
• Reorganizing Documents
• Scanning for Errors
• Validating Document Ranges
• Extracting Subsets
• Run Commands
• Full-text Indexing
• Configuring LAW and SQL Server
• Tracking Page Source, Size, and Color
• Reports
User Guide
No part of this work may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or by any information storage or retrieval system, without permission.
While the information contained herein is believed to be accurate, this work is provided "as is," without warranty of any kind. The information contained in this work does not constitute, and is not intended as, legal advice.
LexisNexis and the Knowledge Burst logo are registered trademarks of Reed Elsevier Inc., used under license. LAW PreDiscovery, is a registered trademark, Concordance is a registered trademark, and CaseMap is a trademark of LexisNexis, a division of Reed Elsevier Inc. Other products or services may be trademarks or registered trademarks of their respective companies.
LAW PreDiscovery™ Concordance® CaseMap®
LexisNexis® Total Litigator LexisNexis® Early Data Analyzer
LAW PreDiscovery™ Version: 6.1.54
LAW Prediscovery Release Date: February 29, 2012 © 2015 LexisNexis. All rights reserved.
© 2015 LexisNexis. All rights reserved.
Table of Contents
Chapter 1 About LAW PreDiscovery
6
Chapter 2 What's New in LAW PreDiscovery
9
Chapter 3 Administrating LAW PreDiscovery
16
... 17
1 Compacting the Database
... 18
2 Reviewing Errors
... 20
3 Reorganizing Documents
... 21
4 Scanning for Errors
... 24
5 Validating Document Ranges
... 26
6 Extracting Subsets
... 267 Run Commands
... 288 Full-text Indexing
... 389 Configuring LAW and SQL Server
... 42
10 Tracking Page Source, Size, and Color
... 45
11 Reporting
... 47
Viewing Reports
... 51
Case Summary Report
... 53
Deduplication Reports
... 55
ED Loader Session Report
... 59
Exception Report
... 60
Files By Type Report
... 62
Files By Type Summary Report
... 63
Folder Summary Report
... 65
Page Properties Report
... 66
Tally Report
... 68
Using Grids for Reporting
Chapter 4 Reference Information
71
... 71
1 Languages
... 732 License Matrix
... 783 Field Descriptions
... 1024 Unicode Support
... 1045 Keyboard Shortcuts
... 1066 Contacting LexisNexis
Chapter 5 Glossary
109
Chapter
1
About LAW PreDiscovery
About LAW PreDiscovery
LexisNexis® LAW PreDiscovery™ helps legal professionals and their service providers meet the
increasing demands in the discovery of printed and electronic documents. By integrating production-level scanning w ith robust e-discovery and data processing features, LAW
PreDiscovery is optimized to enable scalable execution of even the largest discovery projects, from running multiple computers to batch scan boxes of paper documents to importing millions of e-mails and attachments from mail stores, to full text indexing, querying, and exporting to many other popular litigation support applications.
In practice, LAW PreDiscovery supports these key discovery processes:
Prefilter large document sets
The Early Data Analyzer module is a standalone prefiltering module available w ith the LAW PreDiscovery 6.0 suite. Use it to implement high volume electronic discovery productions. Early Data Analyzer indexes, filters, and produces export sets. Culled documents are passed directly to LAW for full expansion and production.
Creating and managing cases
LAW PreDiscovery centers all activities, including data collection, processing, and export on the case. Each case corresponds to a database file, w hich tracks all source files and production files, including graphics and text.
In the process of creating a new case, you select a database engine, create and name the database file, establish a folder structure for documents, and define any additional database fields you w ill need later for coding. Optionally, to simplify future case creation, you can create case templates that specify pre-defined options.
Acquiring documents
In this step you may do any of the follow ing activities that bring documents into the case: Import electronic discovery using ED Loader to extract text and to record document metadata in the case database.
Scan paper documents to electronic format.
Import items and metadata from existing cases and load files. Import existing TIFFs or other kinds of image files.
Assign custodians at the batch or source level. Code documents w ith data fields.
Performing quality control
The exact nature and timing of quality control activities vary greatly, depending on the type and quality of source documents. Quality control typically involves multiple activities spread
throughout the discovery project:
Error correction, for example: review ing and fixing processing errors, keeping detailed logs of w arning and other error conditions, and alerting you to suspected file
extensions.
Tag documents that contain specific text or metadata attributes for the purpose of narrow ing consideration to pertinent documents or pages.
Deduplicate files that w ere imported during electronic discovery. Fix problems w ith TIFF files using built-in image cleanup tools.
Batch processing
Batch processing functionality helps to automate various processor-intensive jobs, including: document numbering, image cleanup, endorsing, conversion to TIFF, printing, and optical character recognition (OCR). LAW PreDiscovery lets you take batch processing to a new level by combining the processing pow er of multiple computers to join distributed batch
processing of large jobs.
Exporting
LAW PreDiscovery provides a w ide range of options for exporting to litigation support applications in a variety of standard formats, including: native files, images, coded data, and OCR text.
For information on LAW PreDiscovery and other litigation support products by LexisNexis, please visit the LexisNexis PreDiscovery w ebsite.
Chapter
2
What's New in LAW PreDiscovery
What's New in LAW PreDiscovery
LAW PreDiscovery™ 6.1.54 and Early Data Analyzer 1.1.110 introduces the follow ing features and product enhancements:
LAW PreDiscovery
Deduplication
The Inter-Case Deduplication utility now supports SQL Server databases. External
deduplication databases can now be created as Microsoft SQL Server databases for better scalability.
For more information, see: Inter-Case Deduplication
Full-Text Report
Full-text search reports now include custodian summary, grouping, and document family information.
The Search Request Summary (by Custodian) section is added to the full-text search reports. All sections in the report now include the follow ing:
# Docs. Number of documents returned in the search queries.
# Docs(family). Number of documents, including child documents, returned in the search
queries.
Total Hits. Total number of search hits identified.
Size (GB). Total file size for documents returned in the search queries.
Family Size (GB). Total file size for the documents, including child documents, returned
in the search queries.
For more information about full-text search reports, see: Full Text Searching.
Imports and Exports
Electronic Discovery imports now support Microsoft Outlook OST files. For more information, see: Importing E-Mail Files.
Load File imports and exports now support EDRM 2.0 XML load files.
For more information about importing EDRM 2.0 XML load files, see: Importing Cases and Load Files.
A <FolderPath> field has been added to the Available Fields list on the Fields tab in the Export Utility dialog box. The <FolderPath> field w ill contain the contents of the Path field in LAW PreDiscovery.
For more information, see: Fields Tab
TIFF Conversions and E-printing
Microsoft Project is now supported as a source application for TIFF conversions and e-printing. You can modify Microsoft Project settings for TIFF conversions and e-printing by selecting Project from the Categories list in the TIFF Conversion Options dialog box or the e-Print Options dialog box.
For more information, see: Output Settings for E-Print and TIFF Conversion and Project.
Early Data Analyzer
Case Settings
The Maximum Agents field is added to the Analysis tab in the New Case Setting and Edit Case Settings dialog boxes. The Maximum Agents field determines the maximum number of agents (computer processors) that can process data for a case at any given time.
For more information, see: Cases in Early Data Analyzer.
Exceptions
The Re-Analyze button is added to the Exceptions tab. The Re-Analyze button provides the ability to re-analyze individual files from the Exceptions tab.
When you click the Re-Analyze button for a file, the file is removed from the exceptions list and added back into the analysis queue. Once the file is added to the analysis queue, it is automatically re-analyzed and re-indexed.
For more information, see: Review ing Exceptions.
Exports
Export sets can now be created and exported by tags, providing more precise control of export sets compared w ith just the core filtering mechanisms. When an export set is created by tags, the export w ill only include the files that contain the selected tags.
All tags associated w ith a document are w ritten to LAW during exports from Early Data Analyzer regardless of the selection method. Both group and individual tags in Early Data Analyzer are created as document-level tags in LAW PreDiscovery.
For more information, see: Exporting.
Filters
The Language Filter is added to Early Data Analyzer and is now available for selection from the filter list on the Filters tab. The Language Filter identifies the languages in each of the case files, and allow s you to filter and tag individual and groups of documents based on the languages selected in the Language Filter.
The Date Range Filter now supports filtering by multiple date ranges.
The Content Filter (Text) is now removed from the filter list on the Filters tab. The
Content Filter functionality is now incorporated into the new search feature in Early Data Analyzer. For more information, see: About Searching.
For more information about filtering in Early Data Analyzer, see: Filtering.
Global Dashboard
The functionality for modifying the processing and analysis priority order for cases has been modified. You can now quickly change the processing order from the new Modify Case Priorities dialog box. The Modify Case Priorities dialog box is accessed by clicking the new Modify the order in w hich cases are processed link on the Working Cases tab on the Global Dashboard.
For more information, see: Using the Global Dashboard.
Indexing
The 64-bit version of the text indexing process is added to Early Data Analyzer to improve speed and scalability on 64-bit operating systems.
The Compact Index button is added to the Full Text Index section on the Dashboard tab. Clicking the Compact Index button compacts the index to reduce the indexing space on the disk and removes fragmentation from the index. The index can only be compacted w hen the indexer state is idle.
For more information, see: Cases in Early Data Analyzer.
OCR
The OCR tab and the OCR Document button are now added to Early Data Analyzer for performing OCR (optical character recognition) on image-based documents, such as TIFF, JPEG, GIF, BMP, PNG, and Adobe Acrobat PDF files, at the document level so that the documents' content can be read, filtered, and searched before exporting the documents to
LAW PreDiscovery.
OCR can now be performed on groups of image-based documents by file type on the OCR tab, or can be performed on individual image-based documents using the OCR Document button on the Filters, OCR, Search, Export and Exceptions tab in Early Data Analyzer.
The purpose for performing OCR on documents is to help identify the documents you w ant to export to LAW PreDiscovery. When you export image-based documents on w hich OCR w as performed in Early Data Analyzer, if an image-based document included image-based attachments, only the OCR from the parent document is exported to LAW PreDiscovery. The OCR for the child documents is not exported. In this scenario, OCR needs to be performed again on the child documents in this document family in LAW PreDiscovery once the documents are exported into LAW PreDiscovery.
For more information about performing OCR in LAW PreDiscovery, see OCR Overview .
For more information about performing OCR in LAW PreDiscovery, see OCR Overview .
Password Management
The Passw ords tab is now added to the New Case Settings and Edit Case Settings dialog boxes for managing passw ords and extracting content from passw ord-protected Adobe Acrobat PDF files. When the passw ord for a passw ord-protected PDF or PST file is added to the Passw ord tab, the document content w ill be visible in the content view er in Early Data Analyzer. Passw ords can be manually added or imported from a line-delimited .txt file. For more information, see: Cases in Early Data Analyzer.
Reports
Reports can now be saved to Microsoft Excel *.xls files.
The Filter Summary report is now updated to include all defined filters, the filter settings by items included and items excluded, and the item count for each filter setting.
Tw o new reports and tw o new log files are added to the Reports tab in Early Data Analyzer:
Export Report. Provides a summary of the documents exported to LAW PreDiscovery
across all export sessions from Early Data Analyzer for the current case grouped by custodian.
Export Exclusion Log. A text-based log file containing a list of all documents not
included in the export set provided to LAW PreDiscovery.
Export Inclusion Log. A text-based log file containing a list of all documents included in
the export set provided to LAW PreDiscovery.
custodian, by search term, and the search terms by custodian. The report includes hit counts by search term and family, and sizes by search term and family. The Search Report replaces the Full Text Report introduced in Early Data Analyzer version 1.0.
For more information about reports, see: Creating Reports.
Searching
The Search tab is now added to Early Data Analyzer for performing searches in Early Data Analyzer. The Search tab provides enhanced search capabilities, including: metadata search (searches by field and field values), searches by dictionary w ords, saving and editing search terms, and view ing search results by metadata-based clustering on custodian, file type, sender, and sender domain on the Guided Search tab.
In Early Data Analyzer, search is only performed on the filtered records for a case. For example, if a case contains 3,000 records, but after filtering the records there are only 500 records, a search query is only run against the 500 remaining case records.
For more information, see: About Searching.
Tagging
Tags can now be created and applied to individual files or files in a group, such as files in a filter, search query, or exception category, in Early Data Analyzer.
Tags are applied to individual files in the Document Tagging section at the bottom of the document preview pane on the Filters, OCR, Search, Export and Exceptions tabs in Early Data Analyzer. Tags are applied to files in a group in the Group Tagging pane on the Filters, Search, and Exceptions tabs.
For more information about applying tags, see: Tagging.
Tags are added to a case, maintained, and can be exported on the new Tags tab in the New Case Settings and Edit Case Settings dialog box.
For more information, see: Cases in Early Data Analyzer.
User Interface
Sort functionality is now added to columns on the Filters, Search, and Export tabs in Early Data Analyzer.
On the Filters tab, you can now change the sort order of the the Name, Start Date, End Date, Count, and Tags columns. On the Searches tab on the Search tab, you can now change the sort order of the ID, Tags, and Count columns. On the Export tab, you can now change the sort order of the Name, Total, and Filtered columns.
By clicking a column header, you can sort items by the selected column in ascending or descending order.
For more information on this release and on previous releases of LAW PreDiscovery, see: Release Notes.
Chapter
3
Administrating LAW PreDiscovery
Administrating LAW PreDiscovery
LAW PreDiscovery supports many core administrative functions.
In this section
Compacting the Database
Describes a rationale and provides procedures for compacting the case database. Reviewing Errors
Provides instructions for using the Log View er to review errors and w arnings that may occur during various operations.
Reorganizing Documents
Provides procedures for using range files to help reorganize documents. Scanning for Errors
Describes procedures for scanning the case database for errors. Validating Document Ranges
Describes the process of validating document ranges and describes methods of validation. Extracting Subsets
Provides procedures for extracting data and images from one folder to a selected output folder.
Run Commands
Explains how to access the command prompt directly from LAW PreDiscovery for the purpose of starting external programs or running scripts.
Full Text Indexing
Explains w hat is required in order to do full-text indexing. Configuring LAW and SQL Server
Describes installation and configuration options for SQL Server that enable it to w ork w ith LAW PreDiscovery.
Tracking Page Source, Size, and Color
Provides procedures to gather statistics on page source, size and color. Reporting
Compacting the Database
Compacting should be done on a w eekly basis at a minimum. How ever, if multiple users are performing extensive coding and scanning in a case, consider compacting the database daily.
Reasons to compact a database
Compacting databases is an essential part of database maintenance. Compacting the database can provide the follow ing benefits:
Consolidate unused disk space. Rebuild indexes.
Decrease the size of the database. Increase performance.
Reduce the incidence of failed database operations.
Reduce problems related to netw ork latency associated w ith running queries on very large databases.
Database files tend to increases in size as information is added and removed. The space used by records is not reclaimed w hen records are deleted, causing the size of the database to grow over time. This unused space is removed during the compact operation, reducing the size of the database. The size of the database before and after the compact operation w ill be reported, so users can see how much space w as recovered (Access only).
To compact the current database
On the File menu, click Administration, and then click Compact Database.
Related Topics
Configuring LAW and SQL Server
Reviewing Errors
You can use the Log View er to review errors and w arnings that may occur during these operations: Importing Exporting Batch Processing Reorganizing Scanning Deduplication
Page Count Extraction
To start Log Viewer
You can start the Log View er in either of the follow ing w ays:
After processing the operation, if errors or w arning conditions occurred, you are prompted to view the Log View er. You may choose to open the view er at this time. Or
1. From the main w indow , on the Tools menu, click Log Viewer. The Open Error Log dialog box appears.
2. Do one of the follow ing:
In the All Logs tab, select a log to open. Click a different tab and then select a log. 3. Click Open.
The Log Viewer dialog box appears. The table lists fields is log files and the title bar show s the filename of the error log. Error logs for most processes are stored in <case root>\$Logs in *.csv format.
Tagging records for review
You can apply a Tag (Boolean) value to records show n in the Log View er. This action can be useful for creating custom reports, review s, and selecting items for further processing, etc.
1. Create a Tag (Boolean) field. For more information on creating tag fields, see Creating Tag Fields.
3. Select the tag field you created in the previous step. 4. Click the Tag All Records button.
5. Select the desired records and then click the Tag Selected Records button.
Tagged records w ill appear checked in the grid displays and set to <Yes> in the Index display.
Tag values cannot be toggled using this feature.
Related Topics
Viewing Reports
Batch Processing Overview Creating Tag Fields
Reorganizing Documents
You can reorganize your documents based on the ranges specified in a selected range file.
Note the follow ing facts w hen considering w hen to reorganize documents:
The best time to run the reorganize documents function is prior to OCR operations. The reorganize function is capable of reorganizing text extracted from documents by OCR. How ever, information not associated w ith the leading document for a range w ill be
discarded.
If an error does occur you might see a message stating that the image and OCR text are not synchronized. In such cases, the reorganize process w ill stop and the OCR data w ill have to be removed or corrected for the image.
This issue can occur any time the OCR process stops before it completes. For example, the issue could result if the OCR engine crashes, if you attempt to insert new pages into a document after the OCR process ends, or if you try to merge documents w ith incomplete OCR.
To reorganize documents
2. Select a range file. A range file is a comma-delimited text file consisting of tw o fields: BegDoc# and EndDoc#.
LAW PreDiscovery™ w ill begin rebuilding documents based on the specified ranges.
Related Topics OCR Overview
Scanning for Errors
As cases increase in size, you w ill w ant to detect and eliminate certain types of problems in the database. The Scan For Errors feature provides a means to automatically search the database
for some common problems.
Note the follow ing facts about the Scan For Errors feature:
Errors that are detected are logged in a file named scandb.log that is kept in the temp folder (%temp%\Law 50\Log).
When the scan is complete, if errors w ere found LAW PreDiscovery™ w ill present the option to view the log file.
To scan for errors
1. On the File menu, click Administration, and then click Scan For Errors.
2. Select options to customize the scan and then click Begin. Options to customize the scan are described in the follow ing table:
Option
When you want to
All Documents Scan all documents for errors.
Current Folder Scan only documents in the current folder for errors.
Include subfolders Scan documents in all folders w ithin the current folder for errors.
Ignore Native
Find invalid records
(missing images) Verify that each record in the database has a correspondingimage.
Remove if found Remove invalid records.
This option is useful if you have used Window s or some other program outside of LAW to delete or move files.
These actions could cause LAW to contain records that do not point to valid images. These extra records can affect processing and summary functions, so users should remove them.
Find blank/missing
Page IDs Find documents w ith pages that have blank or empty Page IDentries. Whether intentional or simply operator errors, certain export formats require non-blank Page ID entries for renaming or linking purposes. This option provides a w ay to find the documents w ith blank entries so users can take the appropriate measures to correct them.
To add page IDs to pages that have blank or empty Page ID entries after they are found:
1. Open the standalone grid display.
2. On the Query menu, click Blank Page IDs.
A 'missing' Page ID is defined as being a document record w ith an incorrect number of page-level records. Since each document should have the same number of page-level records as the
document's page count, this check ensures (for example) that a 5-page document has exactly 5 records in LAW's 5-page table. If any missing page records are found, LAW w ill automatically sequentially number the PageID values of the missing page level records if Auto-number missing pages is selected.
Find gaps in Page IDs Find gaps or breaks in the numbering sequence.
Pages in a case are typically numbered sequentially. Sometimes, how ever, there may be breaks in the numbering sequence. This option allow s users to find these breaks to ensure that all pages are accounted for and to confirm these breaks, if any, are
intentional and correspond to the original documents.
Remove duplicate/
orphan page records Fix duplicate page records or records that consist of orphanpages. Duplicate page records can result w hen a document contains tw o "page 3's" for example. Since there can only be one 'page 3', this record is safe to remove. Duplicate records can be detected w hile numbering a range of documents as it causes a duplicate PageID to be detected during this process.
An orphan page record is a page level record that no longer belongs to an existing document. This may have occurred after a document w as deleted, but a failure occurred deleting the page records for the deleted document. These records are also safe to remove from the database.
Verify Page Counts Validate the page count of every image in the case that has a record.
LAW PreDiscovery opens every image and compares the actual page count w ith the page count stored in the database. If the page count in the database is incorrect, it is updated, provided the Correct invalid database page counts option is selected. Because every image has to be opened, this option can be very time consuming for large cases. How ever, this option has several benefits. First of all, it ensures that the total page count displayed in the Case Summary is accurate for billing purposes. Second, by opening every image file, it ensures that none of the images have become corrupted (if they are, it w ill be logged). Third, it ensures that there are no excess Page ID entries (entries for pages greater than the actual page count) that can affect the export process.
Related Topics Importing Electronic Discovery Launching the Grids
Validating Document Ranges
The process of validating document ranges is composed of the follow ing steps: 1. Before scanning, inspect the documents to determine document breaks.
2. Create a range file that describes document breaks. A range file is a delimited text file w ith tw o fields, BegDoc# and EndDoc#.
3. Use the Validate Ranges function and reorganize document as necessary using the
Reorganize Documents function.
4. After the scan process check that document breaks w ere applied correctly. If errors are found after scanning, you can manually correct document breaks by using a combination of the Merge Documents and Split Documents functions.
1. On the File menu, click Administration, and then click Validate Ranges. 2. Enter the path to a range file.
A range file is a comma-delimited text file that consists of tw o fields: BegDoc# and EndDoc#.
After a range file is identified, documents are compared against the range file in tw o passes.
The first pass ensures that all pages fall w ithin the specified ranges. This pass is only useful if the documents and ranges are numbered sequentially w ith few or no gaps. Otherw ise, LAW may report an excessive amount of errors. Any pages that do not fall w ithin one of the specified ranges w ill be reported in the error log.
The second pass validates all of the specified ranges against the documents in the case. Any ranges that are not found is reported.
3. To display the error log, click Yes.
Related Topics Merge Documents
Split Documents
Extracting Subsets
This feature extracts data and images of the current folder to a selected output folder. This feature has been designed to be useful for creating partial backups and re-importing. Not all indexes and field properties are retained, so the output is not suitable for a standalone w orking case.
To extract subsets
On the Folder menu, click Extract as Subset.
This function w orks w ith either ADS or Access databases and alw ays produces a project.mdb file. This feature is not supported w ith SQL Server cases.
Related Topics Export Utility Overview Launching the Grids
Run Commands
This topic covers integration of LAW PreDiscovery™ w ith custom applications and scripts. This topic assumes you have intermediate to advanced programming skills. LexisNexis assumes no responsibility for any damage done w hen you the LAW PreDiscovery run command to start external applications, scripts, commands or other active content.
LAW allow s you to run executable files, commands, and scripts on LAW cases. Note the follow ing facts w hen you run external commands from w ithin LAW:
The connection string to the current database is passed to the executable or script. Only programs located w ithin the <AppPath>\Commands folder can be executed from w ithin LAW.
If the external program contains a file description, this value w ill be used in the menu name. If no file description is found, the menu name is populated by the filename w ithout the extension.
see the Field Descriptions topic.
To run an external command
Click Tools, and then click Run Command.
Create a connection string using code
The follow ing code creates a connection string using Visual Basic. The VBA.Command property w ill return the connection strings for both an Access database and an ADS database.
Dim cnn as New ADODB.Connection Dim rs1 as New ADODB.Recordset Dim rs2 as New ADODB.Recordset cnn.Open VBA.Command
rs1.Open "tblDoc", cnn, adOpenKeyset rs2.Open "tblPage", cnn, adOpenKeyset
Command example
The follow ing example command populates RecordType values in a LAW case. This command is useful w hen you w ant to w ork w ith RecordType data w ithout having to export first. This command is intended only to be used w ith LAW cases that are enabled for electronic discovery.
Populate RecordType Values
In this command, <RecordType> represents the field available only in the export utility. This field is used to classify exported records as e-docs, e-mail, etc. The command can be used to populate this field w ithin the LAW case database thereby
Using the RecordType command
The follow ing procedure describes how to use a command to populate RecordType values in a LAW case:
1. Create an index field to store the values. Note the follow ing requirements for the field: The field type must be restricted to Text or Memo.
You can name the index field anything you like as long as the field is applicable at the document-level.
2. Click Tools, click Run Command, and then click Populate RecordType Values.
3. Type the name of the target field and then click Begin. The possible values for target field are:
LOOSE E-MAIL ATTACHMENT E-MAIL ATTACHMENT
LOOSE E-MAIL E-MAIL
E-DOC
IMAGE ATTACHMENT IMAGE
4. When the process has completed, a Success message box indicates the number of records successfully updated.
Related Topics
Administration
Full-text Indexing
To perform full-text searches, the text for the records must first be indexed. The follow ing indexing capabilities are offered by LAW PreDiscovery:
Allow automatic indexing occur after you: Use ED Loader to create new records. Import a case.
Import raw images if the new record has associated text. Create scanned images and then OCR them.
Manually start the indexing process as necessary.
You can re-index documents, for example w hen you import a load file that contains records w ith text; or after you add text to previously indexed documents, as w hen you perform OCR or TIFF conversion after import.
You can also disable automatic indexing as a post import action in ED Loader.
To configure indexing options
Before you perform any action that involves indexing, consider configuring indexing options. Indexing options provide you w ith control over how certain w ords, punctuation, and other text elements are handled during indexing. Auto-indexing can also be enabled from this form.
2. Click the Indexing tab. The Indexing tab appears.
3. Set general options as needed:
Accent-sensitive - The indexer will take accents into account in indexing words with
this option enabled. For most users this is not recommended because this option increases the chance of missing the retrieval of a document if an accent w as omitted in one letter.
Automatically recognize dates, e-mail addresses, and credit card numbers - Enable
this option to have the indexer scan for anything that looks like a date, e-mail address, or credit card number during indexing.
Case-sensitive - The indexer will take capitalization into account in indexing words
w hen this option is enabled. In a case-sensitive index, "CREDIT", "Credit", and "credit" w ould be three different w ords. This option can be useful, for example, w hen you are searching for a term, such as a capitalized name that can be confused w ith a common non-capitalized w ord.
Ignore duplicate documents during indexing - When enabled prior to indexing, LAW
w ill not index any duplicate records in the case. Duplicate records have a DupStatus of either G or C. The "parent" duplicate, DupStatus=P, is also included. Enabling this
option can help to increase performance of indexing, searching, and review because only text from unique files is added to the index.
Insert word breaks between Chinese, Japanese, and Korean characters - Check this
box if you plan to search Chinese, Japanese, or Korean documents that do not contain w ord breaks. Some Chinese, Japanese, and Korean text does not include w ord breaks. Instead, the text appears as lines of characters w ith no spaces betw een the w ords. Because there are no spaces separating the w ords on each line, the indexer sees each line of text as a single long w ord. To make this type of text searchable, enable automatic insertion of w ord breaks around Chinese, Japanese, and Korean characters so each character w ill be treated as single w ord.
Run index process in background until canceled (auto-index mode) - When enabled,
the indexing process w ill run in the background, referred to as auto-indexing. When running the indexer in this mode, the indexer w ill continue to poll the database for new documents to index until it is canceled. This allow s the indexing of documents during the import process, so that w hen an ED loader session is complete, the documents are indexed and ready to be searched. Clicking the Hide button will
minimize the Auto-Indexer Status dialog to the notification area. To restore, right-click the icon in the notification area and choose Restore. A count of total documents indexed w ill appear w hen resting the mouse pointer over the icon.
The auto-indexer cannot be restored from the notification area w hen certain forms are displayed, such as Batch Processing and the Query Builder.
Auto-start indexing prior to electronic discovery imports - Enable this option to
ensure auto-indexing is enabled prior to ED Loader imports. The option is useful in the event the auto-indexing option is inadvertently left disabled.
Use local folder for temporary files during indexing - During indexing, the dtSearch
Engine may need to create temporary files to store w ord lists that are too large to fit into memory. By default, these files w ill be placed in the index folder. Use this setting to instruct the indexer to use the local user’s temporary folder for these files. The indexer w ill automatically delete the w ord list files w hen the index update completes. This is the recommended setting for cases on netw ork drives, NAS, or SAN devices. 4. Set options for handling hyphens in terms as needed:
Treat hyphens as spaces - This is the default method of handling hyphens for indexing.
For example, "first-class" w ould be treated as "first class."
Treat hyphens as searchable - Hyphens are treated as searchable text. For example,
"first-class" w ould be indexed as "first-class."
Ignore hyphens - Hyphens are ignored during indexing. For example, "first-class" would
be indexed as "firstclass."
All three - Applies all of the above options to allow multiple ways of finding text.
5. If necessary, change the priority of the type of text to index. For more information, see the next section in this topic, To change the text priority order.
6. Click OK.
If index options are changed after the case has already been indexed, the case w ill need to be re-indexed in order for the changes to be applied.
Records in LAW can have up to three types of text: text extracted from document by optical character recognition (OCR), printed text, and text extracted from electronic documents. Only one type of text for each record can be included in the index at any given time.
The default priority is: 1. OCR
2. Printed 3. Extracted
Note the follow ing facts that apply to text priority:
If the default values are used, OCR text w ill be indexed. If OCR does not exist for a document, then printed text is used. If no OCR or printed text is available, extracted text is indexed.
The sequence of priority can be changed as needed.
For positions 2 and 3, you can select <None> to remove alternate text types from consideration for indexing.
To change text priority order
1. On the Tools menu, click Options. 2. Click the Indexing tab.
3. Click the Configure button.
The Configure Text Priority dialog box appears.
4. Choose the desired text types for options 1, 2, and 3.
Extracted for Option 1, and then choose <None> for options 2 and 3.
If the above index options are changed after the case has already been indexed, the case w ill need to be re-indexed in order for the changes to be applied.
To flag documents and reset flags for indexing
Documents must be in a "flagged" state in order to be included in the indexing process. A document that is flagged for indexing means that it w ill be indexed w hen you run the indexing process manually. The steps required to flag or reset flags on documents depend on w hether you are setting this on an OCR operation, a TIFF conversion, or w hether flagging or reset w ill occur on one folder or a set of folders.
To set the option to reset text index status for OCR
1. From the main w indow , on the Tools menu, click Options, and then click the OCR tab. 2. The OCR Options dialog appears.
3. Select [OCR] Reset text index status to reset text index status for OCR processing of individual records or batches of records.
Clearing this option w ill prevent LAW from re-flagging the document for indexing after the OCR process is performed. This means the OCR text for affected records w ill not be searchable in LAW.
To set the option to reset text index status for TIFF conversion
1. From the main w indow , on the Tools menu, click Batch Process. 2. In the Batch Process dialog, on the Options menu, click TIFF Output. 3. The TIFF Conversion Options dialog appears.
Do one of the follow ing:
Select [TIFF Conversion] Reset text index status to reset the status and allow indexing to occur again.
Or
Clear [TIFF Conversion] Reset text index status to prevent LAW from re-flagging the document for indexing after the TIFF conversion and printed text is created. This means the printed text for affected records w ill not be searchable in LAW.
To manually flag documents for indexing
In certain situations, one or more documents may need to be manually flagged for indexing. For example, if the OCR text for a document w as deemed unusable and deleted outside of
LAW, the document could be manually re-flagged for indexing so the printed text for that document w ould be indexed instead.
To reset the text index flags for documents in one folder
1. In the main form, select the documents in the document list.
2. On the Edit menu, click Reset Fulltext Flags, and then select ON. To remove the flag, choose OFF instead.
To reset all documents or documents that span folders
1. From the main form, click click Tools and then click Display All Records. The standalone grid opens.
2. In the standalone grid, on the Tools menu, click Reset Fulltext Flags, and then click ON to enable records to be re-indexed, or OFF to prevent records from being re-indexed. The full text index flags for all documents in the current record set are set to ON or OFF. For more information about the text flag values stored in this field, see the _FTIndex
field values section in this topic.
After the desired documents have been flagged, they can be indexed.
3. In the main form, on the Tools menu, click Fulltext Index and then click Index New
Documents.
To enable automatic background indexing
An auto-indexing feature is available for indexing text as a background process, allow ing text to be indexed as records are being imported rather than w aiting for an EDD import to complete.
1. On the Tools menu, click Options and then click Indexing. 2. Set options as needed.
When records w ith associated text are imported via the LAW case import, LAW w ill prompt to index once the import has been completed.
To index new documents after ED Import
If the indexing is not performed immediately after the ED import, it may be performed at any time thereafter.
This feature w ill index any records that are "flagged" to be indexed.
To re-index all documents
A case can be re-indexed if needed.
From the Tools menu, click Fulltext Index, and then click Re-Index All Documents. This feature is useful in the event an indexing option needs to be changed or the index has somehow become corrupt.
_FTIndex field values
The _FTIndex system field is automatically created w hen a case is ED-enabled. It holds a numeric code that represents the status for the indexing process.
The possible values for this field are:
0: No text is available for indexing.
1: The record has text that is ready for indexing.
2: The record was flagged again for indexing but has not yet been re-indexed. 3: The record text is indexed.
To access full-text index properties
1. On the Tools menu, click Search Records. The Query Builder starts.
2. Select Full text search.
3. Click Options, and then click Index Properties.
The Full Text Index Properties dialog box appears. This screen provides details about the full text index for the current LAW case, such as size and the number of indexed documents.
4. Select options as needed:
Purge Duplicates - This function removes all records that were flagged as duplicate
records in LAW (DupStatus=G or C) from the full text index. This feature w ill first scan the case and then return the duplicate count in a message box.
Click Yes to remove the duplicates from the index or click No to cancel. To prevent these records from being included prior to indexing, use the Ignore duplicate documents during indexing option.
Compress Index - Compressing the index removes obsolete records from the index.
Obsolete records may include documents that w ere deleted from the case or records that w ere removed from the index using the Purge Duplicates feature. These obsolete documents are not returned in searches. If the "ObsoleteCount" value in this dialog is greater than zero, use the Compress Index function.
Verify Index - This function will check the full text index for problems or corruption. If any
issues are discovered, an error w ill be returned after running the verify and the case w ill likely need to be re-indexed.
To configure ED Loader auto-indexing
1. In the main w indow , on the File menu, click Import and then click Electronic Discovery. 2. Click the Settings tab and then select Post Import Actions.
3. Select or de-select Perform full-text indexing as necessary.
If the Perform full-text indexing option is enabled, after import you will be prompted to choose w hether to index the text of the new documents. If the setting is disabled, import w ill complete w ithout your having the option to perform full-text import.
Related Topics Creating Tag Fields Full Text Searching
Configuring LAW and SQL Server
Please contact LexisNexis for instructions on configuring SQL Server Express.
To enable support for SQL Server
1. On the Tools menu, click Options.
2. On the Preferences tab select Enable SQL Server/MSDE support.
3. Type the name of the SQL Server instance. (This is the computer name of server running SQL Server).
The value is saved and must only be re-entered if the server name changes.
By default, the option to select a database type is visible w hen you create a case. To disable the option, open any case in LAW. On the Tools menu, click Options, and then click the Preferences tab. Deselect the "Enable SQL Server/SQL Express Support" option.
Creating SQL Server user account(s)
There are tw o methods of specifying user accounts for use w ith SQL Server. You can use either of these methods to allow LAW access to the LAW cases stored on the server.
Create a Global Default User for LAW
PreDiscovery
Create Individual Users with Integrated
Security
Use this method w hen using SQL Server for other applications in addition to LAW
PreDiscovery™. This option helps to prevent users of SQL Server from accessing and modifying any other existing databases.
To create a generic global user account using this method:
Setup a SQL Server user w ith create/ modify permissions.
The user name and passw ord must be:
User: LAW_User Pwd: law32sql
When using the default user, the security mode for SQL Server must be set to SQL
Server and Windows or mixed-mode
authentication.
This method allow s a user to create SQL Server cases w ithout adding a special user to SQL Server as long as the current user has database create permissions on the specified SQL Server. Window s integrated security may be used w hen accessing/creating SQL Server cases.
If using this method, each user must be setup on the SQL Server to allow access to the case.
To enable this feature:
Select the Use Windows NT integrated
security option when specifying the
database backend for new ly created cases.
Detailed setup example
This section describes an example of a know n, w orking setup of SQL Server 2008 Express edition (not R2) on a computer running Window s XP.
Note the follow ing about using SQL Server w ith LAW PreDiscovery:
All testing has been performed internally using SQL Server 2000, but SQL Server 7 or higher should be supported.
Please contact LexisNexis Technical Support for instructions on configuring your instance of SQL Server to run w ith LAW. The follow ing listing provides sample values to use to setup a configuration of SQL Server 2008 Express w ith Tools (not R2) is suitable for testing new case production with LAW PreDiscovery. Use this as a starting point when discussing a production oriented SQL Server configuration w ith LAW PreDiscovery technical support.
Installation Summary for SQL Server 2008 Express
Installation Tasks
Instance name: can use default -- SQLEXPRESS
Features: Database Engine Services and Management Tools - Basic
Account Name: NT AUTHORITY\ NETWORK SERVICE
Passw ord = leave blank (default)
Database Engine Configuration dialog box: Mixed Mode (SQL Server authentication and Window s authentication)
User accounts: Add Current User. Or add at least one Windows login or domain user account.
In SMSS
Create a new login: Login name: LAW_User
Authentication mode: SQL Server authentication. Passw ord: law32sql
Depending on the information security policies for your organization you may be able to disable these passw ord settings: Enforce password expiration and Enforce password
policy.
Select Server Roles: enable dbcreator
Installation Steps
Step 1: Install Prerequisites
1. Install prerequisites as directed on Microsoft w eb site for the processor type and operating system of your computer.
Prerequisites include:
.NET Framew ork 3.5 SP1 or .NET Framew ork 4 Window s Installer 4.5
Pow erShell 1.0
2. After prerequisites are installed, restart the computer.
Step 2: Install SQL Server 2008 Express with Tools
SQL Server 2008 Express w ith Tools includes the Microsoft SQL Server Management Services console.
1. Dow nload the installer file for SQL Server 2008 Express with Tools from the Microsoft w ebsite.
2. Run the installation file and then follow prompts to continue. 3. In SQL Server Installation Setup dialog box click Installation.
4. Click New SQL Server stand-alone installation or add features to an existing
installation.
5. After installation files expand click OK. 6. In the Product Key dialog box click Next.
Next.
8. In the setup support dialog boxes, follow prompts to continue. 9. In Feature Selection, select both of the following:
Database Engine Services Management Tools - Basic
10. Click Next.
11. In Instance Configuration, using the default SQLEXPRESS is recommended although it is optional to change the instance name. Also, you can change the installation directory or leave the default.
12. Click Next.
13. In the Disk Space Requirements dialog box, click Next, assuming you have requisite disk space.
14. In the Server Configuration dialog box, next to SQL Server Database Engine: In the Account Name field, select NT AUTHORITY\ NETWORK SERVICE. Leave the passw ord blank.
Next to the SQL Server Browser field, under Startup Type, select Automatic. 15. Click Next.
16. In Database Engine Configuration dialog box, select Mixed Mode (SQL Server
authentication and Windows authentication).
17. In the Enter password and Confirm password fields, type the SQL administrator passw ord you w ant to use. Recommended: w rite the passw ord dow n in a secure location.
18. Under Specify SQL Server administrators, click Add Current User. Add other users as necessary, and then click Next.
19. In Error and Usage Reporting, select from options as needed and then click Next. 20. In Installation Rules, click Next.
21. In Ready to Install click Install. When Setup Progress Complete appears above the progress bar, click Next, and then click Close.
22. Close the SQL Server Installation Center.
Step 3: Add SQL user account for LAW PreDiscovery
1. Start SQL Server Management Studio. This is located in the SQL Server program group.
2. Login to the new SQL Server instance.
4. In Login name type LAW_User. 5. Select SQL Server authentication.
6. In the Password and Confirm password fields type law32sql. 7. Deselect Enforce password expiration and Enforce password policy.
8. In the left panel of the dialog box, click Select Server Roles and then select dbcreator. 9. Click OK.
10. Close Microsoft SQL Management Studio.
Related Topics System Requirements
Tracking Page Source, Size, and Color
You can capture at the page-level the source, size, and color of scanned and imported images, and for images created via TIFF Conversion w ithin LAW PreDiscovery™ cases. This data is stored w ithin the case database in the follow ing page-level system fields:
PageSource PageSize PageHeight PageWidth PageColor
When pages are scanned into a case all of the fields are populated.
Images acquired via raw image import or via load file receive only a PageSource value. Images created in LAW via TIFF Conversion or by single-document TIFFing receive values for PageSource and PageColor.
Images affected by the "Treat native TIFF images as image for record (bypass TIFF Conversion)" setting do not receive a PageColor value.
A batch process is available to populate this missing information for TIFFed and imported images. For more information on how to create a report containing the page-level information, see Page Properties Report.
Field names and values
These are the five fields used to store page-level properties: PageSource
PageSize PageHeight PageWidth PageColor
Three of these fields are lookup fields and are listed differently w ithin the database. Possible values contained in these fields are listed in the follow ing table. The lookup field names as referenced in the database are show n in parentheses beside the field name displayed in the LAW interface. Also, the numeric values used in the database are listed in parentheses beside the textual value users w ill see in LAW.
Field Lookup field names as referenced in the
database
Possible values (database numeric value)
PageSource (SourceID) Feeder (1)
Flatbed (2) Imported (3) TIFF Conversion (4)
Manual TIFF Conversion (5)
PageColor (ColorID) Black & White (1)
Color (2) Grayscale (3)
PageSize (PageSizeID) Letter (1) *8.5x11
Legal (2) *8.5x14
Double Letter (3) *11x17
Oversized (4) *Any pages outside the above 3 sizes
PageWidth -- Varies (Example: 8.5)
PageHeightVarie s
To update page data
You can use the Update Page batch process to populate the PageColor, PageSize, PageWidth, and PageHeight fields for any images in the selected record set missing this information. PageSource is not affected during this process because the source can only be captured at the time the image is acquired. As mentioned, imported images receive only a PageSource value and images created by TIFFing only receive PageSource and PageColor values. This process is necessary to populate the remaining fields if this type of data is needed for a particular project.
To start the Page Update batch process
1. From the main menu, click Tools and then click Batch Process. The Batch Processing dialog appears.
2. In the Batch Process dialog select Update Page Data and then click Begin. The batch process starts.
A page size tolerance setting can be used to set a margin for the page size values. The default value of the tolerance is set to one-tenth (.1). Using the default value, for example, everything up to 8.6 x 11.1 is interpreted as 'Letter' size. This setting applies at the
application level.
To set page size tolerance
1. Use Window s Explorer to open the LAW PreDiscovery installation folder. By default the path is:
C:\Program Files\Law 50
2. Use Notepad or some other text editor to open the Law 50.ini file.
3. Scroll to the [Settings] section. If one does not exist you can create the setting by typing [Settings] directly into the file.
4. Edit the [Settings] section as follow s, substituting <value> for a w hole number or decimal value:
[Settings] PageSizeTolerance= <value>
5. Save the file.
Related Topics Batch Processing Overview
Reporting
LAW PreDiscovery™ provides support for generating a number of predefined reports as w ell as ad hoc reports based on the results of a query. Predefined reports available for all cases include the Page Properties and Tally reports. In addition, if electronic discovery is enabled the follow ing reports are available: ED Loader Session, Exception, and Deduplication or Inter-Case Deduplication reports. The type of deduplication used in a case determine w hich type of report w ill appear in the View Reports dialog box. For more information on deduplication reports, see the Files By Type and Files By Type Summary topics.
In this section
Viewing ReportsProvides instruction for opening a report for view ing, configuring grouping of report data, adding a logo to the report, and generating report output as a PDF file or other format. Case Summary Report
Provides instructions for creating a report of the status of current optical character recognition (OCR) operations.
Deduplication Reports
Provides instructions for creating a summary report or a detailed report of deduplication information for the current case.
ED Loader Session Report
Provides instructions for creating a summary of the records logged for each ED Loader Session imported into a case.
Exception Report
Provides instructions for creating a report of the records that w ere filtered or that received either errors or w arnings during the ED Loader import process.
Provides instructions for creating a report that contains a list of native files associated w ith electronic discovery records.
Files By Type Summary Report
Provides instructions for creating a condensed version of the Files By Type report by providing native file counts and sizes per source application.
Page Properties Report
Provides instructions for creating a report that contains source, size, and color information at a page level for images in a case.
Tally Report
Provides instructions for creating a report that lists the unique values that may be present in a system field or in a user-defined field, follow ed by a count of the unique values. Using Grids for Reporting
Discusses how to use the standalone grid to generate reports that apply to coding and to the results of queries. Also discusses the use of grids to create reports of the import results from ED Loader sessions.
Viewing Reports
After you open a report for view ing, you can configure grouping of report data, add your ow n logo to the report, and then generate an output as a PDF file or other format.
To view a report
You have several choices for accessing reports. 1. Do one of the follow ing:
In the main w indow , on the toolbar click the View Reports button: . Or
On the File menu, click Administration, and then click View Reports. Or
From a grid display, on the Tools menu, click View Reports. The View Reports dialog box appears.
2. Select a report, and then click View Report.
If the View Reports dialog box is launched from a grid, or if a grid is active when the tool is launched, certain reports can be limited to the current record set loaded in the grid.
To remove or restore grouping
By default options to group reports are enabled in the View Reports dialog box.
To remove grouping, in the options area click the Alphabetical button located above the options. The group headers, Global Settings and Options, w ill be removed.
To restore group headers, click the Categorized button.
To add a logo to reports
Global settings apply to every type of report and w hen they are changed, the changes persist to the other reports as w ell. The Options located below the Global Settings are
report-specific and therefore w ill change each time a new report is selected in the left panel. These options are discussed in the separate topics for each report (see the "Report Types" section below ).
1. Open the View Reports dialog box. For more information see To view a report section in this topic.
2. Configure options for adding logos according to your needs by consulting the follow ing table:
Option
Procedure
Notes
Display Custom
Logo 1. Set this option to True.
2. Specify the path to the logo file in the Logo Filename setting.
Enables (or disables) a custom logo.
The logo appears on the first page of the report.
Logo Filename 1. Click the ellipsis (...) button in the second column beside this setting. 2. Brow se to the desired image file
(.bmp, .jpg, or .gif), and then click
Open.
The path to the image w ill appear in the field.
For the logo to appear, the
Display Custom Logo setting
must also be set to True.
Logo Location Set the location to one of the follow ing:
Top Left Top Right Bottom Left Bottom Right
Determines w here logo is located on the first page of the report.
To generate reports in PDF and other formats
1. On the File menu, click Administration, and then click View Reports. Or
From a grid display, on the Tools menu, click View Reports. The View Reports dialog box appears.
2. Select a report, and then click View Report. 3. Click the View Report button.
4. Save the file using one of the file types provided in the Save as type drop down.
If on your computer you have installed a print driver that can save print jobs to file, such as Adobe Acrobat, you can optionaly click Print, and then print the report to the print driver that generates PDF or other file output.
Related Topics
ED Loader Session Report Exception Report
Files By Type Report
Deduplication Reports Page Properties Report Tally Report
Case Summary Report
The Case Summary report provides a quick status of current optical character recognition (OCR) operations. This report is useful for answ ering basic questions related to billing and project status. The report lists these items:
Number of documents. Total pages.
Number of pages flagged for OCR. For more information, see Flagging Documents/Pages for OCR.
Number of pages completed.
This summary can be incorrect if invalid records or page counts exist in the database, both of w hich can be detected and/or corrected w ith the Scan for Errors functions.
To create a Case Summary report
1. On the File menu, click Administration, and then click Case Summary. LAW prompts you to enter a date range for narrow ing summary information.
2. Do one of the follow ing:
Click No to generate a report for all dates. Or
Click Yes to specify a date range. Use the calendar controls to specify a start and end date. These dates apply to document creation dates. After you have selected a data range, click OK.
Related Topics Working with Existing Cases
Reorganizing Documents
Launching the Grids
Deduplication Reports
The Deduplication report provides a summary and detailed view of deduplication information for the current case.
If documents in the LAW PreDiscovery™ case w ere deduplicated using the ED Loader or LAW's internal Deduplication Utility or if the documents w ere not deduplicated at all, the "Deduplication Report" w ill be available in the View Reports dialog.
If the case w as last deduplicated using the external Inter-Case Deduplication utility, then the "Inter-Case Deduplication Report" w ill be displayed in the report list. This report
includes the same information as the Deduplication report, but includes data from any cases the current case w as deduplicated against. This report does not list the case name at the top since the information may apply to more than one case.
Report options
In addition to the Global Settings, the follow ing options are available for the tw o deduplication reports:
Display Custodian Details - When set to True, the report will contain a "Custodians"
section. All custodians in the case w ill be listed here and a duplicate summary w ill be included for each custodian. Set this option to False to exclude the Custodians section from the report.
Display Parent/Dup File List - When set to True, the report will contain a "Parent/
Duplicate File List" section w hich lists every parent and duplicate record (minus attachments) in the case(s), follow ed by duplicate totals.
Group File List By - If the Parent/Duplicate File List is included in the report (see above
option), the Group File List By option can be used to group the file list by parents or duplicate records.
Report contents
Tw o sections exist below the Summary header in the deduplication report: Process Summary and Duplicates.
Process Summary
In the Process Summary, the Total Records count represents the number of records in the current LAW case (and member cases if the report spans multiple cases).
The Processed count represents the number of records that have been deduplicated, w hile the Unprocessed count represents the number of records that have not been deduplicated (DupStatus = Null or U). Files that are ineligible for deduplication (i.e. images imported via raw image import) w ill also be included in the Unprocessed count.
Duplicates
The Duplicates section lists the duplicates and file size totals. The Total Duplicates count is the total number of records that have been flagged as duplicates (DupStatus=G or C). The "Dup. (non-att.)" count is the number of records that are duplicates (DupStatus=G or C) and may or may not have attachments. The "Dup. Atts" count is the number of records that are duplicates (DupStatus=G or C) and are attachments. For example, an e-mail item containing
