Administrating LAW PreDiscovery - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.5/... · Chapter 3 Administrating LAW PreDiscovery 17 1 Compacting the Database ... Acquiring

Administrating LAW PreDiscovery

• 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 GuideLAW PreDiscovery™, Version 6.5

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 ofany 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. LAWPreDiscovery is a registered trademark of LexisNexis, a division of Reed Elsevier Inc. Other products or servicesmay be trademarks or registered trademarks of their respective companies.

© 2015 LexisNexis. All rights reserved.

LAW PreDiscovery™Concordance®CaseMap®LexisNexis® Early Data Analyzer

LAW PreDiscovery™

Version: 6.5.25LAW Prediscovery Release Date: November 19, 2013

Administrating LAW PreDiscovery User Guide

3Contents

3


Table of Contents

Chapter 1 About LAW PreDiscovery 6

Chapter 2 What's New in LAW PreDiscovery 9

Chapter 3 Administrating LAW PreDiscovery 17

................................................................................................................................... 181 Compacting the Database

................................................................................................................................... 192 Reviewing Errors

................................................................................................................................... 213 Reorganizing Documents

................................................................................................................................... 224 Scanning for Errors

................................................................................................................................... 295 Validating Document Ranges

................................................................................................................................... 316 Extracting Subsets

................................................................................................................................... 317 Run Commands

................................................................................................................................... 338 Full-text Indexing

................................................................................................................................... 439 Configuring LAW and SQL Server

................................................................................................................................... 4710 Tracking Page Source, Size, and Color

................................................................................................................................... 5011 Reporting

.......................................................................................................................................................... 52Viewing Reports

.......................................................................................................................................................... 56Case Summary Report

.......................................................................................................................................................... 58Deduplication Reports

.......................................................................................................................................................... 60ED Loader Session Report

.......................................................................................................................................................... 64Exception Report

.......................................................................................................................................................... 65Files By Type Report

.......................................................................................................................................................... 67Files By Type Summary Report

.......................................................................................................................................................... 68Folder Summary Report

.......................................................................................................................................................... 70Page Properties Report

.......................................................................................................................................................... 71Tally Report

.......................................................................................................................................................... 73Using Grids for Reporting

Chapter 4 Reference Information 76

................................................................................................................................... 761 Glossary

................................................................................................................................... 852 Languages

................................................................................................................................... 873 License Matrix

................................................................................................................................... 934 Field Descriptions

................................................................................................................................... 1245 Unicode Support

................................................................................................................................... 1266 Keyboard Shortcuts

................................................................................................................................... 1297 Contacting LexisNexis

LAW PreDiscovery4


Index 131

Chapter

1

About LAW PreDiscovery

Administrating LAW PreDiscoveryUser Guide

LAW PreDiscovery6


About LAW PreDiscovery

LexisNexis® LAW PreDiscovery™ helps legal professionals and their service providers meet theincreasing demands in the discovery of printed and electronic documents. By integratingproduction-level scanning with robust e-discovery and data processing features, LAWPreDiscovery 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 millionsof e-mails and attachments from mail stores, to full text indexing, querying, and exporting tomany 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 with the LAWPreDiscovery 6.0 suite. Use it to implement high volume electronic discovery productions.Early Data Analyzer indexes, filters, and produces export sets. Culled documents are passeddirectly to LAW for full expansion and production.

Creating and managing cases

LAW PreDiscovery centers all activities, including data collection, processing, and export onthe case. Each case corresponds to a database file, which tracks all source files andproduction files, including graphics and text.

In the process of creating a new case, you select a database engine, create and name thedatabase file, establish a folder structure for documents, and define any additional databasefields you will 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 following activities that bring documents into the case:

Import electronic discovery using ED Loader to extract text and to record documentmetadata 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 with data fields.

Performing quality control

The exact nature and timing of quality control activities vary greatly, depending on the typeand quality of source documents. Quality control typically involves multiple activities spreadthroughout the discovery project:

Error correction, for example: reviewing and fixing processing errors, keeping detailedlogs of warning and other error conditions, and alerting you to suspected fileextensions.

About LAW PreDiscovery 7


Tag documents that contain specific text or metadata attributes for the purpose of

narrowing consideration to pertinent documents or pages.

Deduplicate files that were imported during electronic discovery.

Fix problems with 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 or PDF, printing, andoptical character recognition (OCR). LAW PreDiscovery lets you take batch processing to anew level by combining the processing power of multiple computers to join distributed batchprocessing of large jobs.

Exporting

LAW PreDiscovery provides a wide range of options for exporting to litigation supportapplications in a variety of standard formats, including: native files, images, coded data, andOCR text.

For information on LAW PreDiscovery and other litigation support products by LexisNexis,please visit the LexisNexis PreDiscovery website.

http://law.lexisnexis.com/law-prediscovery

Chapter

2

What's New in LAW PreDiscovery


What's New in LAW PreDiscovery 9


What's New in LAW PreDiscovery

LAW PreDiscovery™ 6.5.25 and Early Data Analyzer 1.5.5 introduce the following features andproduct enhancements:

LAW PreDiscovery

Batch Processing

Metadata can now be extracted from files after the files have been imported into LAW

PreDiscovery using the new Document Processing/Analysis batch process.

Adobe Acrobat PDF files can now be split into separate PDF files by bookmark. This

enhancement also added two new fields to LAW PreDiscovery: HasBookmarks andBookmarkName.

The custom metadata extraction and split PDF batch process settings are defined in theDocument Analysis Options dialog box (Tools menu > Batch Process > Options menu >Document Analysis Options).

For more information, see: Extracting Custom Metadata and Field Descriptions.

Exports

Custom fields can now be created for exports in export profiles. Custom fields can be

used to create fields that combine multiple LAW PreDiscovery fields into a single field,customize existing fields, and export the same fields more than once. Custom fields arecreated and maintained in the Custom Field Editor dialog box. (Tools menu > ExportUtility > Fields tab > Custom Fields button).

For more information, see: Fields Tab.

Grid View

Records in the Grid View can now be sorted by a field from the column headers in the

Grid View. Clicking the column header for a field sorts the records in ascending ordescending order. Sorting by the column headers allows you to do layered sorting,because the existing sort order and grouping are retained.

For more information, see: Customizing the Grid View.

LAW PreDiscovery10


Indexing

LAW PreDiscovery now has multi-threaded, partitioned indexing. With this enhancement,

the Maximum index partitions and Maximum index workers fields are now added to theIndexing tab in the Options dialog box (Tools menu > Options). These fields determinethe maximum number of index partitions for the machine running the indexing process,and the maximum number of index workers per processor. You can use up to 16 indexpartitions and 16 index workers for indexing.

This enhancement also removed the Run index process in background until canceled(auto-index mode) and Auto-start indexing prior to electronic discovery imports checkboxes from the Indexing tab in the Options dialog box.

For more information, see: Full-text Indexing.

Licensing

The Near-Duplicate Analysis license is now renamed to the Near-Duplicate/Email Thread

license. The Near-Duplicate/Email Thread license provides access to the Near-Duplicate &Email Thread Analysis utility.

For more information, see: License Types and About Near-Duplicate & Email Thread Analysis .

Near-Duplicate & Email Thread Analysis

The Near-Duplicate Analysis utility is now renamed to the Near-Duplicate & Email Thread

Analysis utility. The Near-Duplicate & Email Thread Analysis utility, in addition toidentifying the near-duplicate families and clusters in a case based on the content of thedocuments, now also identifies email threads within a case.

Performance for the Near-Duplicate & Email Thread Analysis utility has been improved.

The Preserve existing near-duplicate families and master documents check box has also

been added to the Near-Duplicate & Email Thread Analysis utility. The check boxdetermines whether the Near-Duplicate & Email Thread Analysis utility will retain theexisting near-duplicate family and master document IDs already assigned to thedocuments when the utility previously ran. For more information, see: Running Near-Duplicate & Email Thread Analysis.

The Isolate new documents to separate results set check box is now removed from the

Near-Duplicate & Email Thread Analysis utility.

You can access the Near-Duplicate & Email Thread Analysis utility by clicking Near-

Duplicate & Email Thread Analysis on the Tools menu. The Near-Duplicate & Email ThreadAnalysis utility uses the LexisNexis Near Dupe and LexisNexis Email Thread engines.

The Near-Duplicate & Email Thread Analysis utility requires the Near-Duplicate/Email

Thread license. For more information, see: License Types.



When the Near-Duplicate & Email Thread Analysis utility runs, the utililty automatically

creates and populates 7 near-duplicate fields and 12 email thread fields for the case.

Near-Duplicate Fields:ND_ClusterID

ND_ContentHash

ND_FamilyID

ND_IsMaster

ND_ResultSet

ND_Similarity

ND_Sort

Email Thread Fields:ET_Conversants

ET_Inclusive

ET_InclusiveReason

ET_IsMessage

ET_MessageId

ET_MetaUpdate

ET_ParentId

ET_ThreadId

ET_ThreadIndex

ET_ThreadModified

ET_ThreadSize

ET_ThreadSort

For more information, see: About Near-Duplicate & Email Thread Analysis and FieldDescriptions.

OCR

The OCR Accuracy field is now added to LAW PreDiscovery. The OCR Accuracy field is used

to track OCR accuracy for each case document. The OCR Accuracy field displays thepercentage of accuracy for a file's document-level OCR.

For more information, see: Field Descriptions.

LAW PreDiscovery12


Early Data Analyzer

Exports

Export settings for LAW PreDiscovery and native export sets can now be saved to exportprofiles. Export profiles and their settings can be applied to other LAW PreDiscovery andnative export sets in the current case or other Early Data Analyzer cases. When you createan export profile, the following export set settings from the current export set are saved tothe profile:

Output Concordance DAT (native)

Output EDRM 1.0 (native)

Fields to export (native)

Include native files (native)

Include text (native)

Include e-mails in thread (Outlook only) (LAW and native)

The following settings are not saved to export profiles:

Export # (native)

Output directory (native)

Target LAW Case (LAW)

Excluded and Included tag IDs (LAW and native)

For more information, see: Exporting.

Imports

Early Data Analyzer now supports EnCase Logical Evidence Files (LEF) *.L01 forensic

image files and both logical and physical *.E01 forensic image files.

Supported Forensic Images

ForensicImageFormats

LogicalDrives (C:\)

PhysicalDrives(DISK1)

SinglePartitionSupport

Multi-partitionSupport

SupportedFile Systems

E01 (.e01) Y Y Y Y FAT (FAT16),FAT32,NTFS, HFS+(non-casesensitive)

L01(.l01) Y N/A N/A N/A N/A



DD/RAW(.001, .dd)

Y Y Y Y FAT (FAT16),FAT32,NTFS, HFS+(non-casesensitive)

For more information about importing, see Importing.

Mapping Sources

The source file directory for a case's source files can now be modified after case files areimported into Early Data Analyzer. When the directory needs to be changed or moved,you can update the directory for individual sources or multiple sources in the new MapSources dialog box. The Map Sources dialog box can be accessed for a case by clicking

Map Sources on the tool menu, .

For more information, see: Mapping Sources.

Reports

The Search Report now displays the selected search filters for each search term. The SearchReport provides a summary of the search hit results for the search terms defined in the currentcase grouped by search term and custodian.

For more information, see Creating Reports.

Searching

In Early Data Analyzer, the user interface of the Search Request pane on the Search tab

has been updated to more closely match the look and feel of the Search tab in Early DataAnalyzer Web. With this enhancement, search queries are now created in the NewSearch Term dialog box, and are now edited in the Edit Search Term dialog box. The daterange, search filters, fields, dictionary, and save functionality has also been moved to theNew Search Term and Edit Search Term dialog boxes.

Search filters can now be applied to search queries to help fine-tune your query and

search results. When a search filter is applied to a search query, the filter icon, , isdisplayed for the query in the new Filters column on the Searches tab in the SearchRequest pane. There are six search filter types available:

Date Range

Custodian

Import Sessions

LAW PreDiscovery14


Tags

Folder or File

Other Search

For more information, see: To create and run a basic word search and To create and run afull-text search in the Running Searches topic.

Early Data Analyzer Web

Searching

Search filters can now be applied to search queries to help fine-tune your query and

search results. When a search filter is applied to a search query, the filter icon, , isdisplayed for the query in the new Filter column on the Search Request pane. There aresix search filter types available:

Date Range

Custodian

Import Sessions

Tags

Folder or File

Other Search

For more information, see: To create and run a basic word search and To create and run afull-text search in the Running Searches topic.

User Interface

In the document details pane on the Filters and Search tabs, the Retrieve document link

is now replaced with the Download document icon, , and the tags icon, , is moved

from the Tags field up to the top of the pane next to the Download document icon, .

For more information, see Filtering and About Searching.

For more information on this release and on previous releases of LAW PreDiscovery, see: Release Notes.



Chapter

3



Administrating LAW PreDiscovery 17



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 Viewer to review errors and warnings that may occurduring 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 outputfolder.

Run Commands

Explains how to access the command prompt directly from LAW PreDiscovery for thepurpose of starting external programs or running scripts.

Full Text Indexing

Explains what 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 work withLAW PreDiscovery.

Tracking Page Source, Size, and Color

Provides procedures to gather statistics on page source, size and color.

Reporting

Provides a detailed listing of the reports available to you.

LAW PreDiscovery18


Compacting the Database

Compacting should be done on a weekly basis at a minimum. However, if multiple users areperforming 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 thedatabase can provide the following 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 network latency associated with running queries on verylarge databases.

Database files tend to increases in size as information is added and removed. The spaceused by records is not reclaimed when records are deleted, causing the size of the databaseto grow over time. This unused space is removed during the compact operation, reducing thesize of the database. The size of the database before and after the compact operation willbe reported, so users can see how much space was recovered (Access only).

To compact the current database

On the File menu, click Administration, and then click Compact Database.

The Compact Database feature is not supported for SQL Server-based cases.



Related Topics


Reviewing Errors

You can use the Log Viewer to review errors and warnings that may occur during theseoperations:

Importing

Exporting

Batch Processing

Reorganizing

Scanning

Deduplication

Page Count Extraction

To start Log Viewer

You can start the Log Viewer in either of the following ways:

After processing the operation, if errors or warning conditions occurred, you areprompted to view the Log Viewer. You may choose to open the viewer at this time.

Or

1. From the main window, on the Tools menu, click Log Viewer.

The Open Error Log dialog box appears.

LAW PreDiscovery20


2. Do one of the following:

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 barshows the filename of the error log. Error logs for most processes are stored in <caseroot>\$Logs in *.csv format.

Tagging records for review

You can apply a Tag (Boolean) value to records shown in the Log Viewer. This action can beuseful for creating custom reports, reviews, and selecting items for further processing, etc.

1. Create a Tag (Boolean) field. For more information on creating tag fields, see CreatingTag Fields.

2. On the Tools menu, click Log Viewer.



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 will appear checked in the grid displays and set to <Yes> in the Indexdisplay.

Tag values cannot be toggled using this feature.

Related Topics

Viewing Reports

Batch Processing Overview

Creating Tag Fields


You can reorganize your documents based on the ranges specified in a selected range file.

Note the following facts when considering when 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.However, information not associated with the leading document for a range will bediscarded.

If an error does occur you might see a message stating that the image and OCR text arenot synchronized. In such cases, the reorganize process will stop and the OCR data willhave to be removed or corrected for the image.

This issue can occur any time the OCR process stops before it completes. For example, theissue could result if the OCR engine crashes, if you attempt to insert new pages into adocument after the OCR process ends, or if you try to merge documents with incompleteOCR.

To reorganize documents

1. Click File, click Administration, and then click Reorganize Documents.

LAW PreDiscovery22


2. Select a range file. A range file is a comma-delimited text file consisting of two fields:BegDoc# and EndDoc#.

LAW PreDiscovery™ will begin rebuilding documents based on the specified ranges.

Related Topics

OCR Overview

Scanning for Errors

As cases increase in size, you will want to detect and eliminate certain types of problems in thedatabase. The Scan for Errors feature provides a means to automatically search the database



for some common problems. You can run the Scan for Errors feature on all documents in thecase, the current case folder, or the current search results. The Scan for Errors feature can beaccessed from the File > Administration menu or the Database Query Builder dialog box.

Note the following facts about the Scan For Errors feature:

Errors that are detected are logged in a file named scandb.log that is kept in the tempfolder (%temp%\Law50\Log).

When the scan is complete, if errors were found LAW PreDiscovery™ will present the optionto view the log file.

To scan for errors from the File menu

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 scanare described in the following 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 within the current folder for

LAW PreDiscovery24


errors.

Search Results Scan documents in the current search results. This option isonly available when the Scan for Errors dialog box is openedfrom the Database Query Builder dialog box. For moreinformation, see To scan for errors from the Query Builder.

Ignore NativeDocuments

Prevent native documents (records without images) from beingrepeatedly scanned and logged as errors.

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 Windows or some otherprogram outside of LAW to delete or move files.

These actions could cause LAW to contain records that do notpoint to valid images. These extra records can affect processingand summary functions, so users should remove them.

Find blank/missingPage IDs

Find documents with pages that have blank or empty Page IDentries.

Whether intentional or simply operator errors, certain exportformats require non-blank Page ID entries for renaming orlinking purposes. This option provides a way to find thedocuments with blank entries so users can take theappropriate measures to correct them.

To add page IDs to pages that have blank or empty Page IDentries 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 withan incorrect number of page-level records. Since each documentshould have the same number of page-level records as thedocument's page count, this check ensures (for example) that a5-page document has exactly 5 records in LAW's page table. Ifany missing page records are found, LAW will automaticallysequentially number the PageID values of the missing page levelrecords 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, however, there may be breaks in the numberingsequence. This option allows users to find these breaks toensure that all pages are accounted for and to confirm thesebreaks, if any, are intentional and correspond to the originaldocuments.

Remove duplicate/orphan page records

Fix duplicate page records or records that consist of orphanpages.

Duplicate page records can result when a document contains



two "page 3's" for example. Since there can only be one 'page3', this record is safe to remove. Duplicate records can bedetected while numbering a range of documents as it causes aduplicate PageID to be detected during this process.

An orphan page record is a page level record that no longerbelongs to an existing document. This may have occurred aftera document was deleted, but a failure occurred deleting thepage records for the deleted document. These records are alsosafe to remove from the database.

Verify Page Counts Validate the page count of every image in the case that has arecord.

LAW PreDiscovery opens every image and compares the actualpage count with 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 isselected. Because every image has to be opened, this optioncan be very time consuming for large cases. However, thisoption has several benefits. First of all, it ensures that the totalpage count displayed in the Case Summary is accurate forbilling purposes. Second, by opening every image file, itensures that none of the images have become corrupted (ifthey are, it will be logged). Third, it ensures that there are noexcess Page ID entries (entries for pages greater than theactual page count) that can affect the export process.

To scan for errors from the Query Builder

1. Start the Query Builder. Do one of the following:

From the main window, on the Tools menu click Search Records.

Or

On the ribbon, click the Search Records button ( ).

The Database Query Builder dialog box appears.

LAW PreDiscovery26


2. Create the search query for the search results you want to scan for errors.

For more information about creating search queries, see Creating Queries and Full TextSearching.

3. Select the output options as needed:

Return all Page ID's with query results - Select this option to return a page-levelquery for the returned documents. The grid view will display a record for every page ofeach document. Additional page-level fields also become available after selecting thisoption.

Return parent/attachment groups - Displays documents matching the specifiedsearch criteria and will also display any parents or attachments of those documents.This does not imply that both the parent/attachments also match the search criteria,however. Enabling this option may require additional time for the query to returnresults.

Use NOLOCK setting to improve performance (SQL only/read-only) - This optioncan help to improve performance of queries of SQL Server-based cases. With thisoption, the result set is read-only, and updates will not be available in the grid. TheNOLOCK setting should only be used in cases where updates in the grid are notnecessary, for example, when executing a query that will be used to run a batchprocess or export.



4. In the Send Results To list, click Scan For Errors.

5. Click Execute.

Clicking Execute opens the Scan for Errors dialog box. The Search Results option andIgnore Native Documents check box are automatically selected in the Documentssection.

6. Select options to customize the scan and then click Begin. Options to customize the scanare described in the following 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 within the current folder forerrors.

Search Results Scan documents in the current search results. This option isonly available when the Scan for Errors dialog box is openedfrom the Database Query Builder dialog box.

Ignore NativeDocuments

Prevent native documents (records without images) from beingrepeatedly scanned and logged as errors.

Find invalid records (missing images)

Verify that each record in the database has a correspondingimage.

LAW PreDiscovery28


Remove if found Remove invalid records.

This option is useful if you have used Windows or some otherprogram outside of LAW to delete or move files.

These actions could cause LAW to contain records that do notpoint to valid images. These extra records can affect processingand summary functions, so users should remove them.

Find blank/missingPage IDs

Find documents with pages that have blank or empty Page IDentries.

Whether intentional or simply operator errors, certain exportformats require non-blank Page ID entries for renaming orlinking purposes. This option provides a way to find thedocuments with blank entries so users can take theappropriate measures to correct them.

To add page IDs to pages that have blank or empty Page IDentries 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 withan incorrect number of page-level records. Since each documentshould have the same number of page-level records as thedocument's page count, this check ensures (for example) that a5-page document has exactly 5 records in LAW's page table. Ifany missing page records are found, LAW will automaticallysequentially number the PageID values of the missing page levelrecords 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, however, there may be breaks in the numberingsequence. This option allows users to find these breaks toensure that all pages are accounted for and to confirm thesebreaks, if any, are intentional and correspond to the originaldocuments.

Remove duplicate/orphan page records

Fix duplicate page records or records that consist of orphanpages.

Duplicate page records can result when a document containstwo "page 3's" for example. Since there can only be one 'page3', this record is safe to remove. Duplicate records can bedetected while numbering a range of documents as it causes aduplicate PageID to be detected during this process.

An orphan page record is a page level record that no longerbelongs to an existing document. This may have occurred aftera document was deleted, but a failure occurred deleting thepage records for the deleted document. These records are alsosafe to remove from the database.

Verify Page Counts Validate the page count of every image in the case that has arecord.



LAW PreDiscovery opens every image and compares the actualpage count with 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 isselected. Because every image has to be opened, this optioncan be very time consuming for large cases. However, thisoption has several benefits. First of all, it ensures that the totalpage count displayed in the Case Summary is accurate forbilling purposes. Second, by opening every image file, itensures that none of the images have become corrupted (ifthey are, it will be logged). Third, it ensures that there are noexcess Page ID entries (entries for pages greater than theactual 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 following 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 withtwo 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 were applied correctly. If errors arefound after scanning, you can manually correct document breaks by using a combination ofthe Merge Documents and Split Documents functions.

To validate ranges

1. On the File menu, click Administration, and then click Validate Ranges.

LAW PreDiscovery30


2. Enter the path to a range file.

A range file is a comma-delimited text file that consists of two fields: BegDoc# andEndDoc#.

After a range file is identified, documents are compared against the range file in twopasses.

The first pass ensures that all pages fall within the specified ranges. This pass is onlyuseful if the documents and ranges are numbered sequentially with few or no gaps.Otherwise, LAW may report an excessive amount of errors. Any pages that do not fallwithin one of the specified ranges will be reported in the error log.

The second pass validates all of the specified ranges against the documents in thecase. Any ranges that are not found is reported.

3. To display the error log, click Yes.

Related Topics

Merge Documents

Split Documents

Reorganize Documents



Extracting Subsets

This feature extracts data and images of the current folder to a selected output folder. Thisfeature has been designed to be useful for creating partial backups and re-importing. Not allindexes and field properties are retained, so the output is not suitable for a standaloneworking case.

To extract subsets

On the Folder menu, click Extract as Subset.

This function works with either ADS or Access databases and always produces aproject.mdb file. This feature is not supported with SQL Server cases.

Related Topics

Export Utility Overview

Launching the Grids

Run Commands

This topic covers integration of LAW PreDiscovery™ with custom applications and scripts. Thistopic assumes you have intermediate to advanced programming skills. LexisNexis assumes noresponsibility for any damage done when you the LAW PreDiscovery run command to startexternal applications, scripts, commands or other active content.

LAW allows you to run executable files, commands, and scripts on LAW cases. Note thefollowing facts when you run external commands from within LAW:

The connection string to the current database is passed to the executable or script.

Only programs located within the <AppPath>\Commands folder can be executed from withinLAW.

If the external program contains a file description, this value will be used in the menu name.If no file description is found, the menu name is populated by the filename without theextension.

For a listing of index fields existing in LAW for both ED and non-ED-enabled cases, pleasesee the Field Descriptions topic.

LAW PreDiscovery32


To run an external command

Click Tools, and then click Run Command.

Create a connection string using code

The following code creates a connection string using Visual Basic. The VBA.Commandproperty will return the connection strings for both an Access database and an ADSdatabase.

Dim cnn as New ADODB.ConnectionDim rs1 as New ADODB.RecordsetDim rs2 as New ADODB.Recordsetcnn.Open VBA.Commandrs1.Open "tblDoc", cnn, adOpenKeysetrs2.Open "tblPage", cnn, adOpenKeyset

Command example

The following example command populates RecordType values in a LAW case. This commandis useful when you want to work with RecordType data without having to export first. Thiscommand is intended only to be used with LAW cases that are enabled for electronicdiscovery.

Populate RecordType Values

In this command, <RecordType> represents the field available only in the export utility. Thisfield is used to classify exported records as e-docs, e-mail, etc. The command can be used topopulate this field within the LAW case database thereby

Using the RecordType command

The following procedure describes how to use a command to populate RecordType values ina LAW case:

1. Create an index field to store the values. Note the following 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 thedocument-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 fieldare:

LOOSE E-MAIL ATTACHMENT

E-MAIL ATTACHMENT

E-DOC ATTACHMENT

LOOSE E-MAIL



E-MAIL

E-DOC

IMAGE ATTACHMENT

IMAGE

4. When the process has completed, a Success message box indicates the number ofrecords successfully updated.

Related Topics

Administration

Full-text Indexing

To perform full-text searches, the text for the records must first be indexed. The followingindexing 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 reindex documents, for example when you import a load file that contains recordswith text; or after you add text to previously indexed documents, as when you perform OCRor TIFF/PDF 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 with control over how certain words, punctuation, and othertext elements are handled during indexing. Auto-indexing can also be enabled from thisform.

1. On the Tools menu, click Options.

LAW PreDiscovery34


2. Click the Indexing tab.

The Indexing tab appears.

3. Set the general options as needed:

Accent-sensitive - The indexer will take accents into account in indexing words withthis option enabled. For most users this is not recommended because this optionincreases the chance of missing the retrieval of a document if an accent was omitted inone letter.

Automatically recognize dates, e-mail addresses, and credit card numbers - Enablethis 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 wordswhen this option is enabled. In a case-sensitive index, "CREDIT", "Credit", and "credit"would be three different words. This option can be useful, for example, when you aresearching for a term, such as a capitalized name that can be confused with a common



non-capitalized word.

Ignore duplicate documents during indexing - When enabled prior to indexing, LAWwill not index any duplicate records in the case. Duplicate records have a DupStatus ofeither G or C. The "parent" duplicate, DupStatus=P, is also included. Enabling thisoption can help to increase performance of indexing, searching, and review becauseonly text from unique files is added to the index.

Insert word breaks between Chinese, Japanese, and Korean characters - Check thisbox if you plan to search Chinese, Japanese, or Korean documents that do not containword breaks. Some Chinese, Japanese, and Korean text does not include word breaks.Instead, the text appears as lines of characters with no spaces between the words.Because there are no spaces separating the words on each line, the indexer seeseach line of text as a single long word. To make this type of text searchable, enableautomatic insertion of word breaks around Chinese, Japanese, and Korean charactersso each character will be treated as single word.

Use local folder for temporary files during indexing - During indexing, the dtSearchEngine may need to create temporary files to store word lists that are too large to fitinto memory. By default, these files will be placed in the index folder. Use this settingto instruct the indexer to use the local user’s temporary folder for these files. Theindexer will automatically delete the word list files when the index update completes.This is the recommended setting for cases on network drives, NAS, or SAN devices.

Maximum index partitions - By default, 16 is selected. You can select up to 32 indexpartitions. When 16 is selected, the machine running the indexing process will use upto 16 index partitions. The default index partition size is 125,000 documents. The indexpartition size determines the maximum number of documents that can be added to anindex partition before creating another partition.

Maximum index workers - By default, 2 is selected. You can select up to 16 indexworkers. When 2 is selected, the machine running the indexing process will use 2workers per available processor, with a limit of 8 workers. If a machine has more than8 processors, only a maximum of 8 workers will be used.

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" would be treated as "first class."

Treat hyphens as searchable - Hyphens are treated as searchable text. For example,"first-class" would be indexed as "first-class."

Ignore hyphens - Hyphens are ignored during indexing. For example, "first-class" wouldbe 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, seethe 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 willneed to be reindexed in order for the changes to be applied.

LAW PreDiscovery36


To change the order of text priority

Records in LAW can have up to three types of text: text extracted from document by opticalcharacter recognition (OCR), printed text, and text extracted from electronic documents. Onlyone 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 following facts that apply to text priority:

If the default values are used, OCR text will be indexed. If OCR does not exist for adocument, then printed text is used. If no OCR or printed text is available, extractedtext 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 fromconsideration for indexing.

To change text priority order


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.

For example, to include only a particular type in the index, such as Extracted, chooseExtracted 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, thecase will need to be reindexed 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. Adocument that is flagged for indexing means that it will be indexed when you run theindexing process manually. The steps required to flag or reset flags on documents dependon whether you are setting this on an OCR operation, a TIFF/PDF conversion, or whetherflagging or reset will occur on one folder or a set of folders.

To set the option to reset text index status for OCR

1. From the main window, on the Tools menu, click Options, and then click the OCR tab.

2. The OCR Options dialog appears.

LAW PreDiscovery38


3. Select [OCR] Reset text index status to reset text index status for OCR processing ofindividual records or batches of records.

Clearing this option will prevent LAW from re-flagging the document for indexing afterthe OCR process is performed. This means the OCR text for affected records will not besearchable in LAW.

To set the option to reset text index status for TIFF conversion

1. From the main window, on the Tools menu, click Batch Process.

2. In the Batch Process dialog, on the Options menu, click TIFF/PDF Output.

3. The TIFF/PDF Conversion Options dialog appears.



Do one of the following:

Select [TIFF Conversion] Reset text index status to reset the status and allowindexing to occur again.

Or

Clear [TIFF Conversion] Reset text index status to prevent LAW PreDiscovery fromre-flagging the document for indexing after the TIFF conversion and printed text iscreated. This means the printed text for affected records will 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 was deemed unusable and deleted outside of

LAW PreDiscovery40


LAW, the document could be manually re-flagged for indexing so the printed text for thatdocument would 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 ONto enable records to be reindexed, or OFF to prevent records from being reindexed.

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 _FTIndexfield 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 NewDocuments.

To enable automatic background indexing

An auto-indexing feature is available for indexing text as a background process, allowingtext to be indexed as records are being imported rather than waiting for an EDD import tocomplete.

1. On the Tools menu, click Options and then click Indexing.

2. Set options as needed.

When records with associated text are imported via the LAW case import, LAW willprompt 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 anytime thereafter.

On the Tools menu, click Fulltext Index, and then click Index New Documents.



This feature will index any records that are "flagged" to be indexed.

To reindex all documents

A case can be reindexed 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 indexhas somehow become corrupt.

_FTIndex field values

The _FTIndex system field is automatically created when a case is ED-enabled. It holds anumeric 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 reindexed.

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 the Full text search check box.

3. Click the Options button, and then click the Index Properties button.

The Full Text Index Properties dialog box appears. This screen provides details aboutthe full-text indexes for the current LAW PreDiscovery case, such as the size and thenumber of indexed documents and words in each index.

LAW PreDiscovery42


4. Select options as needed:

Purge Duplicates - This function removes all records that were flagged as duplicaterecords in LAW (DupStatus=G or C) from the full text index. This feature will first scan thecase 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 preventthese records from being included prior to indexing, use the Ignore duplicatedocuments during indexing option.

Compress Index - Compressing the index removes obsolete records from the index.Obsolete records may include documents that were deleted from the case or recordsthat were removed from the index using the Purge Duplicates feature. These obsoletedocuments are not returned in searches. If the "ObsoleteCount" value in this dialog isgreater than zero, use the Compress Index function.

Verify Index - This function will check the full text index for problems or corruption. If anyissues are discovered, an error will be returned after running the verify and the case willlikely need to be reindexed.

To configure ED Loader auto-indexing

1. In the main window, 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 tochoose whether to index the text of the new documents. If the setting is disabled,



import will complete without your having the option to perform full-text import.

Related Topics

Creating Tag Fields

Full Text Searching


Please contact LexisNexis for instructions on configuring SQL Server Express.

To enable support for SQL Server


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 runningSQL 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 when you create a case. Todisable the option, open any case in LAW. On the Tools menu, click Options, and thenclick the Preferences tab. Deselect the "Enable SQL Server/SQL Express Support"option.

Creating SQL Server user account(s)

There are two methods of specifying user accounts for use with SQL Server. You can useeither of these methods to allow LAW access to the LAW cases stored on the server.

LAW PreDiscovery44


Create a Global Default User for LAWPreDiscovery

Create Individual Users with IntegratedSecurity

Use this method when using SQL Server forother applications in addition to LAWPreDiscovery™. This option helps to preventusers of SQL Server from accessing andmodifying any other existing databases.

To create a generic global user accountusing this method:

Setup a SQL Server user with create/modify permissions.

The user name and password must be:

User: LAW_User

Pwd: law32sql

When using the default user, the securitymode for SQL Server must be set to SQLServer and Windows or mixed-modeauthentication.

This method allows a user to create SQLServer cases without adding a special user toSQL Server as long as the current user hasdatabase create permissions on the specifiedSQL Server. Windows integrated security maybe used when accessing/creating SQL Servercases.

If using this method, each user must besetup on the SQL Server to allow access tothe case.

To enable this feature:

Select the Use Windows NT integratedsecurity option when specifying thedatabase backend for newly created cases.

Detailed setup example

This section describes an example of a known, working setup of SQL Server 2008 Expressedition (not R2) on a computer running Windows XP.

Note the following about using SQL Server with LAW PreDiscovery:

All testing has been performed internally using SQL Server 2000, but SQL Server 7 orhigher should be supported.

Please contact LexisNexis Technical Support for instructions on configuring your instanceof SQL Server to run with LAW. The following listing provides sample values to use tosetup a configuration of SQL Server 2008 Express with Tools (not R2) is suitable fortesting new case production with LAW PreDiscovery. Use this as a starting point whendiscussing a production oriented SQL Server configuration with LAW PreDiscoverytechnical 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

Password = leave blank (default)



Database Engine Configuration dialog box: Mixed Mode (SQL Server authentication and

Windows authentication)

SQL Administrator password: select a password of your choice.

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.

Password: law32sql

Depending on the information security policies for your organization you may be able to

disable these password settings: Enforce password expiration and Enforce passwordpolicy.

Select Server Roles: enable dbcreator

Installation Steps

Step 1: Install Prerequisites

1. Install prerequisites as directed on Microsoft web site for the processor type andoperating system of your computer.

Prerequisites include:

.NET Framework 3.5 SP1 or .NET Framework 4

Windows Installer 4.5

PowerShell 1.0

2. After prerequisites are installed, restart the computer.

Step 2: Install SQL Server 2008 Express with Tools

SQL Server 2008 Express with Tools includes the Microsoft SQL Server Management Servicesconsole.

1. Download the installer file for SQL Server 2008 Express with Tools from the Microsoftwebsite.

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 existinginstallation.

5. After installation files expand click OK.

LAW PreDiscovery46


6. In the Product Key dialog box click Next.

7. In the License Terms dialog box, click I accept, if you accept the terms and then clickNext.

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 itis optional to change the instance name. Also, you can change the installation directoryor leave the default.

12. Click Next.

13. In the Disk Space Requirements dialog box, click Next, assuming you have requisitedisk 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 password 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 Serverauthentication and Windows authentication).

17. In the Enter password and Confirm password fields, type the SQL administratorpassword you want to use. Recommended: write the password down in a securelocation.

18. Under Specify SQL Server administrators, click Add Current User. Add other users asnecessary, 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 theprogress 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 programgroup.

2. Login to the new SQL Server instance.



3. Expand Security, right click Logins, and then click New User.

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 or PDF files created via TIFF/PDF Conversion within LAW PreDiscovery™ cases.This data is stored within the case database in the following 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 and PDF files created in LAW PreDiscovery via TIFF/PDF Conversion or by single-document TIFF or PDF conversion receive values for PageSource and PageColor. Images affected by the "Treat native TIFF/PDF as image for record (bypass conversion)"

setting do not receive a PageColor value.

LAW PreDiscovery48


Batch processing

A batch process is available to populate this missing information for imported images anddocuments converted to TIFF or PDF files. For more information on how to create a reportcontaining 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 within the database. Possiblevalues contained in these fields are listed in the following table. The lookup field names asreferenced in the database are shown in parentheses beside the field name displayed in theLAW interface. Also, the numeric values used in the database are listed in parenthesesbeside the textual value users will see in LAW.

Field Lookup field names

as referenced in thedatabase

Possible values

(database numeric value)

PageSource (SourceID) Feeder (1)

Flatbed (2)

Imported (3)

TIFF/PDF Conversion (4)

Manual TIFF/PDF 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 theabove 3 sizes

PageWidth -- Varies (Example: 8.5)

PageHeightVaries

-- (Example: 11)



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 thisinformation. PageSource is not affected during this process because the source can only becaptured at the time the image is acquired. As mentioned, imported images receive only aPageSource value and images or PDF files created by TIFF/PDF conversion only receivePageSource and PageColor values. This process is necessary to populate the remainingfields 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.

To set page size tolerance

LAW PreDiscovery50


A page size tolerance setting can be used to set a margin for the page size values. Thedefault 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 theapplication level.

To set page size tolerance

1. Use Windows Explorer to open the LAW PreDiscovery installation folder. By default thepath is:

C:\Program Files\Law50

2. Use Notepad or some other text editor to open the Law50.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 follows, substituting <value> for a whole number ordecimal 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 well asad hoc reports based on the results of a query. Predefined reports available for all casesinclude the Page Properties and Tally reports. In addition, if electronic discovery is enabled thefollowing reports are available: ED Loader Session, Exception, and Deduplication or Inter-CaseDeduplication reports. The type of deduplication used in a case determine which type of reportwill appear in the View Reports dialog box. For more information on deduplication reports, seethe Files By Type and Files By Type Summary topics.



In this section

Viewing Reports

Provides instruction for opening a report for viewing, 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 characterrecognition (OCR) operations.

Deduplication Reports

Provides instructions for creating a summary report or a detailed report of deduplicationinformation for the current case.

ED Loader Session Report

Provides instructions for creating a summary of the records logged for each ED LoaderSession imported into a case.

Exception Report

Provides instructions for creating a report of the records that were filtered or that receivedeither errors or warnings during the ED Loader import process.

Files By Type Report

LAW PreDiscovery52


Provides instructions for creating a report that contains a list of native files associated withelectronic discovery records.

Files By Type Summary Report

Provides instructions for creating a condensed version of the Files By Type report byproviding native file counts and sizes per source application.

Page Properties Report

Provides instructions for creating a report that contains source, size, and color informationat a page level for images in a case.

Tally Report

Provides instructions for creating a report that lists the unique values that may be presentin a system field or in a user-defined field, followed 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 tothe results of queries. Also discusses the use of grids to create reports of the import resultsfrom ED Loader sessions.

Viewing Reports

After you open a report for viewing, you can configure grouping of report data, add your ownlogo 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.


In the main window, 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 thetool is launched, certain reports can be limited to the current record set loaded in thegrid.

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 theoptions. The group headers, Global Settings and Options, will 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 when they are changed, the changespersist to the other reports as well. The Options located below the Global Settings are

LAW PreDiscovery54


report-specific and therefore will 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 inthis topic.

2. Configure options for adding logos according to your needs by consulting the followingtable:

Option Procedure Notes

Display CustomLogo

1. Set this option to True.

2. Specify the path to the logo file inthe Logo Filename setting.

Enables (or disables) a customlogo.

The logo appears on the firstpage of the report.

Logo Filename 1. Click the ellipsis (...) button in thesecond column beside this setting.

2. Browse to the desired image file(.bmp, .jpg, or .gif), and then click Open.

The path to the image will appear inthe field.

For the logo to appear, the Display Custom Logo settingmust also be set to True.

Logo Location Set the location to one of thefollowing:

Top Left

Top Right

Bottom Left

Bottom Right

Determines where logo islocated on the first page of thereport.

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.

The report opens in the Report Preview screen.



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, suchas Adobe Acrobat, you can optionaly click Print, and then print the report to the printdriver that generates PDF or other file output.

Related Topics


Exception Report



LAW PreDiscovery56




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 answering basic questions related to billing and projectstatus. The report lists these items:

Number of documents.

Total pages.

Number of pages flagged for OCR. For more information, see Flagging Documents/Pages forOCR.

Number of pages completed.

This summary can be incorrect if invalid records or page counts exist in the database, bothof which can be detected and/or corrected with 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 narrowing summary information.




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 enddate. These dates apply to document creation dates. After you have selected a datarange, click OK.

Related Topics

Working with Existing Cases


Launching the Grids

Scanning for Errors

LAW PreDiscovery58



The Deduplication report provides a summary and detailed view of deduplication information forthe current case.

If documents in the LAW PreDiscovery™ case were deduplicated using the ED Loader orLAW's internal Deduplication Utility or if the documents were not deduplicated at all, the"Deduplication Report" will be available in the View Reports dialog.

If the case was last deduplicated using the external Inter-Case Deduplication utility, thenthe "Inter-Case Deduplication Report" will be displayed in the report list. This reportincludes the same information as the Deduplication report, but includes data from any casesthe current case was deduplicated against. This report does not list the case name at thetop since the information may apply to more than one case.

Report options

In addition to the Global Settings, the following options are available for the twodeduplication reports:

Display Custodian Details - When set to True, the report will contain a "Custodians"section. All custodians in the case will be listed here and a duplicate summary will beincluded for each custodian. Set this option to False to exclude the Custodians sectionfrom the report.

Display Parent/Dup File List - When set to True, the report will contain a "Parent/Duplicate File List" section which lists every parent and duplicate record (minusattachments) in the case(s), followed by duplicate totals.

Group File List By - If the Parent/Duplicate File List is included in the report (see aboveoption), the Group File List By option can be used to group the file list by parents orduplicate records.

Report contents

Two sections exist below the Summary header in the deduplication report: Process Summaryand Duplicates.

Process Summary

In the Process Summary, the Total Records count represents the number of records in thecurrent LAW case (and member cases if the report spans multiple cases).

The Processed count represents the number of records that have been deduplicated, whilethe 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 viaraw image import) will also be included in the Unprocessed count.

Duplicates

The Duplicates section lists the duplicates and file size totals. The Total Duplicates count isthe 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) andmay or may not have attachments. The "Dup. Atts" count is the number of records that areduplicates (DupStatus=G or C) and are attachments. For example, an e-mail item containing



two attachments would be counted as 1 record for the Dup. (non-att.) section since it is themaster duplicate of the family; then, the two attachments would be counted as 2 records forthe Dup. Atts section since those records have received a duplicate status based on theirparent record. The file sizes of the duplicate files in LAW are provided beside these totals inboth MB and GB.

If the Display Custodian Details option was set to True prior to creating the report, the Custodians section will appear below the Summary.

The Custodians section contains the same information as the Summary, but is thesection is sorted by Custodian name and the data is broken down for each custodian inthe associated LAW case(s). In the above example, nine total records exist in the casewith a Custodian field value of CustodianB and four of those records are duplicates(DupStatus=G or C).

If the Display Parent/Dup File List option was set to True prior to creating the report, the Parent/Duplicate File List section will appear next.

This section contains a file listing of duplicates and their associated parent records forthe associated LAW case(s). This file list can be useful for listing and/or locating duplicaterecords for each original duplicate record in the case. Attachment records are notincluded in this list. For each record, the report displays the DocID, Custodian, Path(original), and the DupStatus value. In the above image, the shaded rows represent theparent records (DupStatus=P) and the duplicates are listed below their respectiveparent records. If the Group File List By option was set to Duplicates, the duplicate(s)would appear first, followed by the parent record. Below the file list, the report willdisplay a total count of global duplicates (DupStatus=G) and a total count of custodian-level duplicates (DupStatus=C).

Related Topics


Exception Report





Tally Report

LAW PreDiscovery60



The ED Loader Session Report provides a summary of the records logged for each ED LoaderSession imported into a case.

To create an ED Loader Session Report

Anytime after you run an ED Loader session, you can create a pre-formatted session report,suitable for reporting or billing purposes.

1. From the main window, on the File menu, click Administration, and then click ViewReports.

The View Report dialog box appears.

2. Click ED Loader Session Report.

3. Configure settings and options for the report, as needed:



Setting/option Steps

Add a custom logo to thereport.

1. Click Display Custom Logo, and then select True.

2. Click Logo Filename field, and then click the selection button(...).

3. Browse to a bitmap file, JPG or GIF file, and then click Open.

4. Click Logo Location and then select: Top Right, Top Left,Bottom Right, or Bottom Left.

Select sessions toinclude in the report.

1. Click Included Sessions field, and then click the selectionbutton (...).

2. In the Select Sessions dialog box, select each session toinclude in the report and then click OK.

Select a field by which tosort the report.

Click Sort Field, and then select Date Created or SessionLabel.

Specify a sort order. Click Sort Order, and then select Descending, Ascending, or

None.

4. Click View Report.

The Report Viewer opens with an ED Loader Session Report open for your review.

5. In the Select Summary Database dialog box, click a LAW PreDiscovery™ ED Summaryfile (*.EDSD) and then click Open.

6. Review the session report and view, print or save the report as needed.

If you choose to save the report, the following formats are available:

C1 Document (*.c1d) (default)

LAW PreDiscovery62


Adobe PDF (*.pdf)

OpenXml Excel (C1Report) (*.xlsx)

Microsoft Excel (C1Report) (*.xls)

Rich text (C1Report) (*.rtf)

Open XML Word (*.docx)

HTML (C1Report) (*.htm)

Enhanced metafile (*.emf)

Compressed metafile (C1Report) (*.emz)

Tiff image (*.tiff)

Png image (*.png)

Jpeg image (*.jpg)

Gif image (*.gif)

Bmp image (*.bmp)

Plain text (C1Report) (*.txt)

Report contents

The ED Loader Session Report consists of four primary sections:

Header Section

Session Summary Section

Session Detail Section(s)

Footer Section

These sections are described as follows:

Header Section: The Header Section contains the title of the report along with the name ofthe currently active case in LAW. If a logo image is specified to be displayed at the top of thereport then the logo will appear in this section.

Session Summary Section: The summary section consists of a summary of the data fieldscontained in each session detail section along with a total number of sessions specified inthe report. Note: if only one session is selected for the report, the summary section will notbe displayed.

Session Detail Section(s): The session detail section contains the data specific to a certainED Loader session imported into the current LAW PreDiscovery™case. The name of thesession assigned by the operator can be found in the grey bar at the top of each detailsection followed by the session’s ID and the created date of the session itself found in thetblEDSessions.ID table.

A definition of each field can be found below:

Status: The current state of the session. Possible field values include: Completed (non-recoverable), Aborted (recoverable), Cancelled (recoverable), Not Completed(recoverable), Mid-Inventory (non-recoverable), and Never Started (recoverable,editable).

Creator: Username of the operator who created the session followed by the



Workstation the operator used to create the session.

Processed: Is the number of items in the inventory list that have been processed.

Disc. Size: The discovered size consists of the total number of MB’s ED Loader wasrequired to process while analyzing each item in the inventory. This value includes thefile sizes from items such as zips, embedded items, e-mails, e-mail attachments, andother items that ED Loader may have processed during the analysis phase.

Disc. Items: The total number of discoverable items found after processing the itemslisted in the inventory.

Est. Time: ED Loader does not currently log the total amount of time spent importing aspecific session so this calculation is an estimate based on the Created date field foundin case’s document table. The Created field consists of a time stamp of when the recordwas added to LAW. By finding the minimum and maximum created dates for the recordsin a specific ED Loader session, the estimated processing time can be calculated.

Proc. Speed: Calculates the average speed using the total number of documents foundin the LAW case for the ED Loader session divided by the estimated time calculation. Thisis also an estimated value since the total processing time is only an estimate.

Session Contents

Written to LAW: Displays the total number of records written to the LAW case for aspecified session. This total will include duplicate records and/or records which qualifyfor a file type filter if the filter action is not set to ‘Exclude’. So if the record was writtento the LAW case, it will be included in this total.

Total Size: Displays the total file size of the records written to the LAW case.

File Type List: Displays a total file count and file size of the records written to LAWwith the following file types…

- E-Doc: Only E-Doc items and excludes attachments and archives.

- Embedded: Only embedded items of parents that are E-Docs.

- Archive: Only archive items that are not mail attachment items.

- Archive Attachments: Only archive items that belong to archives that are not mailattachment items.

- E-Mail: Only mail items by excluding E-Docs and embedded files. Includes native MSGand EML files.

- E-Mail Attachments: Only mail attachment items whose parents are not E-Docs.Encludes embedded items if the parent is an e-mail.

Errors/Warnings:

- Processing Errors: Counts the number of processing errors occurred in the currentsession.

- Commit Errors: Counts the number of database write errors occurred in the session.

- Warnings: Counts the number of warnings logged for the session.

- Incomplete: The number of records logged where the inventory status is either“Unprocessed” or “Processing”.

Filters:

- Conditionally Excluded: Number of records which were excluded because of being amail store item or an empty (0 bytes) file.

- File Type Filter: Number of records found to match the specified file type filter. Theserecords will be included in the total records written to LAW if the filter action is enabledto log the record.

- Suspect: Displays the number of records which appear to have suspect extensions.

- Duplicates: Counts the number of records found to be duplicates. The duplicate

LAW PreDiscovery64


‘Action’ must be set to log the records for these items to be included in the ‘Written toLAW’ calculation.

- DeNist (NIST Filter): The total number of records not written to LAW because of anexclusion caused by the NIST Filter.

Footer Section: The footer section is used to display a logo image if the bottom of the reportlocation is specified. Also, the printed date and page count of the report exists in thissection.

Related Topics

Viewing Reports

Exception Report





Tally Report

Exception Report

The Exception report provides both a summary and a detailed overview of ED Loader sessionexception data. This report focuses on records that were filtered or received errors or warningsduring the ED Loader import process.

Report options

In addition to the Global Settings, the following option is available for the Exception report:

Included Sessions - By default, this option will be set to All Sessions, meaning all sessionsin the current case will be included in the report.

Click the ellipsis button in the second column to launch the Select Sessions dialog toselect specific sessions.

Click on the Title or Created column header to sort the session list.



Report contents

The Summary section of the Exception report provides three sets of information: ItemSummary, Filters, and Errors.

The Item Summary displays a count of items processed (prior to expansion), itemsdiscovered (after expansion), records written to the LAW PreDiscovery™ case database(after expansion, filtering, errors, etc.), and records that were not written due to errors orfiltering. Post-process file sizes are also included for the last three items mentioned.

The Filters section displays a list of the ED Loader filters (conditional, NIST/NSRL,deduplication, and file type) and provides a count and post-process file size for each.

The Errors section displays the total counts for processing errors (errors that occurredduring processing, but records were likely still written to the case database), commiterrors (errors that occurred during processing and prevented the record from beingwritten to the case database), warnings, and incomplete records (records that will belisted in the Incomplete tab in the ED Loader's Session Viewer).

The Details section of the report provides a more detailed view of filtered records, filteractions, a list of warnings and error messages, and a list of sessions included in thereport.

Related Topics

Viewing Reports






Tally Report


This report contains a list of native files associated with electronic discovery records in a LAWPreDiscovery™ case. The records will be grouped by their file type description, such as AdobePortable Document Format (PDF) or HyperText Markup Language (HTML). Non-ED records mayoptionally be included in the report.

LAW PreDiscovery66


Report options

In addition to the Global Settings, the following option is available for the Files By Typereport:

Document Range - When the range is set to All Documents, the report will span the entireLAW PreDiscovery™ case. The Current Record Set option will only be available if one of thegrid displays are active when launching from File > Administration or when launching fromthe standalone grid display's Tool menu (View Reports).

File Type Filter - Three filters for the report are available:

All File Types - This option includes both supported and unsupported file types in thereport. The term "supported" refers to files with a valid source application assigned forprinting, such as Adobe Acrobat or Microsoft Word. Non-ED records may be includeddepending on the state of that setting (see #2).

Supported File Types - This option includes supported file types only in the report. Non-ED records may be included depending on the state of that setting (see #2).

Unsupported File Types - This option includes unsupported file types only in the report.Non-ED records are not currently included in this report, regardless of the state of the"Include Non-ED Records" setting.

Include Non-ED Records - When set to True, non-ED records such as scanned documentsor images imported via load file will be included in the report, provided the All File Types orSupported File Types filter is selected. These records will be grouped under the <Non-EDRecords> header.

Report contents

The contents of this report will vary depending on the selected options.

The report groups the entries by their file description or by the <Non-ED Records> headerfor non-ED records, such as scanned documents. The group header will also display the totalfile count for that type, the number of pages (if available), and the total file size. The pagecounts and file sizes are also available for each individual file. The Pages value is pulled fromthe PgCount field in the LAW case. If the PgCount is not greater than zero, LAW will checkthe EDPages field and use that value. The file sizes are post-process file sizes.

Related Topics

Viewing Reports


Exception Report






Tally Report


The Files By Type Summary report provides a condensed version of the Files By Type report byproviding native file counts and sizes per source application. This report does not include alisting of every native file path, which is the key difference between the Files By Type Summaryand the Files By Type report.

Report options

In addition to the Global Settings, the following option is available for the Files By Typereport:

Document Range - When the range is set to All Documents, the report will span the entireLAW PreDiscovery™ case. The Current Record Set option will only be available if one of thegrid displays are active when launching from File > Administration or when launching fromthe standalone grid display's Tool menu (View Reports).

File Type Filter - Three filters for the report are available:

All File Types - This option includes both supported and unsupported file types in thereport. The term "supported" refers to files with a valid source application assigned forprinting, such as Adobe Acrobat or Microsoft Word. Non-ED records may be includeddepending on the state of that setting (see #2).

Supported File Types - This option includes supported file types only in the report. Non-ED records may be included depending on the state of that setting (see #2).

Unsupported File Types - This option includes unsupported file types only in the report.Non-ED records may be included depending on the state of that setting (see #2).

Include Non-ED Records - When set to True, non-ED records such as scanned images orimages imported via load file, will be included in the report.

Report contents

The contents of this report will vary depending on the selected options. This report shows alisting of each unique file type included in the case. For each file type, the report provides atotal file count, the total number of pages, and the total file size (post-process). The Pagesvalue is pulled from the PgCount field in the LAW case. If the PgCount equals zero, LAW willcheck the EDPages field and use that value.

LAW PreDiscovery68


Related Topics


Exception Report




Tally Report

About Deduplication

Folder Summary Report

The folder summary report analyses a folder and generates a count of the following:

Documents scanned in a folder.

Total number of pages contained within the folder.

Total area of images.

Summarizing images at the folder level will often take longer than other summariesbecause of the area of all images must be totalled. The total area is often used for billingof oversized images.

To create a folder summary

1. In the main window, within the tree-view, select a folder to summarize.


In the main window, on the Folder menu click Summarize Images.

Or right-click the tree-view and then select Summarize Images.



A status bar appears in the window title bar that tracks the progress of the imagesummary operation.

If necessary, press ESC to cancel.

When complete, a Summarize Images dialog appears.

3. Take note of the folder statistics you need and then click OK.

The Summarize Images dialog closes.

LAW PreDiscovery70


Related Topics

Viewing Reports



Tally Report


LAW PreDiscovery™ can capture the source, size, and color information at a page level forimages in a case. The reporting tool utilizes this information to provide tallies of each propertyfor the images in a case and output the data to the Page Properties report.

Report options

In addition to the Global Settings, the following options are available for the Page Propertiesreport:

Document Range - When the range is set to All Documents, the report will span theentire LAW case. The Current Record Set option will only be available if one of the griddisplays are active when launching from File > Administration or when launching from thestandalone grid display's Tool menu (View Reports).

Group By Field (Primary) - Choose from one of the following options: Page Source,Page Size, or Page Color. The report will be grouped by the selected field.

Group By Field (Y-Axis) - Choose from one of the following options: Page Source, PageSize, or Page Color. The values in the selected field will appear in the Y-axis. The samefield cannot be selected for both the Primary and Y-Axis grouping options.

Report contents

The report layout will vary depending on the fields selected for the primary and Y-axisgrouping.

Since the above report is grouped by color, the primary sections are listed as Black & White,Color, and Unknown Color, as those were the colors found in this particular case. Withinthese sections, the Y-axis holds the various page sizes that were found in the LAW case.Totals for the page sizes or Y-axis fields are located at the end of the row (down the rightside of the report). The Source data (i.e. Feeder) and totals are listed horizontally in eachsection.

For more information on Page Properties report data see Tracking Page Source, Size,and Color.



Related Topics

Viewing Reports


Exception Report




Tally Report

Tally Report

The Tally report can be used to produce a report listing the unique values present in a systemfield or in a user-defined index field followed by the total number of times that unique valueexists in the selected index field.

Report options

In addition to the Global Settings, the following options are available for the Tally report:

Display Custodian Details - When set to True, the Tally report will be grouped by anycustodians that exist in the current case.

If the current case is not ED-enabled, Display Custodian Details will not be available.

Document Range - When the range is set to All Documents, the report will span the

entire LAW PreDiscovery™ case. The Current Record Set option will only be available ifone of the grid displays are active when started from the File menu, Administrationitem, or when launching from the standalone grid display's Tool menu (View Reports).

Field To Tally - Select the field to be tallied in the report from this drop-down list. Most

system fields and user-defined fields will be listed here - the following types of fields areexcluded from this list: page-level fields, fields with the Unique property applied, auto-increment fields, and any field starting with the character "_" (underscore). Field valuescontaining delimited lists such as “A; B; C” will be tallied as a single unique value ratherthan individual items.

LAW PreDiscovery72


While memo fields are included in the Field To Tally list, the data will automatically betruncated to 255 characters in the report.

Number of Columns - The data in the report can be displayed in 1, 2, or 3 columns on

each page of the report.

Sort Field - The following two options are available for sorting the data in the report:

Field Value or Totals. If Field Values is selected, the data will be sorted alphabeticallybased on the values located in the selected tally field. If Totals is selected, the data willbe sorted based on the tally results for each field value.

Sort Order - This option is used to sort the data in the "Sort Field" Ascending orDescending in the report. Choose None to avoid applying a specific sort order.

Report contents

The following Tally report sample is set to display custodian details and the tally field is setto DocExt, as indicated in the header below the LAW case name.

The number next to the custodian indicates the number of unique field values for thatcustodian. The number to the right in the heading indicates the total number of field valuesin the tally field for each custodian. The count of each unique value is displayed to the rightof the value below the section heading. For example, in the above report, five records existwith a value of "CustodianA" in the Custodian field and a value of "doc" in the DocExt field. Ifthe tally field does not contain a value for any of the selected documents, the report willinclude a <Null> entry.

Related Topics

Viewing Reports


Exception Report







Using Grids for Reporting

You can use the standalone grid to generate reports that apply to coding and to the results ofqueries in general. You can also use grids to create reports of the import results from EDLoader sessions.

To generate reports from standalone grids

If you need more detail than the Case Summary report provides, consider using either of thefollowing reports:

Report type Description Steps to run

The summary function inthe standalone grid display

Provides the number of fieldscoded and/or a summary on aspecific set of documents thatcan be identified by a query.

1.In the main window, on the Tools menu, click Display AllRecords.

2.The standalone grid opens. 3.In the grid on the Tools

menu, click Summary.

ED Reports in thestandalone grid

Provides electronic discoveryreports based on data loadedvia ED Loader.

1.In the main window, on the Tools menu, click Display AllRecords.

2.The standalone grid opens. 3.In the grid on the Tools

menu, click ED Reports.

Related Topics

Viewing Reports

Launching the Grids

LAW PreDiscovery74


Chapter

4

Reference Information


LAW PreDiscovery76


Reference Information

This section contains reference items.

In this section

Languages

Lists the languages LAW PreDiscovery can recognize in imported documents.

License Matrix

Lists each license along with available functionality.

Field Descriptions

Lists the field names, their return values, and other information pertaining to the fields thatare created by default with any LAW case.

Unicode Support

Provides description of Unicode support in LAW PreDiscovery.

Keyboard Shortcuts

Lists the keyboard shortcuts available in LAW PreDiscovery.

Contacting LexisNexis

Provides contact information for LexisNexis training, technical support, and sales.

Glossary

Glossary

A – B – C - D – E – F – G – H – I – J – K – L – M – N – O – P – Q – R – S – T – U – V – W – X – Y –Z

A – B – C

Acrobat

An application by Adobe Corporation for creating, reading, and editing PDF files.

archive file

Reference Information 77


A file type whose purpose is to store compressed copies of other files. The ZIP file is acommon type of archive file. Other types of archive files are:

RAR

JAR

GZIP

Z

TAR

ED Loader can import archive files and the files they contain either as multiple separate filesor as a single-file archive. The files within the archive are called attachments.

attachments

Attachments are files that are linked to or embedded within other files. For example, wordprocessor files are commonly found attached to e-mail messages.

An attachment relationship is displayed by indenting attachments below its parentdocument or archive.

Batch Process

The tool you use to perform page and document numbering, image cleanup, endorsingimages, OCR, printing, e-printing, scanning for suspected footers, TIFF/PDF conversion, andupdating page data. Batch processing can be done using just a single computer, or bydistributing the job among 2 or more networked computers by using the LAW ManagementConsole.

Batch Update

The tool you use from a grid display to update all currently visible records in a grid. Forexample, you could use the Batch Update tool to reassign all selected records to a differentcustodian. Before you can use the Batch Update tool, the field that you want to updatemust be unlocked for editing. See also Modify Fields.

Tools -> Batch Update

Bates numbering

A system for uniquely identifying individual documents or pages using a sequentialalphanumeric code.

case

1. In LAW PreDiscovery, the basic unit of organization for a set of source documents andsource metadata; and the metadata and operational settings associated with that set ofdocuments. 2. In the Early Data Analyzer component of LAW PreDiscovery, the basic unit oforganization for identifying sets of source documents, applying filters, exporting, and otherfunctions related to prefiltering.

Cases in Early Data Analyzer and LAW PreDiscovery are managed and stored in separatedatabases.

case name

Case name is the only property required when you create a database. LAW provides youwith a default name of New Case, but we advise you use a more descriptive name. LAWuses the case name as the root directory of the case.

LAW PreDiscovery78


compound document

A document created in one application that contains information created in anotherapplication. For example, a Word document can contain a worksheet developed in Excel.When you import compound documents you can specify whether a compound document willbe extracted or not.

custodian

The party responsible for safe keeping of documents. In ED Loader, prior to importing, youcan identify the custodian responsible for source documents. You can also access theCustodian Manager from ED Loader to manage the list of custodians available for a case. After import, the Custodian field is locked by default.

You can update the custodian after import. To do so, unlock the field for editing (Index ->Modify Fields), and then you can reassign the custodian manually by using the folder viewor Index tab. Or you can use the Batch Update utility accessible from a grid view.

D – E – F

data source

In LAW, a data source is the collection of MS Word docs, Excel worksheets, Adobe .pdf files, winzip .zip files, or others, to be imported into a case.

database

A type of data structure in which information is organized in one or more tables. LAWPreDiscovery cases are managed each in its own database file. See also table.

database engine

The software application used to organize, manage and query information stored in adatabase.

Deduplication Utility

The tool used for determining if there are multiple copies of the same document in a case.

default value

A value that LAW uses to populate a field. For example, the default value for the name of anew case is ‘New Case.’ The default value for Case is Active is ‘Yes.”

delimited text

A method of representing a table of information in a text file. In delimited text, the tablecolumns are separated by a designated character, such as a comma or tab character.

Example:

Order number,CustomerName

1,Smith

2,Jones

3,Brown



Typically a comma is used to separate values. A comma-separated value (CSV) file containscomma delimited text. One of the six kinds of source files you can import into a LAW case.

DocExt

DocExt is the name for one of the fields in the case database. It’s an abbreviation for‘document extension.’ See Document and Document Extension.

DocID

A unique value that LAW assigns to each document in a case.

DocID seed

A unique eight-digit number that you can specify as the starting point for documentnumbering before importing source docs into the case.

document

Used interchangeably with ‘file.’ a document is composed of one or more pages, has athree-character extension, and a unique ID created during import.

document extension

The suffix added to a filename that identifies the format of its contents. For example, thedocument extension of text files is TXT. During electronic discovery, LAW PreDiscoveryanalyzes file contents and records the file extensions in the DocExt field. If a file’s contentsdo not match the extension, the SuspectExt field is checked. For documents with suspectedextensions the OrigExt field is populated with the extension associated with the type of file,as inferred by LAW PreDiscovery.

document numbering

One of the batch processes applied to the results of an import session. You can opt fornumbering each page of every document, placing the number that LAW generates in thePageID field, and specifying the serial number to start counting from.

document review software

A type of litigation support software that consumes the export product of LAWPreDiscovery.

e-doc

Short of electronic document, in distinction to paper document. Any computer file identifiedas a source document in a case.

Early Data Analyzer

An optional software component of LAW PreDiscovery that performs high-speed prefilteringof large document sources.

electronic discovery

The process of finding information in electronic documents that is important to litigation. InLAW PreDiscovery you use ED Loader to import electronic files These files then constitutethe source documents for further discovery processing.

e-mail store

LAW PreDiscovery80


A type of file that contains individual email messages.

endorsing

Imprinting an image or PDF file, such as a logo on TIFFs. One of the batch processes appliedto the results of an import session. You can opt for endorsing every image or PDF file oronly the first page of every image or PDF file.

e-print

One of the batch processes that you can run on electronic documents. Prints the nativedocument using application software external from LAW PreDiscovery.

ErrorMsg

One of the built-in fields that LAW adds to the project database, error messages tell youthat LAW was either unable to extract data from a document, or write that data to thedatabase.

exclusions

Rules that prevent certain items from being processed.

export

The process of packaging documents and metadata in formats suitable for use by softwareapplications outside of LAW PreDiscovery.

Export Utility

Used for specifying what data will be exported to document review software. In the Exportutility you specify: the documents to be exported, the data fields and values of interest, theexport format, file name and path, and the naming scheme for exported files and folders.

field

One of the properties associated with a document or page. Examples include: documentidentification number (DocId), page identification number (PageID), document file extension(DocExt), etc. You use fields as a basis for filtering and analyzing documents. By default,LAW PreDiscovery creates and populates many fields for documents and pages that itprocesses. You can lock or unlock fields, or create new fields for your own purposes byusing the Modify Fields dialog box.

field list

A tool in the grid display you use to control which fields are visible in the grid. Checkeditems are visible, unchecked are not. All the properties associated with a document. Forexample the three fields in the screen shot tell you the date when a file was created, thedate for the last time it was modified, and the date when it was last printed. All of thesefields are populated by the operating system.

file description

Information about a document stored in the FileDescription field.

Folder

A container for documents and pages.

From:



Found in email, saved in the To field of the database so that you can search for all of theemails that were sent by an individual.

G – H – I

grid

A type of display in LAW PreDiscovery that enables you to view lists of document and pagerecords each in a single row in a table. You can configure grids to show whichevermetadata fields you are interested in. You can also define custom sorting and reuse savedviews.

The embedded grid is built into the main window of LAW PreDiscovery and is designed toprovide a snapshot view, showing just a few records and fields at a time. There is also astandalone grid that runs in its own window and can be more useful for reviewing largerrecord sets and more fields.

hash value

A value assigned to a particular document that uniquely identifies it. Hash values for filesare generated by the Deduplication utility to identify files suspected of being duplicates.There is a slight margin of error when creating file hashes and this factor decreases withthe strength of the working digest used to create the hash. For most projects, configuringthe Deduplication utility to use 128-bit strength is sufficient to positively identify duplicates.You can use a stronger digest for extremely high reliability but at a cost of processingefficiency.

header/footer

Batch process for adding headers and footers to the image of a page before exporting.

image

One of the three options for viewing a document in LAW. For example, the image tabcontains a picture of the document. The image is like a Xerox copy of a document. You canread it, but you can’t be change it.

image cleanup

A batch process for deskewing images, removing black borders found in the original images,or and random black marks that are not part of the image.

index field

A term that describes a field whose purpose is to hold sequential numbering of documentsor pages.

J – K – L

LAW case

One of the six kinds of source files you can import into a LAW case. LAW Case allow usersto import an existing LAW case (created in version 4.x or 5.x) into a new or existing LAWcase.

load file

One of the six kinds of source files you can import into a LAW case. Load files are produced

LAW PreDiscovery82


by litigation support applications for the purpose of packaging source files and otherinformation for import and export to other programs.

Log Viewer

A utility that provides access to LAW PreDiscovery logs.

M – N – O

mail store

A type of file that acts as a container for individual e-mail messages. Outlook mail storeshave the PST extension.

metadata

The information about a file, document or page other than its content. Examples ofmetadata include: author, date created, file size, file type, page dimensions, and manyothers. Much metadata is collected in the process of electronic discovery during the importprocess. Metadata is useful as a basis for creating queries.

Modify Fields

The tool you use to add, delete, lock, or unlock the fields associated with a case. See alsoBatch Update.

naming scheme

A set of rules you define that govern naming of various objects in LAW, such as projects,cases, and folders. Creating a naming scheme helps to maintain organization over sourcesand cases.

noise (visual)

Blemishes, dust, creases and other imperfections in images that can reduce the accuracyand speed of OCR. If scanned images are known to contain fair amounts of noise, you canrun a batch process to remove noise, before you run a batch process to OCR the images.

noise (words)

Words that are ignored by processes of text indexing and full text search. Examples ofnoise words include: are, the, and, but, in, etc.

Open File

An option for viewing files. Opens the native document using the source application of thedocument.

optical character recognition (OCR)

The capability of extracting text from images. LAW PreDiscovery can perform OCR onscanned pages of documents or pictures.

P – Q – R – S

path

A description of the location in the file system of a volume, file, or folder. For example, C:



\Program Files\test.txt represents the path to a test file located in the Program Files folderon the C: drive.

prefiltering

An optional action that can be performed on document sets prior to their import into a LAWPreDiscovery case. This function is accomplished by the use of the Early Data Analyzercomponent of LAW PreDiscovery.

Print Options

A batch process for preparing documents for output to a printer.

properties

The fields of a document.

For example one of the properties of a computer file is its name. Other properties wouldinclude the name of its author, the date it was created, the application that was used tocreate it.

quality control (QC)

The process of ensuring that the results of one phase of discovery are complete, accurate,and usable by subsequent phases. After import, for example, QC may consist of reviewingand resolving errors and warnings. Prior to OCR, QC may consist of applying image cleanupbatch processes to TIFFs.

Query Builder

A tool for finding documents and pages that match conditions you select based on field dataand/or full text conditions. Query Builder can send results to be sent to a grid for furtheranalysis or to a batch process, update utility, or direct to export.

range file

A range file is a delimited text file with two fields, BegDoc# and EndDoc#. You can use arange file when you want to reorganize documents, validate document ranges. or to importimages from a Doculex imagebase.

raw images

One of the six kinds of source files you can import into a LAW case, raw images are read-only image files without an accompanying database or a load file.

record

A single row in a database. In a LAW PreDiscovery case, a record is represented in a grid asthe values held in a row of fields. A record holds all the properties and values associatedwith a particular document or page.

recursive

Directing processing to take place on all items in a folder and then all its subfolders.Recursive processing helps to ensure all items in a deep folder structure are processed.

root directory

The top level folder in a directory structure.

LAW PreDiscovery84


session

A job run in ED Loader.

Session Browser

The utility in ED Loader for reviewing the details of previously run jobs.

session label

A unique name that LAW creates every time it’s importing files into the case.

For example, the default value for a session label is Session Created on [&Created]. WhenLAW starts a session, it reads the date and time from the computer and adds thatinformation to the phrase above

Session Viewer

A feature of the ED Loader that provides access to logs of previous import sessions.

source

A file or folder identified for processing by the Early Data Analyzer component of LAWPreDiscovery.

source name

The folder or file name associated with an item bound for import in ED Loader.

Source Queue

In ED Loader, a control that shows a list of items bound for processing. When you use EDLoader, you must specify items to import based on source type, for example, Outlook folder,files, file lists, etc. You can identify multiple items to import before you press the Startbutton. When you select an item for processing it is added to the Source Queue list.

SourceApp

A field that names the application that originally produced a document.

sources

The files that ED Loader imports into a case.

T – U – V

tag list

A text (.txt) or comma separated value (.csv) file containing a list of unique identifiers usedto locate the records in the case. The unique identifiers typically used in tag lists are theDocID or BegDoc# field. You use tag lists to help speed up the process of defining specialfields for a case. A tag list allows you to save and reuse special fields between cases. See Importing Tag Lists.

Text tab

One of the three options for viewing a document in LAW, the Text tab displays any textextracted from a document.



TIFF

One of several popular image file formats and the most commonly used image format usedin the legal profession for rendering documents.

TIFF/PDF conversion

The process of rendering scanned documents and other electronically stored information(ESI) into the TIFF image or PDF file format. The Batch Processing utility can then be usedto apply Bates numbering, OCR, and other actions to the files.

Title

A metadata field found in office documents. The document title and other metadata isextracted by ED Loader during the import phase of electronic discovery. After import, youcan use Query Builder to query documents by words found in the Title field.

To:

A metadata field for e-mail records that is extracted during the import phase of electronicdiscovery. After import, you can use Query Builder easily find all the e-mails in a documentcollection that were sent to a particular individual by creating a query on the To: field.

unique value

A value in a field that is unique to that field for all records in a database. For example, in anemployee database, no two records should have the same Social Security number.

value

The information stored in a particular database field for a specific record. For example, theAuthor field for a document might contain the value “Smith”.

W – X – Y - Z

Languages

LAW PreDiscovery can recognize the languages that exist in imported documents. For moreinformation see: Text Extraction. The languages recognized are listed in the following table:

Supported LanguagesLANG_AFRIKAANS LANG_FRENCH LANG_LUXEMBOURGISH LANG_SOMALI

LANG_ALBANIAN LANG_FRISIAN LANG_MACEDONIAN LANG_SORBIAN

LANG_ALSATIAN LANG_FULFULDE LANG_MALAY LANG_SOTHO

LANG_AMHARIC LANG_GALICIAN LANG_MALAYALAM LANG_SPANISH

LANG_ARABIC LANG_GEORGIAN LANG_MALTESE LANG_SWAHILI

LANG_ARMENIAN LANG_GERMAN LANG_MANIPURI LANG_SWEDISH

LAW PreDiscovery86


Supported LanguagesLANG_ASSAMESE LANG_GREEK LANG_MAORI LANG_SYRIAC

LANG_AZERI LANG_GREENLANDIC LANG_MAPUDUNGUN LANG_TAGALOG

LANG_AZERI_CYRILLIC LANG_GUARANI LANG_MARATHI LANG_TAJIK

LANG_AZERI_LATIN LANG_GUJARATI LANG_MOHAWK LANG_TAMAZIGHT

LANG_BASHKIR LANG_HAUSA LANG_MONGOLIAN LANG_TAMIL

LANG_BASQUE LANG_HAWAIIAN LANG_NEPALI LANG_TATAR

LANG_BELARUSIAN LANG_HEBREW LANG_NORWEGIAN LANG_TELUGU

LANG_BENGALI LANG_HINDI LANG_NORWEGIAN_BOKMAL LANG_THAI

LANG_BRETON LANG_HUNGARIAN LANG_NORWEGIAN_NYNORSK LANG_TIBETAN

LANG_BULGARIAN LANG_IBIBIO LANG_OCCITAN LANG_TIGRIGNA

LANG_BURMESE LANG_ICELANDIC LANG_ORIYA LANG_TSONGA

LANG_CAMBODIAN LANG_IGBO LANG_OROMO LANG_TSWANA

LANG_CATALAN LANG_INDONESIAN LANG_PAPIAMENTU LANG_TURKISH

LANG_CHEROKEE LANG_INUKTITUT LANG_PASHTO LANG_TURKMEN

LANG_CHINESE LANG_IRISH LANG_POLISH LANG_UIGHUR

LANG_CHINESE_SIMPLIFIED LANG_ITALIAN LANG_PORTUGUESE LANG_UKRAINIAN

LANG_CHINESE_TRADITIONAL LANG_JAPANESE LANG_PUNJABI LANG_URDU

LANG_CORSICAN LANG_KANNADA LANG_QUECHUA LANG_UZBEK

LANG_CROATIAN LANG_KANURI LANG_ROMANSH LANG_UZBEK_CYRILLIC

LANG_CZECH LANG_KASHMIRI LANG_ROMANIAN LANG_UZBEK_LATIN

LANG_DANISH LANG_KAZAK LANG_RUSSIAN LANG_VENDA

LANG_DARI LANG_KICHE LANG_SAMI LANG_VIETNAMESE

LANG_DIVEHI LANG_KINYARWANDA LANG_SANSKRIT LANG_WELSH

LANG_DUTCH LANG_KONKANI LANG_SERBIAN LANG_WOLOF

LANG_EDO LANG_KOREAN LANG_SERBIAN_CYRILLIC LANG_XHOSA

LANG_ENGLISH LANG_KYRGYZ LANG_SERBIAN_LATIN LANG_YAKUT

LANG_ESTONIAN LANG_LAOTHIAN LANG_SINDHI LANG_YI

LANG_FAEROESE LANG_LATIN LANG_SINHALESE LANG_YIDDISH



Supported LanguagesLANG_FARSI LANG_LATVIAN LANG_SLOVAK LANG_YORUBA

LANG_FINNISH LANG_LITHUANIAN LANG_SLOVENIAN LANG_ZULU

License Matrix

Each type of LAW PreDiscovery license is shown with its corresponding LAW PreDiscovery interface items.

For more information about each of the licenses and the Early Data Analyzer and TSI Scan licenses, see LicenseTypes.

Admin

ImportExport

CDPubFullText

Edit(QC

)

ED: E-

Print

ED: Load

er

ED:TIFF/PDF

Endorse

FullText

Indexing

Near-Duplicate&

EmailThrea

dAnaly

sis

OCRABBYY

OCRExperOpenRTK

OCR

ExperPDF

Print

Scan

FILE

OPEN CASE X X X X X X X X X X X X X

NEW CASE X

SAVE X X

SAVE AS X X

IMPORT X

DELIMITED TEXT X

LAW CASE X

LOAD FILE X

TAG LIST X

RAW IMAGES X

ELECTRONICDISCOVERY X

PRINT X X X X X X X X X X X X X

LAW PreDiscovery88


PRINT SETUP X X X X X X X X X X X X X

SEND X X X X X X X X X X X X X

IMAGE X X X X X X X X X X X X X

IMAGE + OCR X X X X X X X X X X X X X

OCR ONLY X X X X X X X X X X X X X

ADMINISTRATION

APPLY CASETEMPLATE X

CASE SUMMARY X

COMPACTDATABASE X

REORGANIZEDOCUMENTS X

SAVE CASETEMPLATE X

SCAN FORERRORS X

VALIDATERANGES X

SCAN

SELECT SCANNER X

SCANNERSETTINGS X

SCAN OPTIONS X

NEW DOCUMENT X

NEWATTACHMENT X

APPEND X

EDIT

INSERT X X

NEW PAGE(S) X X

EXISTING X X



PAGE(S)

E-DOCUMENT(S)*requires bothEdit and EDLoader X X

SCANNEDDOCUMENT X X

DELETE X X

REPLACE X X

AUTO NUMBER X X

ATTACHMENTS X X

MERGEDOCUMENTS X X

MOVEDOCUMENTS X X

RESET OCR FLAGS X X X

RESET FULLTEXTFLAGS X

SPLIT DOCUMENTS X X

VIEW PAGE INFO*requires both Editand Admin X* X*

PROPERTIES X X X X X X

FOLDER

NEW X X X

OPEN X X X X X X X X X X X X X

AUTO-CREATE X X X

AUTO-CREATE NFOLDERS X X X

COLLAPSE X X X X X X X X X X X X X

EXPAND X X X X X X X X X X X X X

DELETE X X X

EXTRACT AS X X X

LAW PreDiscovery90


SUBSET

GRID VIEW X X X X X X X X X X X X X

GRID VIEW(RECURSE) X X X X X X X X X X X X X

SUMMARIZEIMAGES X X X

RENAME X X X

MOVE X X X

PROPERTIES X X X X X X X X X X X X X

INDEX

DEFAULT FIELD X X X

INCREMENT MODE X X X

MODIFY FIELDS X

EDIT PAGE ID X X X

FIND PAGE ID X X X

VIEW

ZOOM IN X X X X X X X X X X X X X

ZOOM OUT X X X X X X X X X X X X X

ZOOM LOCK X X X X X X X X X X X X X

BEST FIT X X X X X X X X X X X X X

FIT TO WIDTH X X X X X X X X X X X X X

ONE PAGE X X X X X X X X X X X X X

THUMBNAILS X X X X X X X X X X X X X

PAGE ANDTHUMBNAILS X X X X X X X X X X X X X

INVERT X X X X X X X X X X X X X

PAN WINDOW X X X X X X X X X X X X X

SCALE TO GRAY X X X X X X X X X X X X X

PAGE

FIRST PAGE X X X X X X X X X X X X X



PREVIOUS PAGE X X X X X X X X X X X X X

NEXT PAGE X X X X X X X X X X X X X

LAST PAGE X X X X X X X X X X X X X

GOTO PAGE X X X X X X X X X X X X X

FLAG FOR OCR X X X

SHOW OCR FLAGS X X X

DESKEW X X

ENHANCE IMAGE X X

ROTATE PAGES X X X X X X X X X X X X X

PROPERTIES X X X X X X X X X X X X X

TOOLS

BATCH PROCESS X X X X X X X X X X X X X

BATESNUMBERING X X X X

IMAGE CLEANUP X X

ENDORSEIMAGE X

PRINT (IMAGES) X X

E-PRINT(NATIVES) X

SCAN FORSUSPECTFOOTERS X X X X X

LOG VIEWER X X X X X X X X X X X X

OCR X X X

TIFF/PDFCONVERSION X

UPDATE PAGEDATA X X X X X X X X X X X X X

DISTRIBUTEDBATCHPROCESSING X X X X X X X X X X X X X

LAW PreDiscovery92


EXPORT UTILITY X

DEDUPLICATIONUTILITY X X

DUPLICATE VIEWER X X X X X X X X X X X X X

NEAR-DUPLICATE& EMAIL THREADANALYSIS X

ANNOTATIONS X

BARCODES X

LAUNCH VIEWER X

OCR X X X

FULLTEXT INDEX X

RUN COMMAND X X X X X X X X X X X X X

DISPLAY ALLRECORDS X X X X X X X X X X X X X

SEARCH RECORDS X X X X X X X X X X X X X

OPTIONS X X X X X X X X X X X X X

HELP

HELP TOPICS X X X X X X X X X X X X X

USER GUIDE X X X X X X X X X X X X X

BUG REPORT X X X X X X X X X X X X X

CHECK FORUPDATE X X X X X X X X X X X X X

ABOUT LAW X X X X X X X X X X X X X

OPEN FILE

AUTOVUE SUITE

HEX EDITOR

INTERNETEXPLORER

MICROSOFTWORD

NOTEPAD



QUICK VIEW PLUS

CHOOSEPROGRAM

CHANGE SOURCEAPPLICATION

AUTOVUE SUITEREVIEW MODE

QUICK VIEW PLUSREVIEW MODE

REVIEW PARENTE-MAILS NATIVELY

LOTUS NOTESREVIEW MODE

Related Topics

License Types

Profile Manager

Undocked Keys

Field Descriptions

For a downloadable copy of Field Descriptions see LAW PreDiscovery Field Descriptions.

Field Name Field Description PossibleValues/Examples

E-Disc.Only

Scope FieldType

Z-Print FieldEquivalent

Table

_DocCat

Numeric valueindicating type ofdocument.Attributes may beeasily searchedusing the QueryBuilder in LAW.

ex: 521 DocNumeric

tblDoc

_DupID

Child duplicateshave ID value ofparent dup. Parentshave their own IDvalue (from LAW IDor external

0=Not dupor nottested

>0=Dup orparent

DocNumeric

tblDoc

http://help.lexisnexis.com/litigation/ac/law_docs/law6.5/LAW_PreDiscovery_Field_Descriptions.pdf

LAW PreDiscovery94



E-Disc.Only

Scope FieldType


Table

deduplicationdatabasetblDupLog.DupID),allowing grouping ofthe field to locatedup families.Records that arenot duplicates ornot tested will havea value of 0 in thisfield.

dup

_DupMethod

Indicates which key,or hash, was usedwhen testing thedup state of therecord.

1=MD5Hash

2=Sha1Hash

129=MD5Hash -Deduplicated usingInter-CaseDeduplication utility

130=Sha1Hash -Deduplicated usingInter-CaseDeduplication utility

DocTinyInt

tblDoc

_FTIndex

Displays status offull text indexingusing numericvalues.

0=No textisavailableforindexing

1=Document's text isready forindexing

2=Recordwasflagged forreindexing, but hasnot yetbeenreindexed

3=Document's texthas been

DocTinyInt

tblDoc




E-Disc.Only

Scope FieldType


Table

indexed.

_PS_ARCX

Numeric success/failure indicator tiedto archiveextraction process.

0=Notexecuted.

1=Successfullyexecuted.

2=Erroroccurred,seeErrorMsgfield.

DocTinyInt

tblDoc

_PS_ATTX

Numeric success/failure indicator tiedto attachmentextraction process(set for parent andchild).

0=Notexecuted.



DocTinyInt

tblDoc

_PS_DIGESTX

Numeric success/failure indicator tiedto process ofhashing native file.

0=Notexecuted.



DocTinyInt

tblDoc

_PS_EMBEDX

Numeric success/failure indicator tiedto extraction ofembedded imagesin e-mail.

0=Notexecuted.



DocTinyInt

tblDoc

_PS_MDX

Numeric success/failure indicator tiedto metadataextraction process.

0=Notexecuted.

1=Successfully

DocTinyInt

tblDoc

LAW PreDiscovery96



E-Disc.Only

Scope FieldType


Table

executed.


_PS_NATIVEX

Numeric success/failure indicator tiedto native fileextraction process.

0=Notexecuted.



DocTinyInt

tblDoc

_PS_OLEX

Numeric success/failure indicator tiedto OLE extractionprocess (set forparent and child).

0=Notexecuted.



DocTinyInt

tblDoc

ApplicationName

Application Namefield value pulledfrom metadata ofthe native file.

ex:MicrosoftOfficeWord

Doc Text tblDoc

Attach

Populates parentrecords with originalfilenames of allattached records,separated by

semi-colons.

ex:Attach1.doc;Attach2.xls

Doc Memo Attach tblDoc

AttachLvl

Numeric valuesindicate if a recordis a parent,attachment, orneither.

0=Indicates parentrecord,recordthat doesnot haveattachments, orrecordthat is notan

DocNumeric

Similar toAttachNo, inthat parentrecords orrecordswithoutattachments will be 0andattachmentrecords will

tblDoc




E-Disc.Only

Scope FieldType


Table

attachment.

1=Indicates record isanattachment.

be greaterthan 0.However,5.0 doesnot usevaluesgreaterthan 1,while Z-Print'sAttachNovalue wouldincrementup by onefor eachattachmentwith thesameparent.

Attachmt

Populates parentrecords withBegDoc# of eachattached record,separated by semi-colons.

ex:ABC0002;ABC0003

Doc Text tblAttach

AttachPID

Populates parentrecords andattachments withthe ID number ofthe parent record.

0=Indicates record isnot aparentand not anattachment.

>0=Anyvaluegreaterthan zerowillindicatethat arecord iseither aparent oranattachment. Thevalue isequal tothe IDvalue ofthe parentrecord, soparentsand their

DocNumeric

Similar toAttachID, inthatparents andtheirattachments will havethe same IDnumber.

tblDoc

LAW PreDiscovery98



E-Disc.Only

Scope FieldType


Table

attachments willhave thesamevalue.

AttRange

Stores BegDoc# ofparent record andEndDoc# of lastattachment record,separated by ahyphen. Populatedfor all records in thefamily (parent andattachment(s)).

ex:ABC0001 -ABC0008

Doc Text tblAttach

Author

Author field valuepulled frommetadata of thenative file.

Doc Text Author tblDoc

BatchStation

Name of thecomputer that ran abatch process on adocument.

ex:Laptop01

Doc Text tblDoc

BatesRng

(Exports only - doesnot exist in LAWcase database)Lists the PageID ofthe first page of adocument and thePageID of the lastpage of adocument,separated by ahyphen.

ex:ABC0001 -ABC0005

Doc N/A N/A

BCC

Recipient(s) of"Blind CarbonCopies" of the e-mail message.

Doc Memo BCC tblDoc

BegAttach

Displays BegDoc#of parent record.When exported, thevalues will matchthe field used asthe Image Tag.

ex:ABC0001

Doc Text

Similar toBegAttach,but usesBegDoc#instead ofDocID.

tblAttach

BegDoc#Displays page ID offirst page in adocument.

ex:ABC0001

Doc Text tblDoc

BookmarkName

Names ofbookmarks in anAdobe Acrobat PDF

Y=Yes

N=NoDoc Text tblDoc




E-Disc.Only

Scope FieldType


Table

file.

Categories

Category field valuepulled frommetadata of thenative file.

ex:Software

Doc Memo Categories tblDoc

CCRecipient(s) of"Carbon Copies) ofthe e-mail message.

Doc Memo CC tblDoc

Comments

Comments fieldvalue pulled fromthe metadata of thenative file.

Doc Memo Comments tblDoc

Conversation Normalized subjectof e-mails.

Doc Memo Conversation

tblDoc

ConversationIndex

E-mail threadidentification.

ex:01C72AC4CB0FC3953C5FA8E149389B522EFF595EF9FB

Doc MemoConversationIndex

tblDoc

CreatedStores date andtime the record wascreated in LAW.

Doc Date tblDoc

Custodian

Lookup field,displays textualvalue of custodianassigned by user inEDLoader.

DocLookup

CustodiantblCustodians.Name

DateAccessed

Stores the lastaccessed date fromthe properties ofthe file. Note: Manyfunctions will causethis value to beupdated byWindows (e.g.,viewing fileproperties,dragging anddropping) andtherefore this datewill often reflect thecurrent date. Toavoid this situation,run theDisableLastAccessUpdate.reg filelocated in the

Doc Date tblDoc

LAW PreDiscovery100



E-Disc.Only

Scope FieldType


Table

\LAW50 folder(same folder aslaw50.exe) prior tohandling the data(requires rebootafter running). Thiswill preventupdates to thisvalue (applies toLAW TimeAccessedfield also) byWindows. To re-enable the registrysetting, run theEnableLastAccessUpdate.reg filelocated in the samefolder.

DateAppEndAppointment enddate for calendaritems.

Doc Date tblDoc

DateAppStartAppointment startdate for calendaritems.

Doc Date tblDoc

DateCreated Creation date of thenative file.

Doc Date DateCreated

tblDoc

DateLastMod Date the native filewas last modified.

Doc Date DateLastMod

tblDoc

DateLastPrntDate the native filewas last printed(Office documents).

Doc DateDateLastPrnt

tblDoc

DateRcvd Received date of ane-mail message.

Doc Date DateRcvd tblDoc

DateSent Sent date of an e-mail message.

Doc Date DateSent tblDoc

DelivReceiptDelivery receiptrequest notification.

Y=Yes(deliveryreceiptrequested)

N=No

<null>=Attachmentsand e-docs willhave nullvalue.

Doc Text DelivReceipt tblDoc




E-Disc.Only

Scope FieldType


Table

DocExt

File extension ofnative file. Mayshow originalextension orsuggestedextension,depending on stateof "auto-assignext." option inEDLoader.

ex: DOC Doc Text DocExt tblDoc

DocID

Document ID valueassigned during EDimport. Startingnumber specified byuser in DocID Seedfield in Sources tabin EDLoader.

ex:ID00001

Doc Text DocID tblDoc

DocOrder

Numeric valueindicating order ofdocuments in eachfolder.

ex: 3 Doc Text tblDoc

DupCustNames

Names of thecustodianscontaining duplicateversions of theoriginal record.Populated forparent/originalrecords only(DupStatus=P) afterrunning Tools >Apply DuplicateRelationships.

FirstCustodianName;SecondCustodianName

Doc Memo tblDoc

DupCustPaths

Source path to eachduplicate version ofthe original record.Populated forparent/originalrecords only(DupStatus=P) afterrunning Tools >Apply DuplicateRelationships.

D:\Docs\;E:\Docs2

Doc Memo tblDoc

DupParentName

Custodian name ofthe original record.Populated forduplicate recordsonly (DupStatus=Gor C) after runningTools > ApplyDuplicate

ParentCustodianName

Doc Memo tblDoc

LAW PreDiscovery102



E-Disc.Only

Scope FieldType


Table

Relationships.

DupParentPath

Name of thecustodiancontaining theoriginal record.Populated forduplicate recordsonly (DupStatus=Gor C) after runningTools > ApplyDuplicateRelationships.

C:\Docs\ Doc Memo tblDoc

DupStatus

Displays dedupstatus with singlecharacter value(see dedupdocumentation formore info).

N=Not aduplicate

G=Global-levelduplicate

C=Custodian-levelduplicate

P=Parentduplicate

Doc Text

Z-Printpopulatesthe Statusfield with a"D" value ifrecord is adup. 5.0usesDupStatusto indicatedup statusin a moreadvancedmanner. "G"or "C" willindicate therecord is adup in LAW.

tblDoc

EdaID

Populated forparent itemsexported from EarlyData Analyzer.Pulled fromInventoryItems.IDin the EDA casedatabase.

0=Indicates non-Early DataAnalyzerrecord orrecordfrom EarlyDataAnalyzerthat wasnot aparent.

>0=Parentrecordfrom EarlyDataAnalyzercase.

DocNumeric

tblDoc

EDFolderFull path to sourcefiles (if e-docs or

ex(1):Personal

DocLookup

FoldertblFolders.Name




E-Disc.Only

Scope FieldType


Table

loose e-mail) orfolder pathcontained with amail store (if NSF orPST).

Folders\Inbox

ex(2): C:\EDOCS

EDPages

Stores the numberof printed pagesfollowing the e-Printbatch process.

ex: 75 DocNumeric

Pages tblDoc

EDSession

Stores sessionname, as assignedby user inEDLoader's SessionLabel field.

ex:SessionCreatedOn1/4/200712:48:23PM

DocBLookup

tblSessions.Title

EDSource

Fully qualifiedoriginal path to thesource folder, files,and/or mail stores.

ex(1): C:\Mail\Outlook.pst

ex(2): C:\Edocs\Spreadsheets

DocLookup

Folder (e-docs/loosee-mail);MailStore(store-based e-mail)

tblEDSources.SourcePath

EMail_SubjectSubject of the e-mail message.

ex: FW:LAWPreDiscovery

Doc MemoEmail_Subject

tblDoc

EndAttach

EndDoc# of lastattached documentin family. Whenexported, thevalues will matchthe field used asthe Image Tag.

ex:ABC0003

Doc Text

Similar toEndAttach,but usesEndDoc#instead ofDocID.

tblAttach

EndDoc#Page ID of lastpage in adocument.

ex:ABC0003

Doc Text tblDoc

EntryIDUnique identifier ofe-mails in mailstores.

ex:1322C3C03649D4418625711400748A13

Doc Memo EntryID tblDoc

EP*

Any field precededby EP indicates afield that containsextended propertyor EP metadata. EP

ex: if aWorddocumentcontains avalue of

Doc Text Extended

LAW PreDiscovery104



E-Disc.Only

Scope FieldType


Table

metadata can comefrom user definedfields added tooriginal PDFs, Officefiles, and EXIFmetadata for TIFFand JPEG imagefiles. Any custommetadata found isplaced into a specialfield designated asa an extendedproperty.

Jones inits Typistfield, uponimport ofthe file,LAWcreate anew fieldfor thecasecalled EPTypistandpopulatethe fieldfor thatdocumentwith thevalue Jones.

ErrorMsg

Displays error orwarning messages,if any occurredduring ED import orTIFF/PDFconversion.

Doc Memo ErrorMsg tblDoc

ET_Conversants

The names of allsenders andrecipientsmentioned in theFrom, To, CC, andBCC fields found inthe entire email,based on readingthe headers of anyquoted messagesas well as theprimary messageitself.

EnronAnnouncements,[email protected]

Doc Memo tblDoc

ET_Inclusive

Flags a minimal setof documents whichcan be viewed inorder to read theemail messagethread's entireconversation. In thesimplest case thiswill simply be thelast message in thethread, since it willquote all thepreviousmessages.

N=No,Y=Yes

Doc Text tblDoc




E-Disc.Only

Scope FieldType


Table

Note thatinclusiveness iscalculated based onmessage bodies,and does notconsider metadata,such as an email'ssubject.

The ET_Inclusivefield only flags emailmessages. It doesnot flagattachments.

ET_InclusiveReason

If ET_Inclusive fieldis set to Y,ET_InclusiveReasonfield indicates whythe email isinclusive.

If the emailmessage containsmessage contentthat is not copied inany of itssubsequent repliesor forwards,Message isdisplayed.

If the emailmessage hasattachments thatare not included inany of itssubsequent repliesor forwards,Attachment isdisplayed.

If the emailmessage has bothnew messagecontent and newattachments notincluded in any ofits subsequentreplies or forwards,Message,Attachment isdisplayed.

If ET_Inclusive fieldis set to N,

Message,Attachment

Doc Text tblDoc

LAW PreDiscovery106



E-Disc.Only

Scope FieldType


Table

ET_InclusiveReasonfield is blank.

ET_IsMessage

Indicates whetherthe document wasrecognized as anemail message ('Y'),or some other kindof document ('N').

N=No,Y=Yes

Doc Text tblDoc

ET_MessageId

A unique ID that isassigned to eachmessage. If severaldocuments havethe same MessageID, it is becausethey wererecognized asseparate copies ofthe same emailmessage.

00001004 Doc Text tblDoc

ET_MetaUpdate

Indicates whetherthe the emailmetadata waspopulated fromanalyzed text bythe Near-Duplicate& Email ThreadAnalysis utility.

N=No,Y=Yes

Doc Text tblDoc

ET_ParentId

The immediateparent of thecurrent email in thethread. For the firstmessage, this willbe blank. For eachsubsequent one, itwill be the DocID ofthe email which itreplies to or is aforward of.


ET_ThreadIdA unique IDassigned to eachmessage thread.


ET_ThreadIndex

Is composed of abase ID, plus aunique number foreach messagewithin the thread,and if there areattachments, theletter A plus theunique number for

1701.1

1701.1.A1

1701.1.A2

Doc Text tblDoc




E-Disc.Only

Scope FieldType


Table

the attachmentwithin the thread.For example, A1,A2, A3.

Uses the format:[base ID].[uniquenumber formessage].A[uniqueattachmentnumber]

The base ID is thesame as the threadID without theleading zeros. Thethread index for theroot message of thethread will just bethis.

ET_ThreadModified

Equal to thetimestamp of themost recent“process data”operation thatmade any additionsto the thread.

9/27/20131:06:59PM

Doc Date tblDoc

ET_ThreadSize

The total number ofunique messages(not documents --see 'IsMessage'above) in thethread.

1, 3, 10 DocNumeric

tblDoc

ET_ThreadSort

A sort order whichfollows the chain ofconversation, fromfirst message tomost recent. If aconversation splitsinto multiplebranches,ET_ThreadSort willkeep each of thebranches together.

640, 641,642

DocNumeric

tblDoc

FileAccuracy

Accuracy ratinggenerated by fileengine during filevalidation.

0=Unidentified

1=Low

2=Medium

3=High

DocTinyInt

tblDoc

LAW PreDiscovery108



E-Disc.Only

Scope FieldType


Table

FileDescription

Description ofnative file type, aslisted in file typedatabase.

ex: MSWord forWindowsDocument

Doc TextFileDescription

tblDoc

Filename

Original filename ofnative file. Containssubject of e-mailmessage for e-mailrecords.

ex(1):Estimates.xls

ex(2): FW:MondayMeeting

Doc Memo Filename tblDoc

Filesize Size of native file, inbytes.

ex: 27739 Doc BigInt Filesize tblDoc

FileType

ID numberassociated with filetype, as listed in filetype database.

ex: 229 DocNumeric

FileType tblDoc

FolderRng

(Exports only - doesnot exist in LAWcase database)Lists the PageID ofthe first page of thefirst document in afolder and the lastPageID of the lastdocument in afolder, separated bya hyphen.

ex.ABC0001 -ABC0011

Doc N/A N/A

Footer

Displays size offooter value ifimage wasendorsed in LAW.

0=Unendorsed

25=Contains 1/4 in.footer.

50=Contains 1/2 in.footer.

and so on.

PageNumeric

tblPage

From Author of the e-mailmessage.

Doc Text From tblDoc

HasAnnotations

Annotations areapplied todocument.

Y=Yes

N=NoDoc Text tblDoc

HasBookmarks

Adobe Acrobat PDFfile containsbookmarks.

Y=Yes

N=NoDoc Text tblDoc

HasComments Microsoft Word, Y=Yes Doc Text Extended




E-Disc.Only

Scope FieldType


Table

Excel or PowerPointdocument containscomments.

N=No

HasExtProps

Microsoft Word orExcel documentcontains extendedproperties.

Y=Yes

N=NoDoc Text Extended

HasHiddenRowCol

Microsoft Exceldocument containsone or more hiddenrows or columns.

Y=Yes


HasHiddenSheet

Microsoft Exceldocument containsone or more hiddenworksheets.

Y=Yes


HasTrackChanges

Microsoft Word orExcel documentcontains trackedchanges.

Y=Yes


Header

Displays size ofheader value ifimage wasendorsed in LAW.

0=Unendorsed

25=Contains 1/4 in.header.

50=Contains 1/2 in.header.

and so on.

PageNumeric

tblPage

HeadersContents of theheader in an e-mailmessage.

Doc Memo Headers tblDoc

HiddenSlidesPowerPointdocument containshidden slides.

Y=Yes


HiddenText

True if documentcontains hiddentext, otherwiseFalse.

DocBoolean

tblDoc

ID

Unique ID valueassigned to allrecords in LAW,starting with 1.

ex: 1 DocNumeric

tblDoc

ImageExtFile extension ofimage records inLAW (applies to

ex: TIF Doc Text tblDoc

LAW PreDiscovery110



E-Disc.Only

Scope FieldType


Table

docs imported asraw images or viaload file, scannedimages, and filesconverted to TIFF orPDF in LAW).

ImportanceImportance fieldextracted from ane-mail message.

ex: High Doc Text Importance tblDoc

ImportStation

Name of thecomputer thatimported adocument.

ex:Laptop01

Doc Text tblDoc

InReplyToID IntMsgID of the e-mail replied to.

Doc Memo InReplyToID tblDoc

IntMsgID

Internet MessageID assigned to ane-mail message bythe outgoing mailserver.

Doc Memo IntMsgID tblDoc

KeywordsKeywords extractedfrom the metadataof the native file.

ex: LAW Doc Memo Keywords tblDoc

LanguageLists the first 5languages found inthe document.

ex:English;Japanese;Spanish

Doc

varchar(SQL)ortext(Access)

tblDoc

LastAuthor

Last Saved By fieldvalue pulled frommetadata of thenative file.

ex: Joe L.Author

Doc Text tblDoc

MailStore

(Exports only - doesnot exist in LAWcase database)Fully qualifiedoriginal path to mailstore (includingfilename).

ex: D:\MailStores\Sample.pst

Doc N/A MailStore N/A

MD5Hash

Unique identifier,similar to a"fingerprint",extracted from allfiles imported viaEDLoader. Uses128-bit encryption.

ex:D564668821C34200FF3E32C9BFDCCC80

Doc Text MD5Hash tblDoc




E-Disc.Only

Scope FieldType


Table

May be used fordeduping purposes.

MsgClass

Outlook boundproperty indicatingtype of entry instore.

ex:IPM.Note

Doc Text

MessageClass (ZPdatabaseonly, notdisplayed inCSV)

tblDoc

NativeFile

Not currentlyutilized in LAWPreDiscovery for EDcases.

N/A Doc Memo tblDoc

ND_ClusterID

A unique ID for eachnear-duplicatedocument cluster.Documents in acluster may besimilar, but not asclosely related asdocuments in thenear-duplicatefamily, and somedocuments in acluster may not besimilar, but areconnected by achain ofrelationshipsbetweendocuments.

ex:00000017

Doc Text tblDoc

ND_ContentHash

Identifies exactduplicates. Ifdocuments havethe same hashvalue in theND_ContentHashfield, they share theexact same text,even if thedocuments havedifferent metadataor file formats.

ex:

230554D8C9CB9A4BCDD6E2B49244D91BBFB6A8DC

Doc Text tblDoc

ND_FamilyID

A unique ID for eachnear-duplicatedocument family. Alldocuments withinthe same near-duplicate family willhave the same ID inthe ND_FamilyIDfield.

ex:


LAW PreDiscovery112



E-Disc.Only

Scope FieldType


Table

The ND_FamilyIDvalue matches themaster document'sID value, but ispadded to eightdigits.

For example, if themaster ID = 1. ThecorrespondingND_FamilyID value= 00000001.

ND_IsMaster

Indicates whetherthe document is themaster document.

Within a family, themaster document isthe one with thegreatest overallsimilarity to all theother documents inthe family. It has tobe a near-duplicateof every otherdocument in thefamily.

Note: Documentsthat are not part ofa near-duplicatefamily will also havea Y (Yes) value inthe field.

Y=Yes

N=NoDoc Text tblDoc

ND_ResultSet

Used for internaltracking purposesby the near-duplicateprocessing utility.Indicates the near-duplicate indexrevision that theND_* fields for thecurrent recordrepresent.


ND_Similarity

Displays thepercentage ofsimilarity betweenthe document andits masterdocument.

Within a family, themaster document is

ex: 85,100

DocNumeric

tblDoc




E-Disc.Only

Scope FieldType


Table

the one with thegreatest overallsimilarity to all theother documents inthe family. It has tobe a near-duplicateof every otherdocument in thefamily.

ND_Sort

A document’s sortorder ID. The Near-Duplicate Analysisutility sortsdocuments basedon documentsimilarity. The closerdocuments are toone another, thecloser their sortorder ID will be toeach other.

ex: 2284,2285,2330,2286

DocNumeric

tblDoc

NumAttach

(Exports only - doesnot exist in LAWcase database)Total number ofrecords attached tothe document.Value will always be0 (zero) for actualattachment records.

ex: 2 Doc N/A NumAttach N/A

OcrAccuracy

The percentage ofaccuracy for thefile's document-levelOCR. This field willbe blank for adocument when theOCR wastransferred fromEarly Data Analyzer.

ex: 10, 99,100

DocNumeric

tblDoc

OcrFlagPage-level OCRstatus of each pagein a document.

Y=Pageflagged forOCR

N=Pagenotflagged

C=Page iscomplete

E=ErroroccurredOCRing

Page Text tblPage

LAW PreDiscovery114



E-Disc.Only

Scope FieldType


Table

page

OcrStatusDoc-level OCRstatus of adocument.

Y=One ormorepagesflagged forOCR

N=Nopagesflagged

C=OCRcompleteondocument

I=OCRwascancelled

E=ErroroccurredOCRingdocument

P=Processing (specialflag usedby LAWduringOCR)

Doc Text tblDoc

Organization

Company fieldextracted frommetadata of nativefile.

ex:LexisNexis

Doc MemoOrganization

tblDoc

OrigExt

Original fileextension of nativefile, if "auto-assignext." option wasenabled and filewas suspect.

ex: PDF Doc Text tblDoc

PagePage number ofeach page in adocument.

PageNumeric

tblPage

Page ID

ID number assignedby user to pages ofdocuments (imagesonly).

ex:ABC0001

Page Text tblPage

PageColor

Stores the colorinformation at apage level forscanned and

Black &White (1)

Color (2)

PageLookup

tblPage.ColorID




E-Disc.Only

Scope FieldType


Table

imported images, aswell as imagescreated during aTIFF conversion.See the followingHelp topic for moreinformation:Administration->Tracking PageSource, Size, andColor.

Grayscale(3)

PageFilename

Path to TIFF imageor PDF file that wasa result of a TIFF/PDF conversion inLAW. Path isrelative to$ImageArchivefolder, located incase folder.

ex: 00\00\00\01.tif

Page Text

Similar toOutputFile,in that thisfield showsthe locationof theoutput TIFFimage orPDF fileafter TIFF/PDFconversion.

tblPage

PageHeight

Stores the height ofan image at a pagelevel for scannedand importedimages, as well asimages createdduring a TIFFconversion. See thefollowing Help topicfor moreinformation:Administration->Tracking PageSource, Size, andColor.

ex: 11.50 PageNumeric

tblPage

PageSize

Stores the pagesize of an image ata page level forscanned andimported images, aswell as imagescreated during aTIFF conversion.See the followingHelp topic for moreinformation:Administration->Tracking PageSource, Size, andColor.

Letter (1)

Legal (2)

DoubleLetter (3)

Oversized(4)

PageLookup

tblPage.PageSizeID

LAW PreDiscovery116



E-Disc.Only

Scope FieldType


Table

PageSource

Stores the source ofan image at a pagelevel for scannedand importedimages, as well asimages createdduring a TIFF/PDFconversion. See thefollowing Help topicfor moreinformation:Administration->Tracking PageSource, Size, andColor.

Feeder (1)

Flatbed (2)

Imported(3)

TIFF/PDFConversion (4)

ManualTIFF/PDFConversion (5)

PageLookup

tblPage.SourceID

PageWidth

Stores the width ofan image at a pagelevel for scannedand importedimages, as well asimages createdduring a TIFF/PDFconversion. See thefollowing Help topicfor moreinformation:Administration->Tracking PageSource, Size, andColor.

ex: 8.5 PageNumeric

tblPage

ParentID

(Exports only - doesnot exist in LAWcase database)Populated only forattachments, thisfield will display theImage Tag fieldvalue of theattachment record'sparent. Forexample, if theImage Tag is set to"DocID", the parentrecord's DocIDvalue will be listedas the ParentID forthe attachments.

ex:ID00001

Doc N/A N/A

Path

Folder path for LAWrecords, relative toroot case folder, asshown in the treeview in LAW's maininterface. Physical

001Source\001Box

Doc Text tblDoc




E-Disc.Only

Scope FieldType


Table

files may not existin this path inWindows,depending on howthe files wereimported orscanned into LAW.For moreinformation onstorage locations,please see the Helptopics underAcquiringDocuments.

PgCountNumber of pages ina document (imagerecords).

ex: 250 DocNumeric

Pages tblDoc

PrevErrMsg

If a record issuccessfullyconverted to TIFF orPDF, the ErrorMsgfield is cleared andany existing valuein that field isprepended to thePrevErrMsg field forreference.

Doc Memo

PrintJobName

Displays the nameof the job in theprint spooler forTIFF/PDFconversions. Thisfield allowsadditional errors tobe logged if multiplejobs are detected inthe spooler for aconversion or thename of the job inthe spooler doesnot match theexpected job namefor a document.*NOTE: Specialattention must begiven to any errorsprefixed with"Multiple jobsdetected" or "Printjob name does notmatch expectedformat" to inspectthe captured image

0DB7AC7F42A84562A2749BF95483F43B_5_05.ntv.xls

Doc Text tblDoc

LAW PreDiscovery118



E-Disc.Only

Scope FieldType


Table

against the originalfor correctness.

ReadReceipt

Read receiptrequest notificationfor e-mailmessages.

Y=Yes(readreceiptrequested)

N=No

<null>=Attachmentsand e-docs willhave nullvalue.

Doc TextReadReceipt

tblDoc

RecordType

(Exports only - doesnot exist in LAWcase database)Lists the recordtype for each entryin the load file.

IMAGE;LOOSE E-MAIL;E-MAIL;E-DOC;IMAGEATTACHMENT;LOOSEE-MAILATTACHMENT;E-MAILATTACHMENT;E-DOCATTACHMENT;LOOSEE-MAILATTACHMENT (E-MAIL);E-MAILATTACHMENT (E-MAIL);

E-DOCATTACHMENT (E-MAIL)

Doc N/A RecordType N/A

Revision

Revision numberextracted frommetadata of nativefile.


SensitivitySensitivity fieldextracted from e-mail messages.

ex: Private Doc Text Sensitivity tblDoc

Sha1Hash Unique identifier, ex: Doc Text tblDoc




E-Disc.Only

Scope FieldType


Table

similar to a"fingerprint",extracted from allfiles imported viaEDLoader. Uses160-bit encryption.May be used fordeduping purposes.

B68F4F57223CA7DA3584BAD7ECF111B8044F8631

SourceApp

Source applicationassigned to thenative file, asspecified in the filetype database. Thisapplication will beused to print the fileduring the e-Printand TIFF/PDFConversion batchprocesses.

<NoSourceSpecified>

AdobeAcrobat

AutoVueSuite

Binary/HexPrinter

CorelWordPerfect

eDrawingsViewer

ImagePrinter

InternetExplorer

MicrosoftExcel

MicrosoftOutlook

MicrosoftPowerPoint

MicrosoftProject

MicrosoftVisio

MicrosoftWord

Quick ViewPlus

ShellPrinter

Doc List SourceApp tblDoc

LAW PreDiscovery120



E-Disc.Only

Scope FieldType


Table

SnapshotViewer

Text/RTFPrinter

VoloViewExpress

SourceFile

Fully qualifiedoriginal path(including filename)to original loose e-mail message. Fieldis blank for all othertypes.

ex: D:\001\test.msg

Doc Memo tblDoc

SpeakerNotesPowerPointdocument containsspeaker notes.

Y=Yes


Subject

Subject field valueextracted frommetadata of nativefile.

ex: LAW Doc Text Subject tblDoc

SuspectExt

Flagged with "Y"value for filesdeemed suspectduring thevalidation process,meaning theoriginal fileextension did notrepresent the truefile type.

Y=Consideredsuspect

N=Not asuspectfile

Doc Text tblDoc

SuspectOLE

Documentsuspected tocontain embeddedfiles.

Y=Containsembeddedfiles.

N=Doesnotcontainembeddedfiles.

Doc Text tblDoc

Template

Template field valuepulled frommetadata of thenative file.

ex:Normal.dot

Doc Text tblDoc

TextPStatus

Status of textextraction thatoccurs as files areconverted to TIFFimages or PDF files

C=TextwasextractedduringTIFF/PDF

Doc Text tblDoc




E-Disc.Only

Scope FieldType


Table

(TIFF/PDFConversion batchprocess). "Save textwith images" mustbe enabled in orderfor the TIFF/PDFengine to attempttext extraction.

conversion.

N=No textwasextractedduringTIFF/PDFconversion.

TextXStatus

Status of nativetext extraction thatoccurs when a file isimported viaEDLoader.

C=Textextractedsuccessfully fromnative file.

N=No textwasextracted.

E=Erroroccurredextractingtext, seeErrorMsgfield.

Doc Text tblDoc

ThreadID

Tracks e-mailthreads importedvia ED Loader fromOutlook stores andfrom loose MSGfiles. Attachmentsto e-mails receivinga value for theThreadID arepopulated with theThreadID of thecorrespondingparent e-mail.

Populatedwith theleftmost22charactersofConversationIndexfield.

Doc Text tblDoc

TiffStatus

Status of TIFF/PDFconversion.

Note: Values in thisfield will not controlwhich files areconverted to TIFF orPDF files, and whichare not. Any filesselected for TIFF orPDF conversion inthe Batch Processform will beconverted to TIFF orPDF or given a

Y=Flaggedforconvertingto TIFF orPDF (anyfiles with avalidsourceappassignedwill beflaggedafter EDimport)

Doc Text

Similar toStatus.Values areslightlydifferentthan Z-Print. SeePossibleValues.

tblDoc

LAW PreDiscovery122



E-Disc.Only

Scope FieldType


Table

placeholder (ifenabled) regardlessof this field.

C=File wasconvertedto TIFF orPDF file

E=Erroroccurredand wasloggedduringTIFF or PDFconversion(seeErrorMsgfield)

W=Warning wasloggedduringTIFF or PDFconversion

N=File notflagged forconvertingto TIFF orPDF (novalidsourceappassignedduring EDimport,<NoSourceSpecified>value isassigned)

P=Placeholderprinted forthedocument

TimeAccessed

Stores the lastaccessed time fromthe properties ofthe file. Note: Manyfunctions will causethis value to beupdated byWindows (e.g.,

Doc Text tblDoc




E-Disc.Only

Scope FieldType


Table

viewing fileproperties,dragging anddropping) andtherefore this timewill often beinaccurate.

To avoid thissituation,prior tohandling the data,run theDisableLastAccessUpdate.reg filelocated in the\LAW50 folder(same folder aslaw50.exe) (requires rebootafter running). Thiswill preventupdates to thisvalue (applies toLAW DateAccessedfield also) byWindows while thefile is being handledthroughout theproject. To re-enable the registrysetting, run theEnableLastAccessUpdate.reg filelocated in the samefolder.

TimeAppEndAppointment endtime for calendaritems.

Doc Text tblDoc

TimeAppStartAppointment starttime for calendaritems.

Doc Text tblDoc

TimeCreated Creation time of thenative file.

Doc Text TimeCreated

tblDoc

TimeLastMod Time native file waslast modified.

Doc Text TimeLastMod

tblDoc

TimeLastPrntTime native file waslast printed (Officedocuments).

Doc TextTimeLastPrnt

tblDoc

TimeRcvdTime the e-mailmessage wasreceived.

Doc Text TimeRcvd tblDoc

LAW PreDiscovery124



E-Disc.Only

Scope FieldType


Table

TimeSent Time the e-mailmessage was sent.

Doc Text TimeSent tblDoc

TimeZoneProcTime zone whereitem was firstprocessed.

Doc Text tblDoc

Title

Title field valueextracted from themetadata of thenative file.

Doc Text Title tblDoc

To Main recipient(s) ofthe e-mail message.

Doc Memo To tblDoc

UnreadE-mail has not beenread.

Y=Yes

N=NoDoc Text Unread tblDoc

UserId Not currentlyutilized in LAW.

N/A Doc Numeric

tblDoc

Volume

Stores volume ID,as listed intblVolume in LAWcase database.

DocNumeric

tblVolume

Related Topics

User Guides

Unicode Support

The general requirements and supported functionality for Unicode are listed as follows:

LAW PreDiscovery™ versions 5.2 and higher support the Unicode standard.

Proper language packs must be installed for the associated Unicode characters to rendercorrectly.

To print Unicode text files, use either Microsoft Word or the Shell Printer as the sourceapplication. The Text/RTF Printer can print RTF with Unicode, however it cannot print Unicode



text files.

If using the Shell Printer, you must ensure that the application registered on the system fortext files supports shell prints For example, Notepad supports shell prints.

The ExperVision and TextBridge OCR engines do not currently support Unicode.

Supported languages for OCR can be found in the Language drop-down list located in theOCR tab in Tools -> Options.

Printed and extracted text will contain Unicode data if it exists in the original file and can bedisplayed, provided the proper language pack(s) are installed on the system.

To view Unicode in a grid

In a grid view, rest the mouse pointer over a cell that contains Unicode characters.

The text appears in a pop-up text box.

Unicode in names for files, cases, and fields

Files with Unicode file names or residing in a Unicode path may be imported using the ED

Loader. These Unicode paths can be retained and displayed in the main folder view andany other applicable folder view in the application. Unicode existing in the metadata willbe retained and can be displayed in the Index display.

Unicode is not supported in case names. While the rest of the case path can contain

Unicode, it is recommended the case paths do not contain Unicode characters to avoidpotential issues with 3rd party applications.

Index field names cannot contain Unicode characters.

Exporting Unicode data

Unicode data can be sent to the export file when exporting field data from a grid.

In the Save Results As dialog box, in the Save as type list, select Unicode Text (Tabdelimited)(*.csv).

Exporting Unicode

Export Formats

Unicode data is supported in the Export Utility in the following export formats:

CaseLogistix - Unicode is automatically included if present in the exported data.

Delimited Text - Unicode data will be included only if the Allow Unicode data (UCS-2format) option is enabled in this format's configuration settings.

EDRM XML 1.0 - Unicode is automatically included if present in the exported data.

EDRM XML 2.0 - Unicode is automatically included if present in the exported data.

Concordance Direct DCB - Unicode data will be included only if LexisNexis Concordance10 or above is installed on the computer and Create Concordance 10.0 database(supports Unicode is enabled in the configuration settings for that format.

LAW PreDiscovery126


Concordance - Unicode data will be included only if Allow Unicode data (UCS-2 format)is enabled in this format's configuration settings.

Export Utility Restrictions

When using the Export Utility, if you export to a format that does not support Unicode:

Do not use the Mirror Original folder naming scheme if Unicode folders exist in thecase.

Ensure the export path does not contain Unicode. Unicode paths and filenames may

prevent the target applications from opening associated images, text, or native files.

Keyboard Shortcuts

If the keyboard shortcuts are not functioning, and a grid display is currently active, pleaseensure that Review Mode is disabled in the grid. See Tagging Records for more information.

For a downloadable copy of the keyboard shortcuts see LAW PreDiscovery Keyboard Reference.

Function keys

Key Function

F1 Help

F2 Edit Search Entry

F3 Scan New Batch

F4 Deskew Document

F5 Append Document

F6 Replace Pages

F7 Page Size - Letter (8.5 x 11")

F8 Page Size - Legal (8.5 x 14")

F9 Page Size - Double Letter (11 x 17")

F10 Scan Mode - Simplex

F11 Scan Mode - Duplex **

F12 Scan Mode - Flatbed **

http://help.lexisnexis.com/litigation/ac/law_docs/law6.1/LAW_Prediscovery_Keyboard_Reference.pdf



** Availability of these modes depends on whether the scanner support for thesecapabilities.

Control keys

Key Combination Action

ALT+UP ARROW Increase scan brightness (32pts)

ALT+DOWN ARROW Decrease scan brightness (32pts)

CTRL+A Select All Pages (if thumbnails display has focus)

CTRL+A Select All Documents (if document list has focus)

CTRL+A Show All Fields (if Search Results window has focus)

CTRL+X Hide All Fields (if Search Results window has focus)

CTRL+E Edit Page ID

CTRL+F Find Page ID

CTRL+G Go To Page

CTRL+L Rotate Left (current or selected pages)

CTRL+M Merge Documents

CTRL+O OCR Document

CTRL+P Print

CTRL+R Rotate Right (current or selected pages)

CTRL+S Save Image (saves image with current page orientation)

CTRL+U Split Document

CTRL+Z Zoom Lock

CTRL+1 Black and White Scanning

CTRL+2 8-bit Grayscale Scanning

CTRL+3 24-bit Color Scanning

CTRL+F3 Scan New Attachment

CTRL+F4 Enhance Image menu

CTRL+F6 Replace Document

CTRL+F12 Merge Annotations

CTRL+INSERT Insert New Pages (from scanner)

CTRL+PAGE DOWN Zoom In

CTRL+PAGE UP Zoom Out

CTRL+LEFT ARROW Pan Left (moves image, if zoomed)

LAW PreDiscovery128


Key Combination Action

CTRL+RIGHT ARROW Pan Right ARROW (moves image, if zoomed)

CTRL+UP ARROW Pan Up (moves image, if zoomed)

CTRL+DOWNARROW

Pan Down (moves image, if zoomed)

ESC Clear current region (if main image has focus)

ESC Clear selected pages (if thumbnails display has focus)

SHIFT+INSERT Attach to Previous

SHIFT+BACKSPACE Detach All

SHIFT+DELETE Delete Pages

Document list keys

The focus must be on the document list to use these shortcuts.

Key Action

LEFT Previous page

RIGHT Next page

UP Previous document

DOWN Next document

HOME First page

END Last page

DELETE Delete document

SPACEBAR Toggle page selection for current page

Related Topics

User Guides



Contacting LexisNexis

LexisNexis® offers the broadest choice of discovery solutions, giving law firms, corporationsand government agencies the efficiency, control, and confidence they need to litigatesuccessfully in the face of overwhelming data volumes and rapidly changing technology.

Technical Support

Our number one priority is our clients. Our representatives pride themselves on resolvingclient issues quickly and effectively. To receive technical assistance, or to provide feedback orsuggestions, please e-mail or call us. The Technical Support team is available from 9:00 A.M.to 8:00 P.M. Eastern Time, Monday - Friday.

E-mail: [email protected]

Phone: 1 (800) 833-3346 (Option 5 for LAW PreDiscovery. Option 7 for Early DataAnalyzer.)

Websites

Litigation Solutions:

http://www.lexisnexis.com/litigation

LexisNexis® Early Data Analyzer:

http://www.lexisnexis.com/litigation/products/ediscovery/early-data-analyzer

LAW PreDiscovery®:

http://www.lexisnexis.com/litigation/products/ediscovery/law-prediscovery

Sales

Our sales team is committed to helping you to find the right products to suit yourrequirements. Contact us to learn more about the many flexible licensing options for LAWPreDiscovery™, and to see how our related software and service offerings for litigationsupport — such as Concordance®, CaseMap®, and IDEX Full-Service Expert Witness Search— can help to integrate and accelerate your efforts to arrive at winning solutions.


Phone: 1 (800) 722-3288

Client Training Program

To help you meet the increasing complexity of electronic discovery, our Client Training

mailto:[email protected]

http://www.lexisnexis.com/litigation

http://www.lexisnexis.com/litigation/products/ediscovery/early-data-analyzer

http://www.lexisnexis.com/litigation/products/ediscovery/law-prediscovery


LAW PreDiscovery130


Program offers classroom experiences that focus on applying the powerful features of LAWPreDiscovery to solve real-world problems. To learn more about our training offerings, pleasee-mail or call us.


Phone: 1 (800) 227-9597 extension 1252111


Index 131


Index- A -auto-indexing 33

- B -batch processing

Log Viewer 19

Update Page 47

- C -Case Summary report 56

CaseLogistix

Unicode export format 124

cases

extracting subsets 31

scanning for errors 22

Unicode in case names 124

custodians

in deduplication reports 58

in Tally report 71

- D -database compacting 18

deduplication

Log Viewer 19

Deduplication reports 58

documents

reorganizing 21

validating ranges 29

- E -ED Loader

standalone grid reports 73

ED Loader Exception Report 64

ED Loader Session Report 60

EDRM XML


error logs 19

errors in case database 22

Excel

ED Loader session report format 60

exporting 124

delimited Unicode text 124

Log Viewer 19

Unicode 124

external commands 31

extracting subsets 31

- F -fields

counting unique values 71

descriptions 93

image 47

page-level 47

Unicode in field names 124

files

how many imported 65

types imported 65

Files by Type Report 65

Files By Type Summary report 67

folder

Folder Summary report 68

full-text indexing 33

auto-indexing 33

Chinese 33

credit card numbers 33

dates 33

e-mail addresses 33

hyphens 33

ignore duplicate documents 33

Japanese 33

Korean 33

temp files with NAS and SAN devices 33

- G -grids

viewing Unicode 124

- H -hotkeys

listing of 126

HTML

LAW PreDiscovery132


HTML

ED Loader Session Report 60

Files by Type report 65

- I -images

color property 47

fields for 47

size property 47

source property 47

importing

Log Viewer 19

Unicode 124

installation

SQL Server 43

- K -keyboard shortcuts 126

- L -LAW PreDiscovery overview 6

Law50.ini 47

LexisNexis contact information 129

licensing

capabilities listed by UI element 87

LexisNexis sales 129

Log Viewer 19

logs

batch processing 19

exporting 19

importing 19

Log Viewer 19

reorganizing 19

scandb.log 22

tagging 19

- M -metadata

Unicode 124

- O -OCR

Case Summary report 56

reorganizing documents prior to 21

Unicode 124

- P -page

area calculated 68

page counts

verifying 22

page fields 48

Page Properties report 70

page size tolerance 47

PageColor 47

PageColor tracking 48

PageHeight 47

page-level properties 47

pages

how many imported 65

PageSize 47

PageSize tracking 48

PageWidth 47

partial backup 31

PDF

creating reports 52

PgCount report 67

printing

Unicode 124

- Q -quality control

case files 22

document ranges 29

duplicate records 22


invalid records 22

Log Viewer 19

orphan records 22

PageID gaps 22

verifying page counts 22

querying

image properties 47

Index 133


querying

page properties 47

- R -range files

reorganizing documents 21

validating documents 29

release notes 9

reorganizing documents 21

reporting

standalone grid 73

reports

adding a logo 52

Case Summary 56

Deduplication 58


ED Loader session 60

Files by Type (import) 65

Files by Type Summary 67

Folder Summary 68

formatting in PDF 52

how to access 52

Log Viewer 19

native file counts 67

Page Properties 70

sizes per source application 67

Tally report 71

- S -scandb.log 22

scanning

Log Viewer 19

scripts 31

shortcuts

keyboard 126

SQL Server

enabling support for 43

SQL Express install example 43

user accounts 43

- T -tagging

log items 19

Tally report 71

text priority

full-text indexing 33

- U -Unicode

language pack requirement 124

summary of support 124

Update Page 47

- V -validating document ranges 29

verify page counts 22

verifying page counts 25, 28

- W -what's new 9

Word

printing Unicode text 124

- X -XML

ED Loader session report format 60
