LAW Pre Discovery User Guide

LAW PreDiscovery™ Software
User Guide
Version 5.7, June 2010
Copyright
LexisNexis and the Knowledge Burst logo are registered trademarks of Reed Elsevier Properties Inc., used under
license. LAW PreDiscovery is a trademark of LexisNexis, a division of Reed Elsevier Inc. Other products or services
may be trademarks or registered trademarks of their respective companies.
© 2008 LexisNexis, a division of Reed Elsevier Inc. All rights reserved.
Additional Resources
For additional help and support, please contact:
▪ General Product Information: www.lexisnexis.com/law-prediscovery

▪ LAW PreDiscovery Technical Support: phone: 866-831-0497, email: lawsupport@lexisnexis.com
▪ LAW PreDiscovery Training: phone: 425-463-3503, email: lawtraining@lexisnexis.com
1
LAW PreDiscovery User Guide
LAW Licensing .................................................................................................................18

Profile Manager ................................................................................................................18
Creating and Changing Passwords...............................................................................................18
Specifying the License Server.......................................................................................................18
Selecting Licenses.........................................................................................................................19
Creating Custom Profiles ..............................................................................................................20
Hiding System Profiles ..................................................................................................................20
Profile Manager - Administrative Mode .........................................................................................21
Concurrent User Licenses.............................................................................................................23
Adding New LAW Licenses to an Existing Server Key .................................................................23
Acquiring or Releasing Licenses in LAW ......................................................................................23
Undocked Keys ................................................................................................................25
Obtaining Undocked Keys.............................................................................................................25
Creating Undocked Keys...............................................................................................................25
Reclaiming Undocked Keys ..........................................................................................................25
Licenses Defined .............................................................................................................27
Admin (Import/Export) ...................................................................................................................27
CD Publishing w/Full Text .............................................................................................................27
Edit/Review (QC)...........................................................................................................................27
Electronic Discovery: e-Print .........................................................................................................27
Electronic Discovery: Loader.........................................................................................................27
Electronic Discovery: TIFF ............................................................................................................28
Endorse .........................................................................................................................................28
Full Text Indexing ..........................................................................................................................28
OCR (ABBYY FineReader) ...........................................................................................................28
OCR (ExperVision OpenRTK).......................................................................................................28
OCR (ExperVision PDF Add-On) ..................................................................................................28
Print ...............................................................................................................................................28
Scan...............................................................................................................................................28
TSI Scan........................................................................................................................................29
Creating a New Case .......................................................................................................31
Creating Cases..............................................................................................................................31
Creating Projects ...........................................................................................................................32
Editing Projects..............................................................................................................................33
Deleting Projects ...........................................................................................................................34
Working with Existing Cases..........................................................................................35
Opening Cases..............................................................................................................................35
2
LAW Licensing
Browsing to a Case .......................................................................................................................36

Viewing Case Properties ...............................................................................................................36
Deleting a Case .............................................................................................................................36
Creating Index Fields.......................................................................................................37
Adding a Field................................................................................................................................38
Field Types ...........................................................................................................................................................39
Changing Field Properties.............................................................................................................39

Deleting a Field..............................................................................................................................39
Changing the Field Order ..............................................................................................................39
Case Templates................................................................................................................41
Saving a Case Template ...............................................................................................................41
Applying a Case Template ............................................................................................................41
New Case .............................................................................................................................................................41
Existing Case ........................................................................................................................................................42
Populating List Items.......................................................................................................44

Adding List Items ...........................................................................................................................44
Deleting List Items .........................................................................................................................44
Renaming List Items......................................................................................................................44
Importing and Exporting List Values..............................................................................................45
Index Profiles ...................................................................................................................46
Creating Index Profiles ..................................................................................................................46
Applying and Modifying Index Profiles ..........................................................................................48
Deleting Index Profiles...................................................................................................................49
Establishing Folder Structures.......................................................................................50
Creating Folders ............................................................................................................................50
Auto-Creating Folders ...................................................................................................................50
Viewing Folder Contents ...............................................................................................................50
Deleting Folders ............................................................................................................................51
Renaming Folders .........................................................................................................................51
Moving Folders ..............................................................................................................................51
Folder Properties ...........................................................................................................................52
Summarize Images........................................................................................................................52
Importing Electronic Discovery......................................................................................53
Launching the ED Loader..............................................................................................................53
Session Configuration ...................................................................................................................54
Default Target Folder.....................................................................................................................54
Session Label ................................................................................................................................54
3
Default Custodian ..........................................................................................................................54

DocID Seed ...................................................................................................................................55
Adding/Removing Sources .............................................................................................56
Adding Sources .............................................................................................................................56
Drag and Drop Method ..................................................................................................................57
Removing Sources ........................................................................................................................57
Viewing Sources............................................................................................................................57
Long Paths ....................................................................................................................................57
Source Queue...................................................................................................................58
Editing Source-level Settings ........................................................................................................58
Resetting Source-level Settings ....................................................................................................59
Viewing Source Paths ...................................................................................................................59
File Type Summary ..........................................................................................................60
Viewing File Groups ......................................................................................................................61
Identifying File Types.....................................................................................................................62
Saving and Reloading ED Loader Summaries..............................................................................62
Generating Reports .......................................................................................................................62
Archives.........................................................................................................................................63
Compound Documents..................................................................................................................64
Deduplication.................................................................................................................................66
E-Mail.............................................................................................................................................68
Exclusions .....................................................................................................................................70
File Types ......................................................................................................................................71
General..........................................................................................................................................73
Source Selection ...........................................................................................................................73
File Type Management Database .................................................................................................74
NIST(NSRL) Filter .........................................................................................................................75
Hash Database..............................................................................................................................75
Options ..........................................................................................................................................76
Output............................................................................................................................................77
Folder Output Scheme ..................................................................................................................77
Options ..........................................................................................................................................77
Structure ........................................................................................................................................77
Post Import Actions .......................................................................................................................78
Text Extraction...............................................................................................................................79
Session Defaults............................................................................................................................80
Reviewing Sessions ........................................................................................................81
Session Viewer..............................................................................................................................81
Tabs......................................................................................................................................................................81
4
LAW Licensing
Session List...........................................................................................................................................................82
Fields ....................................................................................................................................................................82
Item Properties......................................................................................................................................................82
Exporting Session Data .................................................................................................................82

Summary Reports ............................................................................................................84
File Numbering......................................................................................................................................................85
Watermarks...........................................................................................................................................................85
Cancelling/Resuming Sessions......................................................................................86
Cancelling Sessions ......................................................................................................................86
Resuming Sessions.......................................................................................................................86
Lost Database Connection ............................................................................................................87
Scanning Documents ......................................................................................................88
Selecting a Scanner ......................................................................................................................88
Scanner Settings ...........................................................................................................................89
Scan Area......................................................................................................................................89
Scan Brightness ............................................................................................................................90
Special Settings.............................................................................................................................90
Scan Options .................................................................................................................................91
Imaging Options ............................................................................................................................94
Scanner Output .............................................................................................................................94
Color Format .........................................................................................................................................................94
File Type ...............................................................................................................................................................94
Compression.........................................................................................................................................................95
Storage Schema ...................................................................................................................................................95
Barcode Breaks ....................................................................................................................................................95
Scanning in LAW ...........................................................................................................................96

New Documents ............................................................................................................................96
Adding Documents................................................................................................................................................96
Adding Attachments..............................................................................................................................................96
Inserting Documents .............................................................................................................................................97
Modifying Existing Documents ......................................................................................................97
Appending Pages..................................................................................................................................................97
Inserting Pages .....................................................................................................................................................97
Replacing Pages/Documents................................................................................................................................98
Using Barcodes .............................................................................................................................99
5
Folder Level ..........................................................................................................................................................99
Document Level ..................................................................................................................................................100
Attachment Level ................................................................................................................................................100
Ignore Barcode Value .........................................................................................................................................100
Storing Barcode Break Sheet Values in a Field ..................................................................................................100
Dilate Scan Region .............................................................................................................................................100
Scan Entire Page ................................................................................................................................................100
Use Thorough Scan ............................................................................................................................................100
Extracting Barcode Information...........................................................................................................................101
Troubleshooting Barcode Breaks ................................................................................................101

Importing Images ...........................................................................................................103
Importing Cases and Load Files..................................................................................................103
Import Formats ............................................................................................................................103
LAW Case...........................................................................................................................................................103
Z-Print Load File .................................................................................................................................................103
Doculex Imagebase ............................................................................................................................................105
Opticon Load File................................................................................................................................................105
Summation Load File ..........................................................................................................................................105
IPRO Load File ...................................................................................................................................................107
EDRM XML 1.0 ...................................................................................................................................................107
Importing Raw Images.................................................................................................................108

Selecting Images .........................................................................................................................108
Import Options .............................................................................................................................108
Convert images to binary (B&W).........................................................................................................................109
Determine document breaks ...............................................................................................................................109
Include OCR .......................................................................................................................................................109
Link to images in place .......................................................................................................................................110
Remove originals ................................................................................................................................................110
Use filename as BegDoc#...................................................................................................................................110
Mirror original structure .......................................................................................................................................110
Auto-increment folder..........................................................................................................................................110
Store original filename ........................................................................................................................................110
Store original location .........................................................................................................................................110
Image Display.................................................................................................................111
6
LAW Licensing
Viewing Images ...........................................................................................................................111

Zoom Features ............................................................................................................................111
Zoom In/Zoom Out..............................................................................................................................................111
Best Fit/Fit to Width.............................................................................................................................................111
Zoom Lock ..........................................................................................................................................................111
Scrolling the Image......................................................................................................................111
Pan Window........................................................................................................................................................111
Viewer Options ............................................................................................................................112
Scale to Gray ......................................................................................................................................................112
Invert ...................................................................................................................................................................112
Rotating Pages ............................................................................................................................112

Page Navigation ..........................................................................................................................112
Thumbnails Display .....................................................................................................................113
Selecting Pages...........................................................................................................................113
Viewing File Properties .................................................................................................116
Image Page Properties................................................................................................................116
Viewing Properties for Image Records........................................................................................116
Viewing File Properties for Native Records.................................................................................117
Manipulating Documents ..............................................................................................119
Page-Level Cleanup ....................................................................................................................119
Deskew........................................................................................................................................119
Enhancing Images.......................................................................................................................119
Rotate Pages...............................................................................................................................120
Moving Documents/Pages ..........................................................................................................121
Moving Documents......................................................................................................................121
Moving Pages..............................................................................................................................121
Deleting Documents/Pages.........................................................................................................123
Deleting Documents ....................................................................................................................123
Deleting Pages ............................................................................................................................123
Deleting Records from the Grid Displays ....................................................................................123
Splitting Documents.....................................................................................................................125
Split Options ................................................................................................................................126
Merging Documents ....................................................................................................................128
Inserting Document/Pages ..........................................................................................................129
Inserting Documents....................................................................................................................129
Inserting Pages............................................................................................................................129
Inserting Existing Pages ..............................................................................................................130
Replacing Document/Pages........................................................................................................131
7
Replacing a Document ................................................................................................................131

Replacing a Page ........................................................................................................................131
Replacing Documents with Existing Images ...............................................................................132
Working with Attachments............................................................................................133
Adding Attachments ....................................................................................................................133
Removing Attachments ...............................................................................................................133
Validating Attachments................................................................................................................134
Annotations ....................................................................................................................135
Creating Annotations ...................................................................................................................135
Viewing and Printing Annotations................................................................................................135
Merge Annotations ......................................................................................................................135
Editing Annotation Tool Properties..............................................................................................136
Sticky Mode .................................................................................................................................136
Working with Native Documents ..................................................................................137
Extracting Page Counts...............................................................................................................137
Launching Native Files ................................................................................................................140
Launching Files Using Hyperlinks ...............................................................................................140
Launching Files Using Open File Button .....................................................................................140
Locating Native Files in the Case Folder.....................................................................................141
Native File Review Mode.............................................................................................................141
Native E-Mail Review ..................................................................................................................141
Inserting Electronic Documents...................................................................................................142
Single Document TIFF Conversion .............................................................................................144
Grid Displays..................................................................................................................147
Launching the Grids ....................................................................................................................147
Specifying the Preferred Grid ......................................................................................................147
Methods of Launching the Grids .................................................................................................148
Customizing Grid Views ..............................................................................................................150
Creating Grid Profiles ..................................................................................................................150
Switching Profiles ........................................................................................................................151
Selecting Fields to Display ..........................................................................................................152
Moving Fields ..............................................................................................................................152
Changing Grid Colors ..................................................................................................................152
Deleting Profiles ..........................................................................................................................153
Grid Functions .............................................................................................................................154
Selecting Fields to Display ..........................................................................................................154
Sorting Records...........................................................................................................................154
Saving Records to File ................................................................................................................155
Printing Records ..........................................................................................................................156
Batch Updating ............................................................................................................................157
8
LAW Licensing
Deleting Records .........................................................................................................................157

Viewing Attachment Fields ..........................................................................................................158
Viewing Document and Page Totals ...........................................................................................158
Working with Columns, Rows, and Cells.....................................................................................158
Building Control Lists...................................................................................................................159
Creating Outlook PST Files.........................................................................................................160
Resetting Text Flags....................................................................................................................162
Spell Checking.............................................................................................................................162
Generating an Index Summary ...................................................................................................162
Searching........................................................................................................................163
Grouping......................................................................................................................................163
Removing Groups........................................................................................................................163
Filtering........................................................................................................................................164
Filtering Records .........................................................................................................................164
Removing Filters..........................................................................................................................165
Query Builder...............................................................................................................................167
Specifying Search Criteria...........................................................................................................168
Removing Conditions ..................................................................................................................168
Returning Additional Records......................................................................................................168
NOLOCK Setting .........................................................................................................................169
Saving Queries ............................................................................................................................169
Executing a Saved Query............................................................................................................170
Search History .............................................................................................................................171
Full Text Searching........................................................................................................173
Full Text Search Options .............................................................................................................173
Retrieval Thresholds ...........................................................................................................................................174
Search Syntax.....................................................................................................................................................174
Results Options...................................................................................................................................................174
Performing Full Text Searches....................................................................................................175
Tagging Text Hits................................................................................................................................................176
Term Searching ..................................................................................................................................................177
Noise Words .......................................................................................................................................................177
Combining Database and Full Text Searches.............................................................................178

Full Text Reports .........................................................................................................................178
Persist Text Hits ..........................................................................................................................182
Document-Level Coding................................................................................................185
Updating Documents ...................................................................................................................185
9
Single Document.................................................................................................................................................185
Multiple Documents ............................................................................................................................................185
Coding Options............................................................................................................................185
Auto-Advance .....................................................................................................................................................186
Default Field........................................................................................................................................................186
List Field Options.........................................................................................................................186

Importing Data................................................................................................................187
Batch Updating ..............................................................................................................189
Batch Updating in the Grid Displays............................................................................................189
Batch Updating in the Index Display ...........................................................................................190
Numbering Documents/Pages......................................................................................191
Auto-Numbering ..........................................................................................................................191
Auto-Number Function ........................................................................................................................................191
Numbering during the Scan Process ..................................................................................................................193
Document/Page Level Numbering ......................................................................................................................193
Alpha-Numeric Numbering..................................................................................................................................193
Document Level Attachment Numbering ............................................................................................................193
Rolling Numeric Sections ....................................................................................................................................195
Manually Numbering Pages ........................................................................................................196

Finding Specific Page IDs ...........................................................................................................196
Creating Tag Fields........................................................................................................197
Tagging Records............................................................................................................199
Tagging Individual Records.........................................................................................................199
Hotkeys ...............................................................................................................................................................199
Tagging Multiple Records............................................................................................................200
Batch Tagging Options .......................................................................................................................................201
Batch Updating ...................................................................................................................................................201
Importing Tag Lists........................................................................................................203

Batch Processing Overview..........................................................................................205
Document and Page Counts .......................................................................................................205
Document Numbering..................................................................................................................206
Image Cleanup ............................................................................................................................206
Endorse .......................................................................................................................................207
OCR.............................................................................................................................................207
10
LAW Licensing
Print (Standard-Image Only) .......................................................................................................207

E-Print (ED-Native Files) .............................................................................................................207
Scan for Suspect Footers ............................................................................................................208
TIFF Conversion..........................................................................................................................208
Update Page Data .......................................................................................................................208
OCR Overview ................................................................................................................209
OCR Indicator..............................................................................................................................209
Flagging Documents/Pages for OCR ..........................................................................................210
Tracking OCR Status...................................................................................................................210
OcrStatus Field ...................................................................................................................................................210
OcrFlag Field ......................................................................................................................................................210
Manually Flagging Pages ............................................................................................................210

Flagging Pages at Scan Time .....................................................................................................211
Displaying Flagged Pages...........................................................................................................211
OCR Options ...............................................................................................................................212
Available Options.........................................................................................................................212
OCR Engine........................................................................................................................................................212
Page Layout........................................................................................................................................................213
Quality.................................................................................................................................................................213
Language ............................................................................................................................................................213
Output Format.....................................................................................................................................................213
Page Markers......................................................................................................................................................214
Auto-Rotate.........................................................................................................................................................215
Auto Deskew.......................................................................................................................................................215
Create PDF Thumbnails .....................................................................................................................................215
Retain Page Layout ............................................................................................................................................215
Retain Pictures....................................................................................................................................................215
Overwrite Existing Files ......................................................................................................................................215
Reset Text Index Status......................................................................................................................................216
OCRing Documents.....................................................................................................................217
OCRing........................................................................................................................................217
Single Document.................................................................................................................................................217
Multiple Documents ............................................................................................................................................217
OCRing a Region ........................................................................................................................217

Creating Searchable PDFs..........................................................................................................219
Checking the OCR Settings ........................................................................................................219
11
Create PDF Thumbnails ..............................................................................................................219

Exporting the Searchable PDF Files ...........................................................................................220
Header/Footer Options ................................................................................................................221
Setting Border Size......................................................................................................................221
Setting Fonts.......................................................................................................................................................221
Setting Text.........................................................................................................................................................222
Auto-Incrementing Using Index Fields ................................................................................................................222
Removing a Header/Footer .........................................................................................................222

Watermark ...................................................................................................................................223
Special Notes: .............................................................................................................................223
Creating a Custom Watermark....................................................................................................224
Print Options................................................................................................................................225
Auto-Rotate Pages ......................................................................................................................225
Auto-Size Paper ..........................................................................................................................225
Do Not Print Annotations .............................................................................................................226
Include Separator Pages.............................................................................................................226
Limit Jobs in Print Queue ............................................................................................................226
Rip to PDF Before Printing ..........................................................................................................226
Send Jobs in Batches..................................................................................................................226
Staple Documents .......................................................................................................................227
Tracking Print Jobs in the Spooler ..............................................................................................227
E-Print/TIFF Output Settings .......................................................................................................228
E-Print Options ............................................................................................................................228
Print Jobs ............................................................................................................................................................229
TIFF Output Options....................................................................................................................229

Saving Defaults ...........................................................................................................................232
Tracking Print Jobs in the Spooler ..............................................................................................232
Supported File Types ..................................................................................................................233
Special File Type Notes...............................................................................................................234
Acrobat ........................................................................................................................................236
E-Mail...........................................................................................................................................237
Excel ............................................................................................................................................238
Orientation ...................................................................................................................................239
Scaling.........................................................................................................................................239
Print .............................................................................................................................................240
Page Order ..................................................................................................................................240
Field Replacements.....................................................................................................................240
HTML ...........................................................................................................................................241
Image Printer ...............................................................................................................................242
Passwords ...................................................................................................................................243
12
LAW Licensing
PowerPoint ..................................................................................................................................244
Word ............................................................................................................................................246
Settings........................................................................................................................................246
Field Replacements.....................................................................................................................247
Separator Pages..........................................................................................................................248
Header and Footer ......................................................................................................................249
Fields ...........................................................................................................................................250
Options ........................................................................................................................................250
Saving Default Settings ...............................................................................................................251
Distributed Batch Processing.......................................................................................252
Initializing a Shared Batch...........................................................................................................252
Joining a Shared Batch ...............................................................................................................253
Deleting Shared Batches.............................................................................................................253
LAW Management Console...........................................................................................255
LMC Overview .............................................................................................................................255
Startup .........................................................................................................................................255
Configuration ...............................................................................................................................257
Initial Configuration of the LMC ...................................................................................................257
Creating a Shared Batch in LAW ................................................................................................259
Automatically Joining Shared Jobs .............................................................................................261
Operation.....................................................................................................................................263
Client Overview ...........................................................................................................................263
Client Details ...............................................................................................................................264
Job Overview...............................................................................................................................265
Job Details...................................................................................................................................267
Logs .............................................................................................................................................269
Application Settings .....................................................................................................................270
Cancelling Batches......................................................................................................................270
License Overview ........................................................................................................................271
License Details ............................................................................................................................272
Deduplication Utility ......................................................................................................273
Info Tab .......................................................................................................................................273
Tools Tab.....................................................................................................................................275
Settings Tab ................................................................................................................................275
Inter-Case Deduplication...............................................................................................278
External Deduplication Database ................................................................................................279
Options ........................................................................................................................................279
Member Cases ............................................................................................................................279
Deduplication Process.................................................................................................................280
Process Summary .......................................................................................................................280
13
LAW Deduplication Fields ...........................................................................................................281

Deduplication Mode.....................................................................................................................281
Reviewing Duplicates ..................................................................................................................282
Duplicate Viewer ............................................................................................................283
Records Deduplicated Internally .................................................................................................284
Records Deduplicated Externally ................................................................................................285
Deleted Records..........................................................................................................................287
Retrieving the Case Deduplication Status...................................................................................287
Export Utility Overview..................................................................................................289
Image Format......................................................................................................................................................290
Load File Extensions...........................................................................................................................................290
Supported Formats......................................................................................................................291
Export Profiles .............................................................................................................................293
Creating Profiles ..........................................................................................................................293
Opening Saved Profiles...............................................................................................................293
Formats/Documents Tab .............................................................................................................294
File Types ....................................................................................................................................294
Documents ..................................................................................................................................296
Document and Page Counts ...............................................................................................................................297
Formats .......................................................................................................................................297
Format-Specific Settings...............................................................................................299
CaseMap .....................................................................................................................................299
Data Delimiters ...................................................................................................................................................299
Path Notation ......................................................................................................................................................299
Other ...................................................................................................................................................................299
CaseLogistix ................................................................................................................................300
Path Notation ......................................................................................................................................................300
Other ...................................................................................................................................................................300
Concordance ...............................................................................................................................301
Settings........................................................................................................................................301
Concordance Direct (DCB)..........................................................................................................303
Settings........................................................................................................................................303
Delimited Text..............................................................................................................................306
DocuMatrix 1.5 ............................................................................................................................307
EDRM XML 1.0............................................................................................................................308
14
LAW Licensing
iCONECT.....................................................................................................................................309
Introspect eCM ............................................................................................................................310
General........................................................................................................................................310
IPRO IntelliVIEW .........................................................................................................................312
JFS Litigator's Notebook .............................................................................................................314
PDF Conversion ..........................................................................................................................315
Ringtail Casebook .......................................................................................................................316
Ringtail Format Notes..................................................................................................................317
Storm Viewer ...............................................................................................................................318
Summation ..................................................................................................................................319
Settings........................................................................................................................................319
TrialDirector and Sanction...........................................................................................................321
Fields Tab .......................................................................................................................322
Selected Format ..........................................................................................................................322
Selecting Fields ...........................................................................................................................323
Image Tag Field...........................................................................................................................323
Options Tab ....................................................................................................................324
Output Path .................................................................................................................................324
File Naming Scheme ...................................................................................................................325
Folder Naming Scheme...............................................................................................................325
Output Settings............................................................................................................................326
Export Status ...............................................................................................................................328
Advanced Tab ................................................................................................................329
Perform Blank Value Checks ......................................................................................................329
Perform Duplicate Checks...........................................................................................................329
Creating CD Volumes ....................................................................................................330
Administration................................................................................................................331
Case Summary ...............................................................................................................331
Compacting the Database.............................................................................................333
Log Viewer...................................................................................................................................334
Reviewing Errors ...........................................................................................................334
Reorganize Documents .................................................................................................336
Scanning for Errors .......................................................................................................337
Documents ..................................................................................................................................337
Options ........................................................................................................................................337
Find invalid records (missing images).................................................................................................................337
Find gaps in Page IDs.........................................................................................................................................338
15
Remove duplicate/orphan page records .............................................................................................................338
Verify Page Counts .............................................................................................................................................338
Validating Document Ranges .......................................................................................339

Extracting Subsets ........................................................................................................340
Run Commands .............................................................................................................341
Populate RecordType Values......................................................................................................341
Full Text Indexing ..........................................................................................................343
Indexing Options..........................................................................................................................343
Flagging Documents for Indexing................................................................................................346
Indexing Documents....................................................................................................................347
_FTIndex Field.............................................................................................................................347
Full Text Index Properties ...........................................................................................................347
Configuring LAW and SQL Server ...............................................................................349
Enable LAW SQL Server Support ...............................................................................................349
Create SQL Server LAW User Account(s) ..................................................................................349
Global Default User .....................................................................................................................349
Integrated Security ......................................................................................................................349
SQL Server Notes .......................................................................................................................349
Tracking Page Source, Size, and Color .......................................................................351
Field Names and Possible Values...............................................................................................351
Update Page Data Batch Process...............................................................................................352
Reporting .....................................................................................................................................353
Viewing Reports.............................................................................................................353
Generating Reports .....................................................................................................................353
Report Types ...............................................................................................................................355
ED Loader Session Report............................................................................................357
Report Options ............................................................................................................................357
ED Loader Session Report Contents ..........................................................................................357
Exception Report ...........................................................................................................359
Report Options ............................................................................................................................359
Exception Report Contents .........................................................................................................359
Files By Type Report .....................................................................................................362
Report Options ............................................................................................................................362
Files By Type Contents ...............................................................................................................362
Files By Type Summary Report....................................................................................364
Report Options ............................................................................................................................364
16
LAW Licensing
Files By Type Summary Report Contents ...................................................................................364

Deduplication Reports...................................................................................................366
Report Options ............................................................................................................................366
Deduplication Report Contents ...................................................................................................366
Page Properties Report .................................................................................................369
Report Options ............................................................................................................................369
Page Properties Report Contents ...............................................................................................369
Tally Report ....................................................................................................................371
Report Options ............................................................................................................................371
Tally Report Contents..................................................................................................................371
Appendix.........................................................................................................................373
Deduplication Information ............................................................................................373
Key Generation............................................................................................................................373
Fields ...........................................................................................................................................373
Scopes.........................................................................................................................................374
Actions.........................................................................................................................................374
Attachments.................................................................................................................................374
(Partially Exclude) File Type Filter Action and Deduplicating......................................................375
Unicode Support ............................................................................................................376
Shortcut Keys.................................................................................................................377
Function Keys..............................................................................................................................377
Control Keys ................................................................................................................................377
Document List Keys.....................................................................................................................378
Contacting LexisNexis ..................................................................................................379
About LexisNexis.........................................................................................................................379
Technical Support........................................................................................................................379
Training........................................................................................................................................379
Sales............................................................................................................................................379
Index................................................................................................................................381
17
LAW Licensing
Profile Manager
LAW uses a server-based licensing scheme, making it easier to track and assign licenses. All licenses are
maintained on one or more hardware dongles installed on a host computer, referred to as the "License Server." Each
workstation is then able to access the License Server through the network to "check out" available licenses for use on
that individual workstation.
The LAW Profile Manager enables users to select licenses, create profiles, identify the licenses in use, and identify
the licenses currently available.
To initially launch the Profile Manager after the installation of LAW, start the LAW PreDiscovery Software from the
program folder or from the shortcut icon on the desktop.
Creating and Changing Passwords

When selecting File > Switch to Administrative Mode or the Advanced button in the Profile Manager for the first
time on a computer, a prompt to enter an administrative password will appear. The password is stored at a
workstation level, meaning each computer on which LAW is launched, whether running locally or in a client/server
configuration, will prompt for a password when executed initially.
When the Enter Admin Password dialog appears, enter a password in the first field and then enter it again in the
second field to confirm. The password must be at least six characters in length and is case-sensitive.
To change the password for a particular station, click the Advanced button on the LAW Profile Manager dialog.
When the LAW Profile Manager (Administrative Mode) dialog appears, click Tools > Change Administrative
Password, enter the new password in each field, and click OK.
Note: A prompt for a password after clicking Advanced indicates that the user is not currently in administrative
mode. For more information, see "License Profile Manager - Administrative Mode."
Specifying the License Server

After starting LAW for the first time on a computer, the Change License Server dialog will appear.
Enter the hostname of the computer to which the LAW dongle is physically attached. In the above example, ICESQL
was used.
Note: If LAW is installed on a network and the program file, Law50.exe, is shared, the hostname only needs to be
entered once. If LAW is executed locally, the hostname needs to be entered for each workstation when the product
is launched.
18
LAW Licensing
Note: If a hardware key is not found on the specified server, a message will appear stating that the key was not
found and will ask to try another server. If Yes is chosen, the Change License Server will appear once again and a
new hostname will need to be specified. Click OK after entering the hostname. If a key had been used successfully
on the machine in the past, however, and was later removed, the Profile Manager will still launch and then display
the error after attempting to check out licenses.
The LAW Profile Manager will appear once a valid hostname has been entered.
The button located to the right of the 'License Server' name ( ) will allow users to change the license server at any
time.
Selecting Licenses
The area below the 'License Server' name displays any license profiles created by the user as well as two default
entries related to license selection: <Any Available Licenses> and <Custom>.
<Any Available Licenses> "Checks out" one of each available license. These licenses will not be available
to other workstations using the same license key. Clicking OK starts LAW PreDiscovery Software.
<Custom> Users can check out specific licenses based on their tasks. For example, if a user needs to scan
documents, she can choose only the Scan license. Clicking OK opens the list of licenses.
Select the licenses needed for the session and click OK. Only the selected licenses will be checked out
and available on that workstation. If one or more license modules cannot be checked out, a message
box will appear stating which licenses could not be acquired. This message will not appear if the CD
Publishing license could not be acquired.
19
Creating Custom Profiles

Click Add on the initial LAW Profile Manager dialog to create a custom profile. If the Add button is grayed out, switch
to administrative mode to enable it (File > Switch to Administrative Mode and enter the password). The Add New
Profile dialog appears.
Enter the name of the profile and, optionally, a description. Select the licenses to include in the profile. To set this as
the default profile for the current user, select Default Profile. Click OK.
The new license profile is displayed in the LAW Profile Manager dialog box. If selected as the default profile, it is
automatically highlighted.
Tip: To automatically check out licenses and bypass the LAW Profile Manager, select the profile as the default
profile. Then clear the check box Prompt for profile when starting LAW in the LAW Profile Manager dialog box.
To re-enable this setting, set Prompt=1 in the profman.ini file in <application path>\ProfMan. The section in the INI
file containing this setting is in the following format: [<user name>].
Hiding System Profiles

Two system profiles are displayed by default in the LAW Profile Manager: <Any Available Licenses> and <Custom>.
These profiles may be hidden to prevent other users from checking out more licenses than needed for the current
LAW session. To hide a system profile, click File > Switch to Administrative Mode. Enter the administrative
password and then click OK. Click OK to the "Success" message box that appears if the correct password was
20
LAW Licensing
entered. Right-click the desired system profile in the LAW Profile Manager dialog box and choose Hide System
Profile.
The profile will no longer be visible. To restore the hidden profiles, right-click anywhere in the profile selection area
and choose Restore Hidden Profiles. At least one profile, system or user-defined, must be visible at all times.
Profile Manager - Administrative Mode

Switching to administrative mode in the Profile Manager will allow users access to a number of features, such as
creating profiles and reclaiming undocked keys (see Undocked Keys section). After launching the Profile Manager,
select File > Switch to Administrative Mode and enter the administrator password. If this is the first time switching
to administrative mode on the current computer, please see the "Creating and Changing Passwords" section in this
topic. This is one method of switching to administrative mode. In addition, any feature requiring an administrator
password prompts the user for the password. Once the password is entered, the Profile Manager is switched to
administrative mode.
Switching to administrative mode allows users to perform the following tasks:
Add, edit, and delete profiles

Create and reclaim undocked keys
Refresh licenses to add any newly purchased licenses to the server key
Enter the advanced view of the Profile Manager
Hide/restore system profiles
To view additional information after switching to administrative mode, click the Advanced button. The LAW Profile
Manager (Administrative Mode) dialog appears.
21
1. Menu Bar: Contains the following:
File: Provides options to refresh profiles and license servers for viewing the most updated
information.
Profile: Allows users to add, edit, and delete profiles as well as the set the desired profile as the
default.
Server Key: Allows users to change the license server, manage undocked keys, and refresh the
license counts when new licenses have been purchased and added to the existing server key.
Tools: Contains options to change the Admin password as well as enable server key enumeration.
Enabling the enumeration option will force the Profile Manager to find all server keys on the network and list
them in the License Servers section.
2. Profiles: Lists all profiles stored on the current machine as well as the two default license selection
methods. When a profile is selected, the right pane will display the name, description, and licenses stored in
that particular profile.
3. License Servers: Lists the current license server, including its IP address, host name, and concurrent
user counts (see next section). If the server key enumeration option is enabled, all other server keys on the
network will be displayed here as well. If any undocked keys currently exist, they will be displayed below the
server key's serial number.
4. License: Lists each type of LAW license. Licenses that do not exist on the key will be grayed out.
5. Total: Displays the total number of each particular license on the current server key.
6. In Use: Displays the number of licenses in use for each type of license.
7. Free: Displays the number of available licenses for each type of license.
22
LAW Licensing
Concurrent User Licenses

The total number of concurrent user licenses owned by a company will indicate the total number of users that may
work in LAW, with any combination of licenses, at the same time. For example, if a key contains 10 concurrent user
licenses, and 3 workstations are currently logged into LAW, then 7 concurrent user licenses will be available at that
time.
In the License Servers tree (#3 above), the current license server key's serial number is listed with two numbers in
parentheses beside it. These two numbers reflect concurrent user license counts. The first number indicates the
number of concurrent licenses in use, while the second number indicates the total number of concurrent licenses
contained on the server key. For example, (5/25) would indicate that LAW is currently open on 5 stations and 25 total
concurrent licenses are contained on the key (meaning 20 concurrent user licenses are currently available).
The amount of concurrent user licenses currently owned by a company will depend on a number of factors. If more
are needed, additional licenses may be purchased individually. See the Contacting LexisNexis section to find contact
information for the Sales department.
Adding New LAW Licenses to an Existing Server Key

When additional licenses are purchased for LAW, they will be added to the user's existing LAW server key. Once a
LexisNexis representative has updated the license counts to reflect the newly purchased licenses, the user will need
to launch the Profile Manager and click File > Refresh License(s) from Internet (must be in administrative mode
first). The key will be updated with the new license counts.
Acquiring or Releasing Licenses in LAW

To avoid closing LAW and launching the Profile Manager in order to change the selection of license modules,
licenses can be checked out and released from within the LAW application. Click Help > About LAW > Licenses to
launch the License Information dialog.
23
The "Active Key" section of this dialog will display the license server name, the serial number of the key(s), and
expiration date(s) (if applicable). Licenses in use by the current workstation will have check marks in the boxes
beside them in the "Licenses" section of this dialog. To acquire a license, check the box beside the license module
name in the list. A message box will appear indicating whether or not the license acquisition was successful. To
release a license, deselect the box beside the license module name (no message will appear when releasing
licenses). At least one license must remain checked out while LAW is running. Also, if the OCR license is released,
OCR Add-on (PDF) will be automatically released as well as it is dependent on the OCR license.
Note: This feature will be disabled when an undocked key or temp license is used or while running LAW in demo
mode.
24
LAW Licensing
Undocked Keys
Licenses can be "checked out" from the LAW dongle and placed on other dongles (referred to as "undocked keys").
This feature is useful for completing on-site scanning projects, for example. A user can choose one or more licenses
(i.e., Scan, Admin, Edit\QC) from the dongle on the license server, specify the length of time the licenses will be
checked out, and pull those licenses to the undocked key or keys. When the licenses are ready to be returned, the
user simply returns the licenses to the server key, allowing other LAW users to access them once again.
Obtaining Undocked Keys

LAW 4.0 and Z-Print keys that have been upgraded to LAW 5.0 and later can be used as undocked keys. There will
be no other use for these keys once the upgrade process has been completed. If users do not possess 4.0/Z-Print
hardware keys, undocked keys can be purchased from LexisNexis. Please see the Contacting LexisNexis topic for
the Sales department contact information.
Note: Server keys can not be used as undocked keys.
Creating Undocked Keys

Attach an undocked key to any LAW station that has access to the server key. Launch the LAW Profile Manager on
that station by double-clicking the LAW shortcut (or by double-clicking the profman.exe in the Law50\Profman folder).
When the LAW Profile Manager dialog appears, select File > Switch to Administrative Mode and enter the
administrator password. Once in administrative mode, select File > Undocked Key Admin > Create Undocked Key.
The Select License(s) dialog appears. Select the licenses to be "checked out" from the server key and placed on the
undocked key. Next, select an expiration date. The undocked key now contains the selected licenses and is ready for
use. One concurrent user license is taken from the server key for each undocked key created.
Note: An Internet connection is required in order to create an undocked key.
Undocked keys can also be created from the LAW Profile Manager (Administrative Mode) dialog box. To open this
dialog box, click the Advanced button and enter the administrator password. If you are already in administrative
mode, you will not be prompted for a password. With the undocked key attached, click the LAW server key below
"License Servers" in the left pane. Then click Server Key > Create Undocked Key. Or right-click the server key and
select Create Undocked Key. Follow the steps in the previous paragraph to create the key.
When one or more undocked keys have been created, an "Undocked Keys" entry is listed under the server key. Click
this item to view the key's serial number, check-out date, and expiration date. The link in this pane is used to
"Reclaim Undocked Key(s)", as explained in the next section.
Reclaiming Undocked Keys

To return the licenses on the undocked key to the server key prior to the expiration date specified during creation, first
attach the undocked key to a LAW station. Launch the LAW Profile Manager, select File > Switch to Administrative
Mode and enter the administrator password. Next, select File > Undocked Key Admin > Reclaim Undocked
Key(s). The Profile Manager searches for a key attached to the local computer. If an undocked key with licenses is
found, LAW reclaims all licenses on the undocked key and returns them to the server key. If an undocked key is not
attached, LAW attempts to locate any expired undocked keys not attached to the computer and prompts the user to
reclaim the licenses. If this method is used, the undocked key or keys will need to be attached at some point and
reclaimed in order to use that particular key again to undock licenses.
Note: Selecting Reclaim Undocked Key(s) from the File menu in the LAW Profile Manager currently only reclaims
licenses from keys attached to the computer and does not look for unattached expired keys.
Undocked keys can also be managed from the LAW Profile Manager (Administrative Mode) dialog box. To open this
dialog box, click the Advanced button and enter the administrator password. With the undocked key attached, click
25
the LAW server key below "License Servers" in the left pane. Then click Server Key > Reclaim Undocked Key(s).
You can also right-click the server key and select Reclaim Undocked Key(s) or click the "Reclaim Undocked Key(s)"
link in the right pane.
26
LAW Licensing
Licenses Defined
Each license module will allow LAW users to perform certain functions within the software. All licenses will
allow users to open a case, utilize the View and Help menus, print single documents (image records) to paper,
navigate pages of documents, rotate pages, view properties of a page, launch both grid displays, access the Run
Command feature, and access the Tools->Options dialog.
A LAW license matrix is also available in this help file and provides a detailed breakdown of which licenses are
needed to access each menu item.
Admin (Import/Export)
Create cases
Modify/create index fields
Import/export (minus ED Loader imports)
Perform administrative functions (case summary, reorganize case, scan for errors, compact database,
validate ranges, view reports, save/apply case templates)
Create/delete folders
Number documents
View Reports
CD Publishing w/Full Text

Allows LAW to create searchable OCR indexes for Storm exports
Edit/Review (QC)
Save and Save As
Access Edit features, except Scan-related (Replace and Insert New Page)
Code index fields
Search, filter, group, and flag records
Clean up images (page-level and batch)
Replace tiffs
Number documents
Electronic Discovery: e-Print

Batch print native files directly to paper
Print slipsheets with document info
Electronic Discovery: Loader

Import native files and metadata into LAW
Extract text from native files
Deduplicate native files
27
Electronic Discovery: TIFF

Convert native files to tiff images in LAW
Replace image in LAW with existing image file
Convert single documents to tiff images (print file through native application and save resulting tiff to LAW
record)
Endorse
Assign headers/footers/watermarks
Number documents
Endorse documents
Full Text Indexing

Indexes OCR, extracted, and/or printed text to allow full text searching in LAW cases (SQL cases only)
OCR (ABBYY FineReader)

Reset OCR flags
OCR documents or pages
Create searchable PDF or PDF/A files using the ABBYY FineReader OCR engine
OCR CJK (Chinese, Japanese, and Korean) languages
OCR (ExperVision OpenRTK)

Reset OCR flags
OCR documents or pages
OCR (ExperVision PDF Add-On)

Create searchable PDF files using the ExperVision OpenRTK OCR engine
Print
Assign header/footer/watermark to printed pages
Batch print image records to paper
Print slip sheets between documents with or without field information
Scan
Scan documents (all Scan features)
Edit documents (all Edit menu features, including Insert and Replace)
Number documents
Clean up images
Reset OCR flags
28
LAW Licensing
TSI Scan
Allows scanning to a LAW case using LAWtsi (touch screen interface). For more information, see the LAWtsi
product sheet.
29
Creating a New Case
Creating a New Case

Before users can begin working in LAW, a case must first be created or opened. LAW stores information about
these cases in the case list database (caselist.mdb). By default, the case list is stored in the same directory as the
LAW executable. If the case list file is not found the first time a user attempts to access the case list, the user will be
prompted to browse to an existing case list file. This allows users to share the same case list among multiple stations,
so that when one station adds or removes a case, all other stations will see those changes. If Yes is selected, browse
to an existing case list. Selecting No will automatically create a new case list. To change the case list at a later time
after one has already been selected, press <CTRL+B> from the case list form. This activates the browse dialog,
allowing the user to select a new case list.
One caveat to keep in mind if sharing a case list among multiple stations is that the case paths must be located on a
shared network drive that is identically mapped for all stations.
Creating Cases
To create a new case, select New Case from the File menu or press the New Case button on the main form toolbar.
The Select Database Engine dialog will appear. LAW currently supports three possible database types for creating a
new case: Microsoft Access, ADS (Advantage Database Server), and SQL Server/SQL Express. MS Access is the
database type shipped with new LAW installations.
Microsoft Access does not need to be installed on a machine in order to create an Access case in LAW. The
purchase and configuration of ADS and/or SQL Server is required before these two database types may be used with
LAW. (SQL Express is a free version of SQL with a limitation of 4 GB total database size.) For instructions on
enabling SQL support, see Configuring LAW and SQL. Instructions for installing and configuring ADS cases may be
obtained by contacting Technical Support.
Select the desired database type for the new case and click OK. Once the desired database type has been selected,
the following New Case - Properties dialog will appear.
31
The New Case - Properties dialog allows users to specify the name of the case, case description, case template,
client or project name, and the path where the database and images will be stored. The Case Name must be unique
and must adhere to typical file name restrictions (e.g., cannot contain ? / \). The Case Template drop-down allows
users to select a previously created template. A case template will store user-defined index fields and folder
structures (optional). See Case Templates for more information.
If the case will contain electronic discovery data, select the Enable Electronic Discovery for this case option. When
this feature is enabled, LAW will automatically create the system fields and supporting database tables necessary for
processing electronic discovery using the Electronic Discovery Loader. The "Client or Project Name" feature is
discussed in the next section.
The New Case - Properties dialog box allows users to modify the default paths for databases and images. The
default paths may be modified by clicking the Options button and entering the desired paths. It is acceptable to
select a different location for the database versus the images. These paths will be applied automatically when
creating a new case. To override the default paths for a particular case, change the path information in the Case
Paths section on the New Case - Properties dialog. The case will be stored in the new location, leaving the default
paths intact for future case creation.
Creating Projects
As mentioned in the previous section, client or project names may be associated with LAW cases. This feature is
useful for grouping cases when data for a single project is separated into multiple cases. From the New Case -
Properties dialog, click the Edit List button to launch the Project Administration dialog.
32
Working With Cases
Click the New Project button to launch the New Project dialog.
Enter the client or project name for the case in the Project Name field. The Project Description is not required but
may be helpful for future identification. The activation setting will default to Active. Click the OK button to continue.
The new project will be added to the list in the Project Administration dialog. Click OK. Choose the project from the
Client or Project Name drop-down list.
Editing Projects
To edit a project name or description, click the Edit List button located beside the Client or Project Name option in
the New Case - Properties dialog. The Project Administration dialog will appear. Click the project to be edited and
click the Edit button. Make the desired changes to the Project Name and/or Project Description and click OK.
33
Deleting Projects
To delete a project, click the Edit List button located beside the Client or Project Name option in the New Case -
Properties dialog. Click the project to be deleted and click the Delete Project button. Any LAW cases that were
previously associated with this project name will display as <none>.
34
Working With Cases
Working with Existing Cases

Once cases have been created, the Open Case dialog may be used to launch or search for cases, view and edit case
properties, delete cases from the case list, and utilize the Project/Client View to group cases that are part of the same
project (for example).
Opening Cases
To open a case in LAW, select File > Open Case or click the open folder icon on the main toolbar. This will activate
the Open Case dialog, which displays three tabs: Recent Cases, Active Cases, and All Cases.
Recent Cases: This tab displays the last ten cases that were opened in LAW.
Active Cases: This tab displays all LAW cases that are in an 'Active' state. A case is set as 'Active'
automatically when the case is initially created. To set a case as 'Inactive', click the case name in any tab of the
Open Case dialog and click Properties. The New Case - Properties dialog will appear. Click the 'No' radio
button beside the 'Case is Active' option and click OK. The case will no longer appear in the Active Cases tab
but will be accessible from the Recent Cases and/or All Cases tabs.
All Cases: This tab will display all cases regardless of their state. The All Cases tab includes searching
capabilities, allowing users to search for a case by either the case name or by the creation date. To utilize the
Search feature, first select the desired search method: CaseName or DateCreated. As letters or numbers are
entered into the adjacent box, the cases that correspond to those beginning characters will appear in the list.
35
Cases may also be opened using a command-line parameter with the case name. For example, to open LAW to a
case called LAW Demo Case, modify the shortcut or call the following command: "C:\Program
Files\Law50\Law50.exe" LAW Demo Case.
Note: The path to the exe will require quotes if it contains spaces and is a Windows shortcut or command prompt
launch.
Browsing to a Case
If a user needs to open a case that already exists but is not in the case list, simply browse to it from the case list form.
This ability provides access to cases created by other users (if not sharing a case list with them) or to a case that was
previously deleted or moved. To browse to a case, press the Browse button from the case list form and select the
project database or ini file (project.mdb, project.add, or project.ini) of the desired case. Once completed, the case will
be opened and added to the case list. If the case is already in the current case list, a message will appear stating that
the case is already in the list. If browsing to a case which conflicts with an existing case name, the user will be
prompted to enter a new case name.
Viewing Case Properties

The New Case - Properties dialog box can be displayed by pressing the Properties button from the Open Case
dialog after highlighting the desired case. This allows users to view the database and image paths for a case, case
description, client or project name, and modify them if necessary. This dialog may also be used to set a LAW case to
active or inactive by choosing Yes or No beside the 'Case is Active' option (as mentioned previously in this
topic). Setting a case to the inactive state will result in that case not appearing in the Active Cases tab in the Open
Case dialog.
Deleting a Case
To delete a case from the case list, select the desired case, right-click and select Delete from the pop-up menu (or
select the case and click Delete from List).
Note: Deleting a case from the case list merely removes the reference to the case in the Open Case dialog. It does
not remove any data or image files for that case. If a user needs to work on the case at a later time, simply browse
to the case database to re-add it to the case list.
36
Working With Cases
Creating Index Fields

Index fields are used to store information about the records in a LAW case. The index information for each record is
displayed on the Index display on the main form to the right of the main image window. This information aids in
retrieving records from within LAW and, once exported, within the litigation support applications. Users may add as
many or few index fields as deemed necessary to produce meaningful search results. LAW will support nearly an
unlimited number of user-defined index fields in each case.
When a new case is created, and "Enable Electronic Discovery for this case" is selected from the New Case -
Properties dialog, the index fields necessary for processing electronic discovery will be created automatically.
Creating index fields is one of the first things users typically do after creating a new case. For example, users can
enter folder level index information when scanning images or tag relevant documents when processing EDD. The
Modify Fields form is used to add, delete, and update existing fields. To open this form, select Index > Modify Fields
from the main form. The Modify Fields dialog will appear, displaying all system and user-defined (if any) index fields.
Fields shown in gray are system fields and cannot be deleted or edited. Fields shown in black are user-defined fields.
1. Add Field: Launches Add Field dialog.
2. Delete Field: Deletes a user-defined index field.
3. Save Changes: Saves changes after editing field properties.
4. Apply Template: Applies an existing case template. See Case Templates.
5. Save Template: Saves a case template based on the current LAW case. See Case Templates.
6. Edit List: Launches the List Editor to allow editing of list field values.
7. Field Profiles: Click the arrow to view a list of active profiles, launch the Manage Field Profiles dialog, and
save a new profile. See the Index Profiles topic for more information.
8. Name: Displays names of system and user-defined fields.
37
9. Table: Indicates if a field is contained in the document-level or page-level table of the database.
10. Type: Lists the type of field (see Field Types below).
11. Row Span: Indicates how many rows of data will be visible in the Index display (Memo fields only).
12. Indexed: Indicates if a field is indexed.
13. Locked: Indicates if a field is locked. All system fields will be locked, meaning they cannot be edited.
14. Unique: Indicates if a field is set to unique, meaning values in this field must be unique for each record.
15. Visible: Indicates if the field is visible on the Index display.
16. Field Order: Displays the order of fields in the Index display.
17. Active Profile: Displays the name of the profile currently applied in the Index display.**
18. Save: Saves any changes made to the active field profile.**
19. Save As: Deletes a user-defined Index profile. to be used for storing field order and visibility.**
20. Delete: Deletes the profile currently selected in the Active Profile field. The Default profile cannot be
deleted.**
**See the Index Profiles topic for more information.
Adding a Field
To create a new field, click the Add Field button. The Add Field dialog will appear.
Enter a name for the field. The Table option allows users to select either Document-Level or Page-Level. Document-
level field values will be the same for all pages of a document. Page-level field values will apply to only the selected
page. Select the field type from the list of available types, which are discussed below in the Field Types section.
Users can choose to have an index created for the field by checking the Indexed option. If a field is indexed, the
Unique option may also be selected to ensure that the field will contain no duplicate values. Indexed fields provide
much faster sorts and search results from within LAW, although this has no effect on the final retrieval application.
Because indexed fields take up more space than non-indexed fields and slow down the insertion of new records, be
careful not to overuse indexes within the LAW cases. Unless a field will be queried or sorted frequently or will contain
unique values, no reason exists to add indexes for the fields. The Insert at top of list option will insert the new field at
the top of the Field Order list and also at the top of the Index display on the main form.
38
Working With Cases
Field Types
The following seven field types are available when creating new fields for document-level fields. Page-level fields are
limited to three field types - Numeric, Tag, and Text.
Text: Standard text field, which can contain up to 255 text characters.
Auto-Increment: Same as text field, except it will automatically increment from one document to the next if
no value is specified.
Date: Date field, which requires entry of a valid date format with a 4-digit year (i.e. mm/dd/yyyy).
List: Same as text field, but allows entry of pre-specified values, which appear in a drop-down list for the
field on the index tab. The list values can be modified by selecting the Edit List button once a list field has been
selected from the fields list.
Memo: Field type used for large text field values that exceed 255 characters. The Span Height setting
adjusts the number of rows displayed on the main form. (Note: Memo fields cannot be indexed.)
Numeric: Accepts numeric values between the values of -2147483647 and 2147483648.
Tag (Boolean): This field will have one of two states (Yes/No). "Yes" is represented by a green check mark
in the grid displays. When viewed in the Index display, the field will contain the two values in a drop-down list:
Yes and No. See the Tagging Records section for more information.
LAW reserves many field names. If one of the reserved field names is entered, or any other name that already
exists, the user will not be allowed to proceed with creating the new field. For a complete list of system fields used by
LAW and their descriptions, please see the Field Descriptions topic.
Changing Field Properties

To change the properties of a field once it has been added, select the field from the field list, change the desired
properties (i.e. name, field type, indexed) and select Save Changes. Certain field type conversions may cause a loss
of data. For example, changing from Text to Date will cause all invalid date values to be cleared and changing from
Memo to Text will cause all fields containing over 255 characters to be truncated. Also, a unique index cannot be
added to an existing field if that field does not contain all unique values.
Deleting a Field
To delete an existing field, select the desired field from the field list and click Delete. Deleting a field permanently
removes that field and all data in it from the database. System fields (displayed in gray in the Modify Fields dialog)
cannot be deleted.
Changing the Field Order

The Field Order section of the Modify Fields dialog is used to specify the order in which fields will be displayed in the
Index display on the main form. To add a field to this pane, simply check the 'Visible' box for the desired field; the field
will be added to the bottom of the list. To move a field to a different location, simply click (and hold) the field in the
Field Order pane, drag it to the desired location, and 'drop' the field (release the left mouse button). To move more
than one field simultaneously, use the Ctrl or Shift key to select multiple fields. While holding one of these keys, click
and drag the fields to the new location and release the left mouse button. The fields will be re-ordered on the Index
display after closing the Modify Fields dialog.
The Field Order pane may also be used to hide or show fields. Right-click anywhere within the Field Order pane to
view the three pop-up menu options.
39
Hide Selected Fields: Hides any fields selected in the Field Order pane. Use the Ctrl or Shift keys to select
multiple fields.
Hide All Fields: Hides all fields that are currently displayed in the Field Order pane.
Show All Fields (User-defined): Leaving currently displayed fields intact, this option displays all user-
defined fields in the current LAW case.
Show All Fields: Displays all system and user-defined fields existing in the current case.
40
Working With Cases
Case Templates
The Case Template feature saves the case folder structure and field information (including list field values) for later
application to a new case. This feature can be used to reduce the amount of time required to set up the same fields
or folder structure multiple times.
Saving a Case Template

Two methods exist for accessing the "Save Case Template" feature.
The first method of accessing this feature is to select File > Administration > Save Case Template. Enable the
"Save Folder Structure with Template" option to save the current folder structure and field information of the case. If
"Top level folders (ONLY)" is selected, the template will consist of field information and only the folders located one
level below the root; any folders within these folders will be ignored.
The second method of accessing this feature is via the Modify Fields dialog. Click Index > Modify Fields
and click Save Template. The Save Case Template dialog (pictured above) will appear. Use the instructions above
to save a template.
Case templates are automatically placed in a Templates folder, a subdirectory of the folder containing the LAW
executable. The templates are stored as <Template Name>.XML.
Note: The Admin LAW license is required to save a case template.
Applying a Case Template

Two methods exist for applying a case template. The first method is to apply the case template at the time of case
creation. The second method is to apply a template to an existing case via the Modify Fields dialog or File-
>Administration menu.
New Case
A Case Template field appears on the New Case - Properties form. This Case Template field allows users to select a
previously created template to create index fields and possibly a folder structure within the new case. The drop-down
will display all templates contained within the Templates folder (see above).
41
Existing Case
Templates may also be applied to an existing case using the feature under File > Administration > Apply Case
Template. The Select Case Template dialog will appear and prompt the user to select a template. Choose the
desired XML file and click Open.
42
Working With Cases
A prompt will appear, listing the fields that will be added to the case. Any field names that are duplicates of existing
fields will be ignored.
Select Yes to proceed. The index fields and folder structure (if any) stored in the template will be applied to the case
in addition to any already existing fields and folders.
An alternate method of applying a case template exists in the Modify Fields dialog. Click Index > Modify Fields and
click the Apply Template button. Follow the instructions above to apply the template.
Note: The EDD lookup fields (Custodian, EDFolder, EDSource, and EDSession) will not be created when applying
a case template even if they exist in the template. These fields will only exist as lookup fields in ED-enabled cases
and should not be saved to case templates.
43
Populating List Items

The List Editor allows users to add and remove list items from index fields that are set up as 'List' type fields.
To launch the List Editor, select Index > Modify Fields from the main form. Highlight a list field and click the Edit List
button. The Edit List button is only enabled for fields defined as 'List' types. The name of the field being edited is
listed just below the title bar.
Adding List Items

To add an entry, type the value into the 'Current Item' text box and click Add. The item will be added to the list,
unless it already exists. The Add button is disabled if the current item matches the selected item or is blank.
List items may also be added automatically when coding documents from the main form. To utilize this
feature, enable the 'Add all new list field values to list on update' option located on the Preferences tab of the Tools >
Options form. If this option is enabled and a value is typed directly into a list field on the Index display, the value will
be added to the list after clicking Update (if it is not already in the list).
Deleting List Items

To remove a list item, select the desired item from the List Items pane and click Delete. The selected item will be
removed from the current list.
Renaming List Items

To rename an existing list item, select the desired item from the list, enter the new name in the Current Item text box,
and then click the Update button. This action updates the name of the current item provided the new name does not
already exist in the list.
44
Working With Cases
Importing and Exporting List Values

List items may be reused by exporting to and importing from list files. A list file is simply a text file (with an "LST"
extension) that contains list items (without quotes) separated by hard returns. These list files can be created by
exporting from LAW's List Editor or created manually with any text editor, eliminating the need to re-enter list items for
common fields by allowing users to share list items between cases. The Import function is used to import existing
entries from a list file, while the Export function is used to save the current items to a list file for future use.
45
Index Profiles
Depending on the type of project (i.e., scanned documents vs. electronic discovery) or the type of process currently
being performed or QC'd, certain fields may be needed for reviewing or coding more often than others. For example,
if documents are being scanned and five fields must be coded at scan time, then perhaps only those five fields should
be displayed in the Index display to avoid confusion.
Field profiles can be used to easily switch between sets of fields in the Index panel. The profiles will store a list of
visible fields and the order of those fields in an .ifp file. A "Default" profile is a user-level profile included by default in
each LAW case. Changes may be made to the Default profile in a case, but the changes will not persist to the Default
in other existing or new cases. In e-discovery-enabled cases, a number of popular EDD-related fields are displayed in
the Index view automatically when the Default profile is selected. In non-EDD cases, no fields are displayed by
default.
Creating Index Profiles

To save a field profile, click Index > Modify Fields, make the desired fields visible, and organize them as needed in
the Field Order area. Next, click the Save As button at the bottom of the dialog or click the arrow beside the Field
Profiles button and choose Save As.
46
Working With Cases
Three storage levels are available when creating field profiles:
User - Available to the current user in the current case.

Shared - Available to any user in the LAW case in which the profile was created. If a profile is shared, LAW
will automatically display "(Shared)" after the profile name.
Global - Available to any user in any LAW case. If a profile is global, LAW will automatically display
"(Global)" after the profile name.
After the storage level has been selected, enter a name for the profile. The name must be a valid file name, as the .ifp
profile storage file will be named according to the value entered in this dialog. Click Accept to save the changes.
The user and shared profiles are stored in the case folder structure ($UserData), while global profiles are stored in
<application path>\Shared. The default storage location for global profiles can be changed via the Preferences tab in
Tools > Options.
Click the Browse button beside the Path for global field profiles, grid views, and filters option to select a new
storage location. Any previously created global queries and profiles will need to be manually moved from the
LAW50\Shared folder into this specified location to be detected as a global query or profile by LAW. Changing this
path will affect saved global queries, global index field profiles, and global grid profiles.
Note: Versions 5.3.08 and below used a different storage scheme for index profiles. All profiles were stored in a
single INI file. When 5.3.14 or later is installed and a case is opened, the profiles will be copied from this
47
indexprof.ini file and updated to match the new storage schema. The previous "Default" profile will be named
"Default_Shared" to avoid conflict with the new Default profile in the current case.
New profiles can also be created by launching the Manage Profiles dialog, available by clicking the arrow beside the
Field Profiles button in the Modify Fields dialog. Profiles can be created, applied, and deleted from this dialog.
Applying and Modifying Index Profiles

Once created, profiles can be selected from the Active Profile drop-down in the Modify Fields dialog or from the
Profile drop-down in the Index panel on the main form.
48
Working With Cases
To modify an existing profile, open the Modify Fields dialog and make the desired changes to the visible fields and/or
field order, then click the Save button. If the Save button is not clicked, LAW will prompt to save changes prior to
closing the dialog.
Deleting Index Profiles

To delete a profile, click Index > Modify Fields, select the profile to be deleted in the Active Profile drop-down, and
then click the Delete button. A confirmation prompt will appear to confirm the user wishes to delete that particular
profile. Choose Yes to proceed with the deletion.
Profiles can also be deleted by clicking the arrow beside the Field Profiles button and choosing Manage Profiles.
Once the dialog appears, select the profile to be deleted from the Field Profiles list and choose Edit > Delete or right-
click and choose Delete.
49
Establishing Folder Structures

Creating a folder structure in LAW will allow better organization of documents and the ability to mimic the structure of
the original documents. This helps scanner operators find their place in the case more easily and aids in finding and
correcting scan errors. The folder structure is also useful for EDD projects, allowing organization by media type or
custodian, for example. LAW provides a set of pre-defined folder suffixes to quickly create a folder structure,
but users are free to customize the folder names as needed. When naming folders, one important item to note is that
the folder structure generally determines the order of processing, i.e. folders are processed in alphabetical order.
Creating Folders
To create a new folder, select Folder > New from the main menu. The New Folder dialog will appear. The folder
"Number" and "Type" are combined to form the actual folder name. If the user wishes to customize the folder name,
simply edit the "Folder Name" text box directly.
Note: Selecting a folder type will reset the folder name to the contents of the folder number and type.
Click OK to create the folder. The new folder will be created as a subfolder of the currently selected folder. To create
a new folder on the same level as the current folder, select the parent of that folder prior to adding the new folder.
Auto-Creating Folders
LAW also provides a quick and easy method for creating a series of folders. The Auto-Create feature automatically
creates the next logical folder on the same level as the current folder. For example, if currently in
"C:\Case1\0001Box\0001Fldr" and Auto-Create is selected, LAW creates "C:\Case1\0001Box\0002Fldr" and makes
that the current folder. This feature can be activated by selecting Folder > Auto-Create from the main menu (or by
right-clicking the desired folder and selecting Auto-Create). If the next logical folder already exists, LAW will simply
jump to that folder and make it the current folder. The next folder is created on the same level as the current
one. Folders cannot be auto-created while the root image folder is selected, as this would create a folder outside of
the root case folder.
Selecting Folder > Auto-Create N Folders serves the same function as Auto-Create but allows users to select 1 to
999 folders to be automatically created based on the current folder.
Viewing Folder Contents

Folder contents can be displayed in the document list (lower right pane in the main interface) by clicking on a folder in
the tree view left of the document list. To expand a folder containing subfolders by one level, click the plus sign to the
left of the folder name. To collapse, click the minus sign. To expand a folder and all subfolders below the selected
folder, choose Folder > Expand. To collapse all folders below the selected folder, choose Folder > Collapse.
The files referenced in the document list are not necessarily physically stored in the folders shown in the folder tree.
Displaying the records in this manner will allow the desired representation of folders and records to be maintained.
For example, folders created via TIFF conversion in LAW are stored in <case root>\$Image Archive; however, the
records will appear in the document list when clicking on the original folder structure created by the ED Loader during
50
Working With Cases
import. See the topic related to the type of function being performed in order to see how the associated files are
stored.
Deleting Folders
To delete a folder, select the desired folder and select Delete from the Folder menu. To prevent accidental deletion
of an entire folder tree, all subfolders of that folder must first be deleted. Similarly, the root case folder cannot be
deleted from within LAW.
Renaming Folders
To rename a folder, select the folder to be renamed and then select Rename from the Folder menu. The folder name
must not contain any characters that the operating system cannot support (i.e. ? / \). The root case folder cannot be
renamed. When a folder is renamed, the path for all documents in and below that folder must be updated to reflect
the name change. This process can take some time if the folder is near the top of the case, depending on the number
of documents affected by the name change. The renaming of a folder may actually cause an error and fail if too many
documents are affected (usually over 10,000). If this error occurs (due to excessive file locks), a setting in the registry
can be adjusted to allow the renaming of the folder to proceed. Contact LexisNexis for specific details if this occurs.
Moving Folders
Any folder below the root displayed in the tree in the main user interface can be moved from one location to another
within a LAW case. All subfolders and records contained in the folder will be moved to the new location as well. To
move a folder, click on the folder to be moved in the main interface folder tree and click Folder > Move, or right-click
the folder and choose Move. The Move Folder dialog will appear.
This screen will display the same folder structure as the tree in the main interface. Select the folder into which the
folder should be moved or first click the New Folder button to create a new folder in the case. In the example above,
the user would like to put the 005Source folder at the same level as 001Source, 002Source, 003Source, and
51
004Source. To do this, the user would select 43695_MoveFolders01 as the destination folder. Once the destination
folder has been chosen, click Accept. The folder will be moved to the designated location. This process may take
longer to complete for folders containing a large number of documents.
Folder Properties
LAW provides a means to get a quick summary of a folder that includes the actual location, size, and number of files
and subfolders within it. The size and number of files displayed will include all files in and below the current folder. To
view the folder properties for a specific folder, click the desired folder and select Properties from the Folder menu.
Summarize Images
LAW provides a quick summary of the images contained within a folder and subfolders (recursively). The image
summary displays a report of the number of documents and pages contained within the selected folder. LAW also
calculates the "Total Area" of the documents contained within the folder. The total area information can be very useful
for billing purposes.
As noted in the message box (ED-enabled cases only), electronic files and their printed images are skipped during
this image summary process. The number of skipped records will be listed in the summary output, in addition the
number of scanned images.
Note: To calculate the square footage of the documents, LAW must open and read each image individually, which
takes an additional amount of time. For a faster document or page count, use the Query Builder or Grid View to
create a query on the selected folder. Then, select Tools > Summary to view the document and page totals.
Another option is to utilize the Case Summary feature by clicking File > Administration > Case Summary. This
feature allows the selection of a date range prior to summarizing the data and also provides the number of pages
flagged for OCR and the number of pages that were completed (OCR process complete).
52
Importing Electronic Discovery
Importing Electronic Discovery

LAW PreDiscovery allows users to acquire documents through importing of electronic discovery, importing images,
and scanning. Using LAW's Electronic Discovery Loader, electronic documents may be imported, along with any
extracted text and metadata. Once imported into LAW, users have the ability to perform searches and filters to cull
down documents for production, convert to tiff, print to paper, produce native files, and produce tiff files. The steps
chosen after loading the documents will depend on the project specifications.
Launching the ED Loader

Electronic documents are imported into LAW via the Electronic Discovery Loader, or ED Loader. To launch the ED
Loader, select File > Import > Electronic Discovery.
53
Session Configuration
The Sources tab of the Electronic Discovery Loader includes four settings that should be configured prior to each ED
Loader session. These options may be set either before or after selecting the sources to be loaded into the LAW
case. The 'Default Target Folder' and 'Default Custodian' settings will apply to all sources unless further configuration
is performed at the source level (see Source Queue).
Default Target Folder

The location of imported electronic discovery documents will be based on the specified target folder. When the ED
Loader is launched in a LAW case, this field will be populated with the currently selected folder (the root case folder is
displayed as "<Case Root>). This value may be changed by either typing in an existing folder path or new folder path
(relative to the root case folder) or by clicking the button beside this setting to launch the Select Target Folder dialog.
In this dialog, users may create a new folder or select an existing folder for the imported documents. If typing a target
folder value directly into the 'Default target folder' text box, and that folder does not currently exist in the case, LAW
will create it prior to import.
Session Label
The Session Label allows users to assign a unique identifier to each ED Loader session for a LAW case. This label
may be useful for filtering specific sessions or researching session logs. By default, the session label will contain the
date and time that the session was initialized. To customize the label, click the button beside this option to launch the
Session Label Editor. The Session Label Editor dialog provides a list of variables selected by double-clicking each
item and also allows users to type any additional data into the Session Label pane.
Default Custodian
Users may assign custodians to one or more sources prior to importing the electronic documents. The same
custodian may be applied to all sources by entering the custodian value into the 'Default custodian' field. Different
custodians may be assigned to each source by entering the various custodian values into the Custodian field in the
Source Queue (see Adding/Removing Sources). To specify a value in the Default Custodian field, either type the
value directly into the field provided on the Sources tab or click the button beside this option to launch the Custodian
Manager.
54
Acquiring Documents
The Custodian Manager dialog allows users to enter one or more custodians, similar to adding list items for list type
fields in LAW (see Populating List Items). Type a value into the Current text box and then click Add to add a
custodian. Repeat these steps to enter multiple custodians. A list of custodians may be imported by clicking the
Import button and browsing to a list file. A list file is simply a text file (with an "LST" extension) that contains the
custodian names (without quotes) separated by hard returns. Click Export from the Custodian Manager to create a
list file containing any currently existing custodian values.
DocID Seed
The DocID is a unique identifier assigned to each document imported into LAW via the ED Loader. Enter the starting
value in the 'DocID Seed' field; the number will increment by one for each record. To ensure the DocID is unique to
each record when loading from multiple workstations, users should force each workstation to use unique numbering
schemes (i.e. PC1_000001, PC2_000001, etc.). The DocID value's length must not exceed 50 characters.
55
Adding/Removing Sources
Folders and files selected for import via the ED Loader are referred to as "sources." The Sources tab of the ED
Loader will be used to add these sources to the 'Source Queue', which is located just below the session configuration
options. Documents may be added to the Source Queue by selecting individual files, folders, mail stores, Outlook
folders, and/or file lists. These different types of sources may be processed in a single ED Loader session.
Adding Sources
The Add section in the ED Loader (Sources tab) will be used to add one or more sources to the queue for processing.
Buttons are available for choosing any of the five different types of sources.
Mail Store - Click this button to add mail store sources. LAW currently supports Outlook (*.PST) mail stores
as well as Lotus Notes (*.NSF) mail stores. When the Select Mail Store dialog appears, simply browse to the
mail store(s) and click <Open>. The store(s) will be added to the Source Queue.
Outlook Fldr. - Click this button to select one or more Outlook folders for import. The mail store(s)
containing the folders to be processed must be opened in Outlook prior to using this option. When the Select
Outlook Folder(s) dialog appears, check the box or boxes next to the folder(s) to be processed. Check the
'Recurse Subfolders' option to ensure the subfolders of selected folders are processed as well. The items in
parentheses beside each folder represent the number of items in the folder (first number) and the number of
unread messages (second number). Click Accept to add the selected folder(s) to the queue.
Folder(s) - Click this button to launch the Select Folder(s) dialog. Check the box or boxes next to the
folder(s) to be processed. Check the "Recurse Subfolders" option to ensure the subfolders of selected folders
are processed. The 'Scan selection(s) for mailstores' option, when enabled, will search any selected folders for
supported mail stores. If any stores are found, they will be listed separately in the queue and processed as mail
stores. If this option is disabled, and mail stores are contained in the selected folders, they will either be
processed as e-docs or excluded completely depending on the state of the 'Exclude mailstores from e-doc
processing' option located on the Settings tab. See the Exclusions topic for more information.
File(s) - Click this button to launch the Select File(s) dialog. This screen is similar to the Select Folder(s)
dialog but will be used to select one or more files from a folder versus selecting entire folders. The Ctrl and Shift
keys may be used to select multiple files and Ctrl+A may be used to select all files in a folder.
File List - Click this button to launch the Select File List dialog. Browse to the file containing the file paths
and click Open to add the source to the queue. The file list should be a text file (file extension does not
matter) containing full paths to the files, separated by hard returns, and without quotes. If the file contains
relative paths, the file list must be placed in a location that will allow the ED Loader to complete the path. For
example, if the file list contains a listing of EDOCS\0001.xls, then the file list should be placed one level above
the EDOCS folder.
56
Acquiring Documents
Drag and Drop Method

Another method of adding sources is to drag and drop items directly into the Source Queue. Folders, individual files,
and mail stores may all be added using this method by simply browsing to the sources through the operating system
(i.e., using Windows Explorer), highlighting the desired folders and/or files, then clicking and dragging the items into
the queue.
There are two options that apply to drag and drop that should be considered prior to adding the sources, both located
in the General category on the Settings tab (see the General section). First, to ensure subfolders of the selected
folders are processed, ensure the "Automatically set E-Doc folder sources to Recurse when I add them via drag and
drop" option is enabled. The second option is to 'Scan folder selections for supported mail stores when added to the
queue' and will force the ED Loader to scan all folder selections for Outlook and Lotus Notes mail stores. If found, the
files will be processed as mail stores rather than e-docs. This option has two sub-options. 'Scan supported archives'
will result in archives (i.e., zip or rar) being scanned for mail stores as well. 'Add selected folder to queue when mail
store scan is active' will result in the folder(s) containing mail store(s) being added to the queue in addition to any mail
stores found. For example, if a folder is selected that contains 5 XLS files and 1 PST mail store, enabling this option
will result in two sources being added to the queue: one file set (5 XLS files) and one mail store (PST file).
Removing Sources
Sources can be removed from the queue using the Remove options.
Remove Item - Used to remove one source at a time. Click the source in the queue that needs to be
removed and click Remove Item to remove it.
Clear All - Used to remove all sources from the queue.
Viewing Sources
To review information about each source selected for processing, click the View Details button located between the
Add and Remove sections on the Sources tab. You can also select Source Details from the View menu. If the
source consists of a file set or file list, all filenames will be displayed.
Long Paths
When sources are selected with paths greater than 260 characters in length (the Windows limit), the ED Loader will
first copy the files to a temporary location to allow successful processing of the files. A warning will be logged in the
Session Viewer logs when this occurs.
57
Source Queue
The Source Queue is located on the Sources tab in the Electronic Discovery Loader and will display all sources
added by the user for the current session. Sources are grouped by type for organizational purposes, allowing users to
easily locate an item to be removed from the queue (for example). Outlook mail stores will be grouped together, Lotus
Notes mail stores will be grouped together, and so on. The Source Queue may also be used to edit information at a
source level.
Editing Source-level Settings

Once sources have been added to the queue, certain items may be edited at the source level versus using the
default session configuration settings. Three settings are listed below:
Source Name - When the option to 'Use source name as top level folder' is enabled in the Output settings
(see Output section), the name listed in this field will be used as the top level folder name, and the documents
will be imported into a structure below it. The source name may be edited by simply typing the desired name
directly into the text box. When a source name is changed, the new name will appear in green.
Note: Source names may appear in green by default if the option to "Ensure source names are unique
when they are added to the queue" is enabled and duplicate source names are detected. The duplicate
source name will be appended with a '-001'.
Custodian - The custodian may be edited at a source level by either choosing a different value from the
drop-down list in the Custodian field (if any exist) or by typing the new custodian value directly into the field.
When a custodian value is changed at a source level, the new value will appear in green. If the custodian
should be the same for all sources, simply enter or select a custodian in the 'Default custodian' field which
is located above the Source Queue in the session configuration settings.
Target Folder - The selected sources will be imported into the designated LAW folder. If all sources should
be imported below the same target folder, simply select the folder in the 'Default target folder' text box located
above the Source Queue in the session configuration settings. To change the target folder for a particular
source, click within the Target Folder text box for the source and either type a new folder or folder path or click
the box within the field to launch the Select Target Folder dialog. This dialog may be used to choose an existing
folder for the target location or to create a new folder.
58
Acquiring Documents
Resetting Source-level Settings

The Reset buttons, located below the Source Queue, are used to undo changes made to the source-level settings.
You can also select these options from the Edit menu.
Reset All - Resets the Custodian, Source Name, and Target Folder fields back to the defaults.
Reset Names - Resets the Source Name field back to the default.
Reset Cstdns. - Resets the Custodian field back to the default.
Reset Folders - Resets the Target Folder field back to the default.
Viewing Source Paths

Select Show source paths to display the path to each source in the queue. This is displayed next to the Target
Folder column. You can also enable this option from the View menu. For File Sets, the total file count is displayed
after the path in the Source Path column. For File Lists, the path (including filename) of the file list will be displayed.
For Folders, if "Recurse Subfolders" is selected to include subfolders, a plus sign <+> is displayed at the end of the
source path.
59
File Type Summary

The File Type Summary in the ED Loader may be used to generate a summary of the selected source files prior to
processing. The summary will process and log e-docs, archive contents, and e-mail attachments. It does not expand
loose e-mails or compound documents.
The summary will include items such as total file counts, counts based on file type (i.e. Microsoft Word documents),
total size, and size of files per file type. This feature may also be used to generate a report containing the
aforementioned information.
To perform a preprocess summary, add items to the ED Loader Source Queue and then click Tools > Summarize
Queue. The File Type Summary Progress dialog will appear as the items are summarized. This dialog will display the
name of the source being processed, as well as both source-level counts and total counts of items inventoried,
discovered, and items that received warnings.
Next, the File Type Summary dialog will appear displaying the results.
60
Acquiring Documents
Four tabs exist in the File Type Summary:
All - Displays a listing of files found in the queue, organized by file extension. E-docs, archives,
archive contents, loose e-mail messages, and e-mail attachments from mail stores will be included in the
summary. Loose e-mail and compound documents are not expanded in the summary, so the
attachments/embedded files from these types of files will not be included. E-mail messages from mail stores
are also not included in the summary, but the number of e-mails can be viewed using the reporting feature
(explained below).
E-Docs - Displays a listing of e-docs only. This tab will include loose e-docs, archives (i.e. zip files), and
archive contents. Compound documents are not expanded so files embedded within the parent documents will
not be included in the summary or reports.
E-mail Att. - Displays a listing of e-mail attachments found in mail stores. Loose e-mail items are not
expanded so their attachments will not appear in the summary or reports.
Identified - This tab will only be populated once the optional identification process has been executed,
allowing users to view the true file types of the items contained in the queue. Note: This process is only
available for items listed in the E-Docs tab.
Viewing File Groups

Files listed for each extension group may be viewed by clicking the Files button or View > Files. This view will list
each file in the group, the total size of the group, each individual file size, and any warnings that may have occurred
during the summary or file identification process. If a file is an e-doc, it may be launched using the Open button. The
Prev Set and Next Set buttons may be used to navigate through the groups.
61
Identifying File Types

The file identification process may be optionally used to validate the files included in the summary. The file engine will
determine the true file type based on the header of each file. Click the Identify Files button or Tools > Identify Files
to initialize this process. The Identified tab will display the results of this process and is linked to the file type manager
database, which allows users to set the Include/Exclude flags directly from this view. File identification automatically
takes place when sources are loaded into LAW via ED Loader, so running this process prior to loading will provide
users with a preview of the file types as they will be displayed in LAW.
Saving and Reloading ED Loader Summaries

Summaries can be saved from the File Type Summary dialog by clicking File > Save As or by clicking the Save
As button. Saved summary databases will be saved as .EDSD files in the location selected by the user. To reload the
summary, launch the ED Loader, select File > Open Summary and browse to the saved .EDSD file. The File Type
Summary dialog will appear displaying the results of the saved summary. To add the sources to the ED Loader
Source Queue, click Tools > Enqueue from the File Type Summary dialog. The sources will be loaded into the
Source Queue and are ready for import into LAW.
Generating Reports
To generate a report based on the contents of the summary, click Tools > Reports from the File Type Summary
dialog once a summary has been performed. The View Report dialog will appear.
A logo may be applied to the report by enabling the Apply logo to report option and then browsing to the desired
image file. Click the View Report button to generate the report. Once generated, the report may be printed or saved
in a number of available file formats using the File > Save As menu item.
62
Acquiring Documents
Archives
To access the LAW Electronic Discovery Loader, select File > Import > Electronic Discovery from the main menu.
Click the Settings tab and click Archives to reach the list of available options.
LAW currently supports the extraction from the following types: ZIP, RAR, JAR, GZIP, Z, and TAR. The Archive
settings apply to these types of files.
Enable Archive Extraction - When selected, LAW will extract contents of the supported archive file types (see
above list).
Treat archive items as attachments - Imports the archive file as a parent document and the contents are grouped
as attachments to the parent document. When an archive file is an attachment to an e-mail, the e-mail will be the
parent record and the contents of the archive will be attached to the e-mail (no record created for the zip). The
Filename field will reference the archive filename for the attachments that were contained within the archive, provided
the 'Use nested filename for items extracted from archives' option is selected (see below).
Include archive source file (copy full archive into LAW) - This option allows users to choose whether or not to
copy the native archive file into the typical native file structure in the LAW case. Users may choose not to copy the file
to save space and the file is often not needed once the contents are extracted.
Use nested filename for items extracted from archives - The archive filename will precede the filename of each
extracted item in the Filename field, as follows: archive.zip?filename.doc
63
Compound Documents
Click the Settings tab and click Compound Documents to reach the list of available options.
If the "Enable Compound Document Extraction" box is checked, the file containing the embedded file(s) will import as
a parent document and the embedded file(s) will be listed as an attachment or attachments.
Note: Not all embedded files are supported. If an embedded file is suspected, but could not be opened, a warning
will be generated and logged in the Session Viewer and ErrorMsg field.
Types currently supported for extraction from compound documents:
Word/RTF
Excel
PowerPoint
PDF
SnapShot
Visio
Outlook.FileAttach (Word-authored e-mail with inline attachments, generally stored in RTF)
Project
Package*
*A Package is a general type of embed; it can be a text file or a zip file, for example. Any of the above types may also
be embedded as a package type depending on the software installed when a user embeds the file. For example, if a
user were to embed an Excel spreadsheet into a Word document, and Excel is not installed, the spreadsheet will be
embedded as Package.
Supported compound document containers:
Description Detection Extraction
Non-MS Office Formats
Adobe Acrobat (pdf) Y Y
Rich text format (rtf) *Converted to Word format for extraction. Original file Y Y
is preserved.
Office 2007
64
Acquiring Documents
Excel Spreadsheet (OpenXml) Y Y
MS Office Data File (OpenXml) Y Y
PowerPoint Presentation (OpenXml) Y Y
Word (OpenXml) Y Y
Office 2003
Word Y Y
Word (xml) Y N
Excel Y Y
Excel (xml) *Compound documents not supported in this format *N *N
PowerPoint Y Y
Publisher **Y Y
Project Y Y
Project (xml) *Compound documents not supported in this format *N *N
Visio N N
Visio (xml) *Currently not recognized by file engine *Y N
OneNote N N
Office 2002/XP, Office 2000
Word Y Y
Excel Y Y
PowerPoint **Y N
Publisher Y Y
Project Y Y
Visio N N
Office 97, Office 95
Word Y Y
Excel Y Y
PowerPoint Y Y
Project Y Y
**Detection of embeds in these types is limited only to the types of files supported for extraction (see above list).
65
Deduplication
A duplicate file is an exact replica of another file. This is often apparent in electronic discovery sets containing
multiple mail stores from individuals receiving the same e-mail or when electronic files have been created and saved
in multiple locations. Duplicate files are determined by hashing either the entire file (e-docs) or key metadata fields (e-
mails). The scope of the project will determine whether or not deduplication will be performed and which methods will
be used.
In LAW, records can be deduplicated against other records in the case and incoming records during the electronic
discovery import process (covered in this topic), after the import against other records in the case (Deduplication
Utility in LAW), or after the import against other records in the case and other LAW cases (external Inter-Case
Deduplication utility).
Click the Settings tab and then click Deduplication to reach the list of available deduplication options.
Enable Duplicate Detection: Enables duplicate checking for the current session.
Working digest: The working digest is the method of hashing that will be conducted to determine duplicates. A hash
value can be thought of as the DNA of a file. The hash values are obtained through metadata fields (e-mail) or by
hashing the entire file (e-docs). LAW uses two types of hashing methods:
MD5: 128-bit output

SHA-1: 160-bit output
Test for duplicate against (Scope): This option identifies the scope for deduplication. During the import process,
deduplication can be performed at one of two levels:
66
Acquiring Documents
Case Level (Globally): Deduplicates documents against the entire incoming collection and against existing
records in the LAW case.
Custodian Level: Deduplicates documents against records with identical custodian values.
If record is considered a duplicate then (Action): This setting determines the action to take once a duplicate is
located. Three options are available:
Include: Creates a record for the duplicate in the database and copies the native file into the case folder.
Partially exclude: Creates a record in the database but does not copy the native file.
Exclude: Does not create a record, no text is extracted, and the native file is not copied to the case folder.
Include attachment hashes in e-mail metadata hash: When enabled, the ED Loader will include the hashes of
attached files in the parent e-mail's metadata hash. When disabled, the Attach field is incorporated in with the
metadata hash which only contains the file names of attached files.
Warning: While enabling this setting is recommended, it is not advisable to change this setting during the course of
a case as it will alter the e-mail hashing schema, as noted in the interface. The desired state of this setting should
be determined prior to the first import into new cases and should not be changed. This setting was not available in
versions prior to 5.5.07.
If the current case has already been deduplicated via the Inter-Case Deduplication utility, a warning will appear (see
below) when starting the ED Loader import if deduplication is enabled.
Warning: As indicated in the warning message, use of the ED Loader deduplication on imported records after the
case has already been deduplicated against other cases using the Inter-Case Deduplication utility is not
recommended. Doing so will present a mixture of internal and external duplicates and could cause problems when
purging, filtering, or reviewing duplicate records. Click the Cancel button to close this warning and return to the ED
Loader settings.
Proceeding with the ED Loader deduplication after clicking the "Yes I understand and wish to continue" button will
result in the external deduplication database being placed in Rebuild/Flush mode. At this point, the current case
should be removed from the external database. Also, before running the internal deduplication, it is recommended
that the Deduplication Status Reset command (see "Tools Tab" section below) is executed to clear the values
assigned by the Inter-Case Deduplication utility to prevent the mixture of internal and external duplicates. For more
information, see the Inter-Case Deduplication topic.
Deduplication may also be performed after the ED Loader import using the Deduplication Utility in LAW or the
external Inter-Case Deduplication utility. Additional information regarding deduplication can be found in
the Deduplication Information topic in the Appendix.
67
E-Mail
Click the Settings tab and click E-Mail to reach the list of available options.
The E-Mail settings identify how e-mails are sorted when loaded into LAW, the format in which they are saved, and
the format of the date field values.
Sort Key - When loading e-mails from mail stores, it is important to identify how the files are imported into LAW and
later produced. Four fields can be used to sort the e-mails during extraction: From, Received, Sent On, and Subject.
For example, if Received is chosen, e-mails are imported by the date the e-mail was received.
Sort Direction - The direction of the sort may be Ascending (oldest to newest) or Descending (newest to oldest).
Save Outlook messages as - Select the output format of Outlook messages as they are imported with the ED
Loader. The four options are:
HTML - Messages are saved to HTML files with the exception of messages containing embedded OLE
items that cannot be rendered in HTML, such as an Excel worksheet. These embedded images and non-mail
items such as calendars, contacts, and tasks, are saved as native Outlook files (*.msg). Embedded images in
HTML messages are saved in the same folder as the converted message. These images are not LAW records.
Instead they are linked to the HTML file for proper rendering. They are listed in a dependency file (*.dep) with
the same root name as the native file. During Export, linked images are exported along with the native file so
the HTML file can be properly rendered with associated images.
HTML/MHTML (based on format) - The format of the output file is determined based on the format of the e-
mail message. Messages formatted as RTF, non-mail items, or HTML messages, including HTML with linked
images, are saved as MHTML. All other messages are saved as HTML.
68
Acquiring Documents
HTML/RTF (based on format) - The format of the output file is determined based on the format of the e-mail
message. Messages formatted as RTF and non-mail items are saved as RTF. Text or HTML messages are
saved as HTML. RTF messages are saved directly from Outlook, so the GMT date option is not applied to the
display of the converted file.
Warning: Messages saved as RTF will not contain the BCC information in the RTF output. This is a
function of Outlook and how it renders messages to RTF. The BCC field, if present, will however still be
captured in the database and in the extracted text.
Note: Subtle formatting differences may exist between HTML and RTF messages. However, this is the
preferred setting if native rendering (MSG) is not required due to the potential of lost images or
embedded objects when saving an RTF-formatted message as HTML.
MSG - Messages are saved as native Outlook files (*.msg) with the exception of e-mails that contain
extremely large recipient lists (typically over 5,000). These messages can cause Outlook and the ED Loader to
hang. Messages that cannot be saved as MSG files are saved as HTML files.
MHTML - All items are saved as MHTML files (*.mht). MHTML files are web archives that allow the
embedding of images directly in an HTML file. This eliminates the need for any linked images or dependent
files. Similar to the HTML/RTF setting, e-mails are converted to HTML or RTF based on their original format,
and then converted to MHTML files.
Note: RTF messages and items use Microsoft Word to convert RTF to MHTML. If Word is not installed,
any RTF output remains as RTF during the import. Due to the secondary conversion from RTF to
MHTML using Word, processing speed is significantly slower when using this setting. Print speeds are
also significantly slower with MHTML files. Use this setting only if it is absolutely necessary.
Translate date fields to universal time (GMT) - When opening a mail store, the date and time stamps take on local
properties. If e-mails were generated in Eastern Standard Time but processed in the Pacific time zone, the time
stamp will be the Pacific time zone's date and time. For this reason, users have the option to translate all date/time
fields to the universal time zone, Greenwich Mean Time (GMT). Selecting the "Translate date fields to universal time
(GMT)" is a decision to be made based on project specifications.
Preserve X.400 addresses - When enabled, this setting instructs the ED Loader to maintain the X.400 e-mail
address (if available) in the To, CC, and BCC fields and not convert it to the SMTP address.
Outlook Folder Types - Allows the loading of non-mail folder types such as calendar items and contacts when
processing Outlook folders or mail stores.
Log warning messages for e-mails containing RTF body content - This option logs a warning message when
RTF is found in the email body since you can lose formatting or data when converting RTF to HTML.
69
Exclusions
Click the Settings tab and click Exclusions to reach the list of available options.
The Exclusions settings are conditional settings that can be used to prevent certain types of records from being
loaded to LAW.
Exclude mail stores from e-doc processing (Mail store as e-doc) - This option prevents mail stores from being
processed as e-docs. For example, if a PST is contained in a folder selected for processing, the mail store would be
recorded as a single e-doc record when this option is disabled. The mail store will still be processed as a mail store if
it is added to the Source Queue using the Add > Mail Store option or the "Scan folder selections for supported mail
stores when added to the queue" feature.
Exclude empty files (0 bytes) from processing (0 byte file) - Any native files that are empty (0 byte file size) will
not be copied or written to the database.
70
Acquiring Documents
File Types
Click the Settings tab and click File Types to reach the list of available options.
Essentially, LAW supports the import of all file types. Even if a file type is not supported for printing or
conversion, metadata and text may still be extracted. Once a file is imported in LAW, and the native file application
exists on the machine, then it can be opened and processed to tiff or paper (if applicable) individually or in a batch.
Files that could not be converted to tiff can still be exported and delivered in native file format. Provided the reviewer
has the native file application, the file can be opened and reviewed. For this reason, loading all file types into LAW
is recommended. However, it is understandable that users may not wish to import certain file types, such as common
system files. The File Types settings allow users to identify specific files for processing.
Enable File Filtering - If this option is disabled, all files will be imported into LAW. If enabled, the files imported will
depend on the selected scope.
Active List (Scope) - Identifies which list will be used to determine the files that will be imported into LAW. Users
may choose from two lists: Include and Exclude. If the Include list is chosen, file types marked as Include in the File
Type Manager's Include list will be imported into LAW; files that are not checked in the Include list will be excluded.
If the Exclude list is selected, files marked as Exclude in the Exclude list will be excluded and not imported into LAW;
files that are not marked as Exclude in the Exclude list will be imported. The lists are independent of each other. If the
Include list is selected as the active list, or scope, the Exclude list is not considered during the import and vice versa.
If filetype is not included then (Action) - Determines which action is taken for excluded file types. Options are:
Include - This option will copy the native file and log a record in the database.
Partially Exclude - This option will not copy the native file but will log a record in the database.
Exclude - This option will not copy the native file or log a record in the database.
File type manager - The File Type Manager displays the Include and Exclude lists and offers several options for
managing file types. Click Edit to open the file type manager.
71
Files marked as "Include" will be imported if the active list is set to the Include list. If Exclude is set as the active list,
then anything not marked as "Exclude" will be imported.
Multiple file type databases can be created. This feature can be useful when establishing procedures on specific files
to exclude from processing. The File menu in the File Type Manager is used to create new file type databases, open
existing databases, and save changes to the current database.
Other items that may be edited in the File Type Manager are the default source applications for each file type and the
flag to determine if text should be extracted from each file type.
Auto Assign Suspect Extensions - LAW automatically validates files to ensure the extension assigned to the file
properly reflects the actual file type. With "Auto Assign Suspect Extensions" enabled, if the extension of the incoming
file does not match any extensions in the "Extensions" field in the File Type Manager for the assigned file ID, LAW
will automatically assign the a new extension (from the "Active Ext." field in File Type Manager) to the DocExt field
and place the original extension in the OrigExt field. If this feature is disabled, the OrigExt field will not be populated
and the DocExt field will contain the original extension. Also, if a suspect file is found, it will be reflected in the
SuspectExt field ("Y").
72
Acquiring Documents
General
Click the Settings tab and click General to reach the list of available options.
The General category identifies settings that relate to source selection and the file type management database.
Source Selection
Ensure source names are unique when they are added to the queue - Enabling this item will ensure there are no
duplicate source names in the Source Queue. This feature is particularly useful when dealing with multiple mail
stores with a source name of "Personal Folders." In this example, the first occurrence of the mail store will be
named Personal Folders, while any subsequent mail stores will be added as Personal Folders-001, Personal Folders-
002, and so on.
Automatically set E-Doc folder sources to 'Recurse' when I add them via drag and drop - If using the drag and
drop method to select sources for processing, this option will add the selected folder and all subfolders to the Source
Queue. If this option is not enabled, only the selected folder will be added to the queue.
Scan folder selections for supported mail stores when added to the queue - This option is also located in the
Select Folders dialog when selecting sources. Invoking this option ensures the Electronic Discovery Loader searches
for supported mail stores in folders that are selected for processing and adds them to the queue as mail stores. Two
sub-options are available below this option:
Scan supported archives - When enabled, this option will force the ED Loader to search supported archive
files for supported mail stores. If a mail store is found, the Extract Stores dialog will appear. The user must
select a location to which the ED Loader can extract the mail store(s) prior to processing. Once extracted, the
mail store will be added to the queue.
Add selected folder to queue when mailstore scan is active - This option will force the selected folders
to be added to the queue as e-doc folders following the scan for mail stores. For example, if a folder is selected
that contains 5 XLS files and 1 PST mail store, and this option is enabled, this will result in two sources being
added to the queue: one file set (5 XLS files) and one mail store (PST file). If the option is disabled in this
example, only the mail store would be added to the queue and the folder of XLS files would not be processed.
73
File Type Management Database

Active database - If file type filtering will be used, this option will identify which database is referenced during the
import. New databases may be created and existing databases may be applied in the File Type Manager. See the
File Types section for additional information.
74
Acquiring Documents
NIST(NSRL) Filter
Click the Settings tab and click NIST(NSRL) Filter to reach the list of available options.
The hash database used for this ED Loader filter is compiled from the NSRL (National Software Reference Library)
RDS (Reference Data Set). The NSRL RDS is a collection of file hashes provided and maintained by NIST (National
Institute of Standards and Technology, see www.nsrl.nist.gov). It is a collection of known, traceable software
applications. This filter is typically employed to exclude known files that have no value to a production.
Enabling this option will exclude any files present in the configured hash database using the documents' SHA-1 hash
values. E-Mails are not tested against this filter (although their attachments will be).
Note: If an archive's hash is present in the NSRL database, then it is automatically filtered out and its contents are
not evaluated or logged to LAW. This also applies to embedded/attached archives. If the archive's hash is not
present, then its contents are evaluated on a file-by-file basis.
Hash Database
The NSRL hash database is a collection of SHA-1 hashes for known, traceable software applications. Currently, the
database is deployed as three files:
1. Master database (EdLoaderNistFilter-<NsrlVersion>.mdb) - Contains version information and verification

counts, in addition to a hash partition table pointing to one of the two partition databases.
2. Partition database (1 of 2) (EdLoaderNistFilter-<NsrlVersion>-ISO(A-B).part) - Contains hashes from the

*NSRL RDS_<NsrlVersion>_A and B ISO's.
3. Partition database (2 of 2) (EdLoaderNistFilter-<NsrlVersion>-ISO(C-D).part) - Contains hashes from the

*NSRL RDS_<NsrlVersion>_C and D ISO's.
All three of these files must reside in the same directory in order for the hash lookup to work. If this condition is not
met, or the versions of these files are mismatched, ED Loader will raise an initialization error and block processing
until this configuration is corrected or until the NIST(NSRL) Filter option is disabled.
The NSRL RDS is publicly available as four ISO files containing hashes within specified ranges. The two partition
databases only contain unique instances of each hash present in the ISO.
See the below "Options" section for information on downloading and configuring the hash database for use with
LAW's ED Loader.
75
Options
Enable NIST(NSRL) Filter - Checking this box will enable the NIST(NSRL) filter for the ED Loader session. After
enabling the filter, the hash database path must be configured (see next setting).
Hash Database - The hash database is a collection of SHA-1 hashes for known, traceable software applications.
These hashes are stored in a partitioned Access database (*.MDB), which must be downloaded from a LexisNexis-
hosted web site (see option below). Click the ellipsis button to browse to and select the MDB file and then click the
Open button.
Click here to learn more about the NIST(NSRL) hash database - Click this link to launch an informational dialog
regarding the NIST (NSRL) feature.
Click here to download the latest version of the NIST(NSRL) hash database (launches browser) - Click this link
to download the NIST(NSRL) hash database, which is required in order to use this feature. The database provided
here is the only database that can be used with the NIST filter. The file is an archive named EdloaderNistFilter.zip
and contains three files which make up the partitioned hash database (see "Hash Database" section above
"Options"). Extract the contents to a folder that can be accessed by LAW and then browse to that location via the
Select NIST/NSRL Hash Database dialog (see Hash Database above).
Check for updated NIST(NSRL) hash database - The NSRL RDS is updated quarterly and therefore, the hash
database compiled and hosted by LexisNexis will also be updated as the new data becomes available. Click this link
to check for an updated database. If a newer version is found, LAW will prompt to download the updated database.
76
Acquiring Documents
Output
Click the Settings tab and click Output to reach the list of available options.
The Output settings will determine how selected sources are identified and organized in the tree view of LAW, and
may be important to export specifications for the project.
Folder Output Scheme

Mirrored - With Mirrored as the selected output scheme, the entire folder structure of the selected electronic
files will be re-created in the tree view in LAW.
Relative - Relative applies to e-doc selections only. The path created in the tree view in LAW will begin with
the selected folder, or the folder containing the selected files. Typically, this is the recommended setting as it
may ensure shorter paths and prevent any issues with operating systems' path limitations. This option does not
apply to mail stores as the path within mail stores will always be mirrored when imported into LAW.
Options
Categorize output sources (E-Mails/E-Docs) - When enabled, all mail store sources will be imported into an "E-
Mail" folder and all e-doc sources (including loose e-mail) will be imported into an "E-Doc" folder.
Use source name as top level folder - The Source Name, as displayed in the Source Queue on the Sources
tab, will be used as the top level folder name for each source when imported into LAW.
Ensure root output folder is unique in LAW - Ensures the target folder for each source is unique in LAW. This only
applies when <Case Root> is NOT set as the target folder for a source or sources. For example, if this option is
checked and the other two output options (listed above) are not checked and a user loads to folders that are both
named "EDOC" into a folder in LAW named 001CD, LAW will import one of the EDOC folders into a 001CD-001
folder and the other EDOC folder into a 001CD-002 folder. This will prevent records in both EDOC folders from being
loaded into one folder.
Structure
The structure section provides a preview of the folder structure in LAW (following the import), depending on the
selected Output options.
77
Post Import Actions

Click the Settings tab and click Post Import Actions to reach the list of available options.
Post Import Actions are used to determine which action will occur automatically following an ED Loader import. If no
options are selected, LAW will prompt to index the documents (SQL cases only), following a manual exit from the
results dialog.
Convert imported documents to TIFF - When enabled, the "Display imported documents in grid" option will
be automatically selected as well and grayed out. LAW will automatically attempt to convert the imported documents
to tiff images once it has closed the results dialog after the specified number of seconds. Be sure to make any
desired changes to the tiff conversion settings prior to configuring and initializing the ED Loader session.
Display imported documents in grid - Following the import, LAW will close the results dialog after the specified
number or seconds. Then, the grid view will launch and display only the records imported during that session.
Perform full-text indexing - When enabled, LAW will automatically begin indexing any documents flagged to be
indexed immediately after closing the results dialog that appears following the import.
Results dialog will close after <N> seconds, unattended - Allows users to specify the number of seconds to pass
before the results dialog is closed and the selected post import action takes place. This option will not be available
unless one of the above options has been enabled.
78
Acquiring Documents
Text Extraction
Click the Settings tab and then click Text Extraction to reach the list of available options.
This category is used to configure settings related to the text that is extracted from files during an ED Loader import.
Enable Text Extraction - Enables the extraction of text from applicable files during an ED Loader import session.
Include metadata in extracted text - Includes any available document properties in the extracted text file (i.e.
Author, Title).
Enable binary scanning in text extraction - Overrides the "Ext. Text" flag in the File Type Manager (see File
Types), so that all file types will be scanned for text. If this option is enabled, it is recommended that users also select
the "Validate extracted text" option (below).
Validate extracted text - Scans each text file for readable text. Any text files that do not contain readable text will be
considered invalid and discarded (i.e. text files with only form feed characters).
79
Session Defaults
In addition to the various configuration settings for ED Loader sessions, the Settings tab contains three options that
should be considered when users are configuring sessions for import.
Lock Settings - Once the ED Loader settings have been configured in a particular LAW case, users may choose to
"Lock Settings" to make it known to other users entering the same case that the settings should not be changed, for
example. Once enabled, the button will read "Unlock Settings" and will do just that when clicked.
Apply Settings - This option will save the current settings to a case-level ED Loader configuration file. This feature
will be useful if a user needs to cancel out of the Loader prior to starting a session; applying the settings will ensure
that the user does not have to "start over" when re-launching the Loader.
Set as Default - This option is used to set the current settings as the defaults for all LAW cases that are launched
with the same LAW executable. All settings in the Settings tab are saved as well as the DocID Seed.
80
Acquiring Documents
Reviewing Sessions
Session Viewer
Once an Electronic Discovery Loader session is complete, a log containing important information about the session
may be viewed, such as warnings and any errors that occurred during the import. These logs will be displayed in the
Session Viewer, which is accessible by clicking the View Logs button on the results dialog that appears following the
import.
The Session Viewer may also be launched by clicking File > Import > Electronic Discovery, then File > Open
Session from within the ED Loader. The Session Browser dialog will appear providing a list of existing sessions for
the current LAW case. Choose a session and then click View Session to view the contents. The Show all sessions
option will allow users to view logs for sessions initialized on all workstations (for the current case).
Items listed in bold within the grid are either parent documents or documents that are not, and have no, attachments.
Tabs
There are 13 tabs in the Session Viewer containing information about the currently selected session. The number of
records listed in each tab is shown beside the tab name in parentheses.
1. Overview - Provides a list of session totals, such as the number of items processed, errors, and filtered
items.
2. Settings - Lists all ED Loader settings, as well as certain settings from the EDLoader.case.config.ini
(located in root LAW case folder), and the state of those settings during the selected session. The
VisibleInUi field will indicate if the setting is visible in the ED Loader interface, or if it only exists in the
EDLoader.case.config.ini. The SettingKey displays the name of the setting in the configuration file, while the
UnderlyingValue field displays the value of the setting in the configuration file.
81
3. Sources - Lists all sources that were included in the session. If a source-level failure occurred, this tab will
provide the error message in the row of the item that failed.
4. Incomplete - Lists any records that did not complete the import process. This may have been due to the
cancelling of a session, or due to a problem file that caused a crash during the import
(see Cancelling/Resuming Sessions).
5. All - Lists all records that were imported during the current session.
6. Warnings - Lists records that received some sort of warning message during import. The warning message
will also be logged in the ErrorMsg field for the affected records.
7. Processing Errors - Lists records that received an error message during the import. Typically, these
documents are still imported despite the error, and if so, the error message will be logged to the ErrorMsg
field for affected records.
8. Commit Errors - Lists documents that errored during the import process. Typically, the documents listed in
this tab were unable to be imported due to the error.
9. Duplicates - Lists all records that were flagged as duplicates during the import process. These records may
or may not have been imported, depending on the selected action in the Deduplication settings.
10. NIST Exclusions - Lists records that were filtered based on the NIST/NSRL database. These records are
not written to the LAW case database.
11. FileType Exclusions - Lists records that were filtered based on the Include or Exclude list. The documents
may or may not have been imported, depending on the selected action in the File Types settings.
12. Conditional Exclusions - Lists records that were excluded based on the Exclusions settings. These
documents are not written to the LAW database.
13. Suspect - Lists records that were determined to be suspect files based on the file extension. LAW validates
all files to ensure the original file extension reflects the actual file type. An example of a suspect file would be
a Word .DOC file that was renamed and given a .PDF extension. If the 'Auto Assign Suspect Extensions'
option is enabled in this situation, the DOC extension would be assigned to the DocExt field in LAW, and the
PDF extension would be assigned to the OrigExt field. See File Types for more information.
Session List
This area of the Session Viewer provides a list of sessions that were initialized on the current machine in the currently
selected LAW case. The sessions will be named according to the user-defined Session Labels (specified in the ED
Loader prior to import). See Session Configuration for more information on session labels.
Fields
The Fields section lists the fields available for display for the currently selected tab. Check the box beside a field to
display it in the grid. To group by a particular field, make the field visible and then drag the column header into the
grouping area above the grid. Click View > Collapse All or right-click > Collapse All to collapse the groups. Click View
> Expand All or right-click > Expand All to expand the groups.
Item Properties
The Item Properties panel displays metadata and other information specific to the selected record. The properties for
attachment records will contain information about the parent record as well.
Exporting Session Data

The data contained within the tabs in the Session Viewer may be exported to a separate file. To save the currently
selected tab only, choose File > Save As from the Session Viewer's main menu or click the Save As button on the
toolbar. Select a file type (CSV or TXT), location, and file name, and then click Save. Click Yes at the prompt to view
the output file or click No to view the file later.
82
Acquiring Documents
To save all tabs in the Session Viewer to file, click File > Export To Excel or click the Export to Excel button on the
toolbar. Select a location and file name for the output file and then click Save. Each tab will appear in its own
worksheet in the output Excel file.
83
Summary Reports
Once documents have been loaded via the Electronic Discovery Loader, the ED Reports feature may be used to
generate reports based on the imported data. Launch the standalone grid display by clicking Tools > Display All
Records, clicking the globe icon on the main toolbar, running a query, or by selecting a folder and clicking Folder >
Grid View (or Grid View (Recurse)).
Once the standalone grid has been launched, click Tools > ED Reports to launch the Report Preview dialog. (These
reports are also available from the View Reports dialog in File > Administration. See the Viewing Reports topic for
more information.)
There are currently four reports to choose from when utilizing this feature:
Supported Files by Type: Lists all supported files loaded via ED Loader, grouped by file type. The term
'supported' refers to records that have an application assigned in the SourceApp field. The report contains
paths to each file, a total count of supported files, and a count of supported files for each file type. If the
EDPages field contains data, these values will also be included in the report.
84
Acquiring Documents
Note: The EDPages field contains data when the Extract ED Pages Counts or the E-Print process is run
on the documents.
Unsupported Files by Type: Lists all unsupported files loaded via ED Loader, grouped by file type. The
term 'unsupported' refers to records that do NOT have an application assigned in the SourceApp field (<No
Source Specified>). The report contains paths to each file, a total count of unsupported files, and a count
of unsupported files for each file type. If the EDPages field contains data these values will also be included in
the report.
Supported Files by Type (Condensed): This report is similar to the Supported Files by Type report, but
does not include paths/filenames to each individual file. The report contains a total count of supported files and
a count of supported files for each file type. If the EDPages field contains data, these values will also be
included in the report.
Unsupported Files by Type (Condensed): This report is similar to the Unsupported Files by Type report,
but does not include paths/filenames to each individual file. The report contains a total count of unsupported
files and a count of unsupported files for each file type. If the EDPages field contains data, these values will
also be included in the report.
To create a report, click the name of a report from the list or choose it from the "Selected Report" drop-down list. A
preview of the report will appear in the Report Preview dialog and may be saved to a PDF or HTM file, or printed to
paper. Once the report appears in the preview window, a different report may be selected using the "Selected Report"
drop-down.
File Numbering
To number the file path entries in the Supported and Unsupported Files by Type reports, choose Format > File
Numbering prior to creating a report.
Watermarks
Watermarks may be applied to reports by selecting the Apply watermark to reports option and browsing to the
desired watermark file.
85
Cancelling/Resuming Sessions
The Electronic Discovery Loader may be easily cancelled during an import and restarted at the point where it should
resume to complete the session.
Cancelling Sessions
When a user attempts to cancel an ED Loader session, three options will be presented in a Confirm Cancellation
dialog.
The "Safe Cancel" is the recommended option. The ED Loader will wait until the current item is complete before
ending the session whereas the "Normal Cancel" will stop the session immediately, possibly resulting in incomplete
items. The "Continue" option may be used if the user decides not to cancel the session.
Resuming Sessions
ED Loader sessions may be easily restarted after a user cancels a session manually. To restart a session, click File
> Import > Electronic Discovery and then File > Sessions from the ED Loader. Choose the incomplete session
from the Session Browser dialog.
86
Acquiring Documents
Incomplete sessions will show "recoverable" in the Status message as shown in the above image. Click the Resume
button to restart the session; the Loader will pick up where it stopped at the time it was cancelled.
Note: Only sessions initialized from the current workstation may be resumed.
Sessions that end unexpectedly due to some sort of crash may generate a restart prompt when the ED Loader is re-
launched from the same machine in the same LAW case.
Lost Database Connection

If the connection to a SQL Server is lost during the ED Loader import process, the ED Loader will display a
notification on the Progress dialog just above the total progress bar. During this time, the Loader will attempt to
reconnect to the database and continue processing. The import process can be stopped manually by clicking the
Cancel button.
87
Scanning Documents
Selecting a Scanner
Before scanning any documents from LAW, the user must first select a scanner. All scan functions will be disabled
until a scanner has been recognized. Once a scanner has been selected, LAW will attempt to load the default
scanner each time LAW is launched and a case is opened. To select a scanner, choose Select Scanner from the
Scan menu to display a list of all available scanner drivers. This is not a complete list of supported scanners.
If the connected scanner is not in the list, contact LexisNexis to determine if a driver is available for the scanner. LAW
will generally run any scanner that uses an ISIS driver. If a new model scanner has been purchased that came
bundled with an ISIS driver, do not automatically run the install for the scanner driver. First, check the LAW CD for
that scanner model or contact us to determine if we have a driver for that scanner. Bundled driver installations
typically contain additional system files that may overwrite critical image libraries and cause problems when running
LAW.
If an error occurs when selecting a scanner, there are two possible explanations: either the wrong driver was selected
or the scanner was not recognized by Windows. The scanner will not be recognized if it was not turned on prior to the
operating system loading. Ensure that the scanner is on and restart the computer. If Windows recognizes the scanner
and it still cannot be selected, contact LexisNexis for assistance.
88
Acquiring Documents
Scanner Settings
Scanner settings are those properties that control the operation of the scanner directly. Common scanner settings
include mode (black & white, color, grayscale), resolution (DPI), page size, brightness, and contrast. These settings
can be modified by selecting Scanner Settings from the Scan menu. The Scanner Settings dialog will appear.
Settings such as mode, resolution, and page size may vary from scanner to scanner.
Scan Area
The scan area can be further adjusted by selecting the Area button. A Scan Area dialog will be displayed that
allows users to fine-tune the scan area for the current page size. The scan area dialog allows users to set an X and Y
offset for the page as well as a custom height and width. This custom area applies only to the current page size. The
custom area for each page size is retained between sessions, so users will only have to customize a scan area once
for each page size. Setting a custom scan area may be necessary with some scanner models that frequently exhibit a
black border around scanned images. Because the black border is not even on all sides, it cannot be adequately
removed with black-border removal and must be removed by adjusting the scan area.
89
Scan Brightness
Scan brightness can be adjusted in the Brightness section of the Scanner Settings dialog box. Alternatively, shortcut
keys may be used. The hot keys for adjusting the brightness of the scanner are (Alt+UpArw/DnArw). Using the
<Alt+UpArw> combination will increase brightness by 32 points (-32 points for Alt+DnArw). Pressing either of these
hot keys will cause the scanner settings to pop up for visual inspection and fine-tuning of the new brightness. When
the dialog appears, focus will be placed on the brightness setting so that it can be quickly adjusted by holding the
<Ctrl> key while pressing the left or right arrow keys.
Special Settings
To display any special settings for your particular scanner, select the More button from the Scanner Settings dialog.
The special settings available will vary depending on the selected scanner.
90
Acquiring Documents
Scan Options
In addition to the standard scanner settings, LAW provides several scan options to help improve scanning efficiency.
The scan options can be toggled by selecting the desired option from the Scan > Scan Options menu. The scan
options menu can also be displayed by right-clicking on any of the scanner settings displayed in the status bar (lower
right-hand corner of main form, shown below). The scan settings displayed on the status bar are some of the most
frequently used settings and can be toggled by double-clicking the desired setting.
Scan Menu
Status Bar
Page Size
The Page Size setting provides a quick alternative to selecting the page size from the Scanner Settings dialog. This
option allows users to toggle between the four most popular page sizes: Letter (<F7>), Legal (<F8>), Double Letter
(<F9>), and A4.
Scan Mode
The Scan Mode controls how the scanner will scan documents: Simplex (<F10>), Duplex (<F11>), or Flatbed
(<F12>). Simplex is used to scan single-sided documents and Duplex is for double-sided documents. The Flatbed
setting is used to scan a page from the glass bed; although, if pages are in the document feeder, it defaults to
91
Simplex and scans a single page from the feeder. If the scanner does not support duplex scanning, use the Turnover
Mode option (see below) to scan double-sided documents.
Auto-Deskew
The Auto-Deskew scan option will deskew (straighten) documents as they are scanned. The deskew filter can also be
applied to multiple documents during Batch Processing and to individual documents (see Page-level Cleanup).
Black-Border Removal
The Black-Border Removal scan option will remove black edges from all newly scanned images. This filter will only
pick up even black edges. If the black edge is uneven or slanted down the page, it will not be dropped. These borders
are a result of the scanner model being used and the scan area will have to be adjusted in order to remove them. The
scan area can be adjusted from the Scanner Settings dialog. Black borders left on pages can prevent LAW from
recognizing blank pages, so this filter should be selected if using the Drop Blank Pages scan option. The black-border
removal filter can also be applied to multiple documents during Batch Processing.
Detect Barcode Breaks

The Detect Barcode Breaks setting allows users to scan multiple documents in a single batch. Barcode pages can be
used to determine both document- and folder-level breaks while scanning. The settings for the break sheets can be
specified from the Imaging tab of the Options form. Images with the default barcode settings can be found in the
installation directory for LAW. These images can be opened with any image viewer and printed if users need to
prepare a scan job with break sheets. Light-colored paper is recommended when printing barcode sheets (e.g., white,
light blue, light yellow, or light green). LAW relies on the contrast between the bars in the barcode and the
background color of the paper for detecting the barcode value. Scanner brightness or contrast (Scan > Scanner
Settings) may require adjustment if LAW is having a difficult time recognizing the barcodes. See Using Barcodes for
more information about barcodes.
Drop Blank Pages

The Drop Blank Pages setting determines whether or not to disregard pages that have a very low percentage of text
or graphics (possibly blank pages attached to a document). If this option is set, pages with very low pixel ratios will
not be saved. If this option is not set, all pages scanned will be saved. This feature can be extremely useful as it
allows users to combine both single- and double-sided documents in a single batch. Blank backsides of all single-
sided documents will be dropped. The backsides of the double-sided documents containing text or images will be
retained.
Invert Pages
The Invert Pages setting allows users to invert (rotate 180 degrees) odd or even pages of a document. This feature is
used for double-sided documents that are printed with opposite orientations on the front and back.
Noise Removal (Despeck)

The Noise Removal setting allows users to apply a filter to reduce the amount of random dots and specks that appear
on the scanned image. OCR results may improve if Noise Removal is performed on a document before converting it
to text.
OCR All New Pages

The OCR All New Pages setting determines whether or not all new pages being scanned will be flagged for OCR.
LAW allows users to flag certain pages for OCR to help increase OCR speed and efficiency. Pages with graphs and
tables or handwriting are not good OCR candidates and may negatively impact OCR performance. See the Flagging
Documents/Pages for OCR section for information on flagging pages after they have been scanned.
92
Acquiring Documents
Scan Rotation
The Scan Rotation setting can be used to rotate pages as they are scanned. Images can be rotated 90, 180, or 270
degrees. Scanning documents in landscape mode may increase the scanner throughput and help prevent paper
jams. If using this feature to scan landscape, the scanner must support double-letter page size in order to capture the
full height of the document.
Single Pages
The Single Pages setting instructs LAW to save all pages in a batch as one-page documents. This can be used to
scan a large group of single-page documents in one batch, saving a great deal of time.
Turnover Mode
The Turnover Mode setting can be used to scan double-sided documents without a duplex scanner. If this option is
enabled, LAW will prompt to flip the document and continue scanning after the front side of a double-sided document
has been scanned. LAW then rebuilds the document in the proper order.
Note: If this option is enabled, the "Detect Barcode Breaks" setting will be ignored because the document must be
flipped after the front side has been scanned.
Scan Page Limit

The Scan Page Limit feature can be used to specify a page limit for the number of pages scanned per document.
This feature can be very useful for scanning checks or note cards, for example.
Configure Filters
This option allows advanced users to modify the default settings of certain filters.
Note: These settings should only be modified if the default settings are not working or causing problems.
93
Imaging Options
Imaging options will control the format used to save images when scanning and the settings used for barcode break
sheets. (See the Using Barcodes section for additional details.) These options are available by selecting Tools >
Options > Imaging from the main form.
Scanner Output
Color Format
This setting is for display purposes only; it may not be modified from this form. This setting identifies the color format
selected by the scanner and determines which file types are available. To change the color format displayed, users
must change the color mode via Scanner Settings.
File Type
The File Type setting determines what type of format, or packaging, is used to save newly scanned images. Common
file types include Adobe (*.pdf), Bitmaps (*.bmp), Calera (*.pda), Fax (*.dcx), JBIG (*.jbg), JPEG (*.jpg), PaintBrush
(*.pcx), Portable Network Graphics (*.png), and TIFF (*.tif). The file types available are determined by the color format
selected. For example, if Binary (Black & White) is the current color mode, JPEG is not available as a file type
because it can only be used for True Color and 256-Level Grey images.
Note: TIFF images (specifically CCITT Group 4) are accepted as the industry standard and are the recommended
format for black & white images. Users can scan to PDF (a frequent request). However, certain features (e.g.,
94
Acquiring Documents
endorsing images and OCR to a non-text format) will not be available to PDF images. If PDF images are required in
the destination application, this conversion can be handled during the export process after the images have been
endorsed and OCR'd by selecting the PDF Conversion export format or by choosing PDF as the Output Format
(see Options tab).
Compression
The Compression setting determines the type of compression used for the specified file type and is specifically
determined by the file type and color format. CCITT Group 4 is the common compression for a TIFF image, although
this compression is not available for non-bitonal images. If scanning color or grayscale images, we recommend
Sequential JPEG as the compression type (TIFF as the File Type). It offers excellent compression for both color and
grayscale images and can be used with multi-page images.
Storage Schema
The Storage Schema setting determines how scanned documents are stored. The Serialized option stores images as
single-page images. For example, scanning a 5 page document stores each page as a separate file. The files are
stored in the $Image Archive folder located in the root case folder. The Multipage option stores images as multiple
pages in one file. For example, scanning the same 5-page document stores one file with 5 pages. The files are stored
within the case folder structure displayed in the folder view.
Note: Moving pages in the thumbnails display is not currently supported for records scanned using the Serialized
Storage Schema.
Barcode Breaks
Barcodes are used in scanning to establish barcode break settings. These settings allow users to specify custom
values for barcode sheets that determine both document and folder breaks and control other aspects of the
recognition process. In order to use these settings, the "Detect Barcode Breaks" scan option must be enabled. See
Using Barcodes for more information.
95
Scanning in LAW
Once the scanner has been selected and any additional scan options have been set, users are ready to begin
scanning. All newly scanned documents will be saved in the current folder, so encourage scanner operators to make
periodic checks to ensure they are still in the intended folder. When scanning documents, remove any staples, clips,
rubber bands or other bindery materials, and then place the page(s) to be scanned in the auto-document feeder or on
the flatbed.
New Documents
Adding Documents
To add new documents to the current folder, open the desired folder, and select New Document (<F3>) from the
Scan menu. All new documents will be added to the end of the folder. If scanning from the document feeder, LAW
scans until the feeder is empty. Some scanner models have a delay option that allows users to insert more pages
and continue scanning in the same batch once the feeder is empty. This is helpful if scanning large documents that
exceed the capacity of the feeder or multiple documents separated by barcode document break sheets. For scanner
models without this functionality, set the 'Prompt to continue scanning when feeder is empty' option on the
Preferences tab of the Options form (Tools > Options). If this option is enabled, users will be prompted to insert
more pages when the feeder is empty or users can cancel to end the batch.
Adding Attachments
Documents can also be added as attachments to other documents. This allows logical grouping of related
documents. Adding attachments during scan time can be done in two ways. To manually add an attachment, select
New Attachment (<Ctrl+F3>) from the Scan menu. The new document will be added as an attachment to the last
document in the current folder. Attachments cannot be added at scan time to intermediate documents in a folder. If
documents have been scanned out of order, the user will have to scan the attachment as a normal document to the
end of the folder, move it immediately behind the appropriate parent document, and then manually attach it. For more
information on attaching existing documents, see the Working with Attachments section.
If using barcode break sheets to scan multiple documents, attachments should be preceded by an attachment break
sheet as opposed to a standard document break sheet. The break sheet for attachments is named attach1.tif and can
be found in the installation directory for LAW. A shortcut to this file (Attachment Break #1) can be found in the Break
Sheets subfolder in the LAW program group. Documents preceded by an attachment break sheet will always be
attached to the previous parent document. Therefore, to scan a document with three attachments, a standard
document break sheet would precede the parent, and an attachment break sheet would precede each of the three
attachments. Attached documents' ItemNo value will appear indented in the document list to indicate that they are
attached to the previous document.
96
Acquiring Documents
(In the above figure, document #0002 is attached to document #0001 and document #0008 is attached to document
#0007)
Inserting Documents
LAW allows the insertion of documents in a particular location within the current folder by selecting Edit > Insert >
Scanned Document, allowing users the ability to insert a document that was missed at scan time. This feature is
very important because, unless documents are specified by a query, all processing functions (batch processing,
exports) are executed in scan order. The insert document function can be used to insert multiple documents if the
"Detect Barcode Breaks" setting is enabled and the pages are separated by barcode break sheets. The inserted
document will be placed above the currently selected document in the current folder.
Modifying Existing Documents

Appending Pages
The Append Pages function lets users append new pages to an existing document. To append new pages, select the
document to which the pages should be appended, and select Append (<F5>) from the Scan menu. The new
page(s) will be added to the end of the selected document.
Note: The Append Pages function is not a batch scanning function. In other words, it will not check for barcode
break sheets, even if the "Detect Barcode Breaks" feature is activated. It is only intended to add pages to a single
document. If using break sheets, use the "Prompt to continue scanning..." setting to allow users to keep adding
pages to the current batch until it is complete. Otherwise, users must manually ensure that document integrity is
maintained every time that a batch is broken down so that it fits into the auto-feeder.
Inserting Pages
LAW also allows users to insert pages into existing documents in the event that pages were missed or acquired from
another source. If users need to insert new pages from the scanner, select the Edit > Insert > New Page(s). The
new pages will be inserted before the currently selected page. To insert pages from existing documents, select the
Existing Page(s) menu item from the Insert menu. If inserting existing pages, the user will be prompted to select one
or more existing images to insert.
Note: If multiple documents are selected, they will be imported in alphabetical order by filename. Also, the Insert
Pages function works the same as the Append Pages in that it disables checks for barcode break sheets because it
is designed to insert pages into the current document.
97
Replacing Pages/Documents
The Replace function allows users to replace pages within a document or the entire document altogether. To replace
individual pages within a document, select Edit > Replace > Page(s) (<F6>) (or Document (<Ctrl+F6>) to replace
the entire document). If replacing pages, the new pages will replace the current page forward for as many new pages
are scanned. Both replace pages and document work the same as the append and insert page functions, disabling
the detection of barcode breaks. The Edit > Replace > Image from File(s) option allows users to replace an entire
document with an existing image. Only one existing image may be selected when using this feature.
98
Acquiring Documents
Using Barcodes
Documents may be prepped for scanning using barcode break sheets. These break sheets may be used to
automatically break documents, folders, and/or create attachment records during the scan process. With additional
configuration, the barcode values may be stored in an index field or used to number the documents.
Barcodes breaks may also be used when importing raw images, to break the documents and optionally code multiple
index fields. See the Importing Raw Images section for additional information.
Barcode-related settings may be found by clicking Tools > Options from the main menu and choosing the Imaging
tab.
Folder Level
This setting determines the barcode value used to represent a folder break. If a barcode that matches this value is
encountered while scanning, a new document is started in a new folder. LAW will increment the current folder name
by one for the newly created folder's name. If the next logical folder does not exist, it is automatically created.
99
Document Level
This setting determines the barcode value used to represent a document break. If a barcode that matches this
value is encountered while scanning, a new document is started. To include multiple document break sheets, enter all
possible values separated by semi-colons (;).
Attachment Level
This setting determines the barcode value used to represent an attachment break. If a barcode that matches this
value is encountered while scanning, a new attachment is created and attached to the previous document.
Ignore Barcode Value

Use this option to ignore and drop barcodes matching the specified value during scan time. Multiple values to ignore
may be specified by separating each value with a semi-colon (;).
Storing Barcode Break Sheet Values in a Field

The values on barcode break sheets can be stored in a field or used to automatically number documents at scan
time. To use this feature, break sheets must be created for every unique value or every document (if using to auto-
number). When using this feature, the barcode value must be entered in the following notation:
/p/f <prefix> <field>
The <prefix> is a common prefix that must be present on every barcode. The <field> is the name of the field used to
store the value. (Note: If spaces exist in the prefix or field name, they MUST be enclosed in single quotes.) The value
to be stored is the value of the barcode with the prefix stripped. For example, if the user has entered "/p/f ID-
DocumentID" (without quotes) for the value of a document break, LAW would recognize all barcodes starting with "ID-
" as a document break, and the remaining text would be stored in the DocumentID field. A barcode value of "ID-
ABC001" would then be detected as a break sheet, and "ABC001" would be stored in the DocID field of that
document. To use this feature for auto-numbering, simply specify BegDoc# as the field name. This notation may be
used with Document, Attachment, or Folder level break sheets.
Dilate Scan Region

Dilates (widens, similar to converting a font from normal to bold) the area tested for barcodes. This setting can help
recognize poor barcodes with lines missing that may prevent recognition; however, its use may actually prevent
recognition of otherwise recognizable barcodes. As such, it should be used with caution and only as a last resort
when all other options have failed.
Scan Entire Page

This setting causes the entire page to be scanned for barcodes at scan time. This may slow scanner throughput due
to the increased time required for barcode detection and should only be used if barcodes are located in various
positions on the page.
If this setting is disabled, only a portion of the page will be scanned for barcodes. The region used to scan for
barcodes can be displayed on the main image display (image must be open) by selecting Tools > Barcodes >
Display Scan Region. The region used for barcode detection will become highlighted on the current image. This
region can be modified by creating a new region and selecting Tools > Barcodes > Set Scan Region. To create a
new region, hold the Ctrl key down and draw a rectangle by dragging the mouse from one corner of the rectangle to
the opposite with the left mouse button depressed.
Use Thorough Scan

This setting causes LAW to use a more rigorous barcode detection method. Enabling the thorough scan will improve
recognition and is especially helpful in recognizing poor quality barcodes. This method does, however, take longer
100
Acquiring Documents
and slows scanner throughput, although the difference is negligible on faster systems when using a relatively small
scan region.
Extracting Barcode Information

LAW can scan all pages of the current document for any barcode values. To access this feature, select Tools >
Barcodes > Scan All Pages from the main form. All pages of the current image will be scanned, and any recognized
barcodes will be saved to a delimited text file in the following structure: Value, Page, BarcodeNo. If no region is
active, the entire page will be scanned. If a region has been created, only this area of every page will be scanned.
Troubleshooting Barcode Breaks

The following section contains information for troubleshooting common issues relating to barcode break sheets not
being recognized in LAW.
Paper - LexisNexis recommends using a light colored paper, e.g., light yellow or light blue paper. Dark paper
decreases the contrast between the bars in the barcode and the paper's background causing detection of the
barcode to become more difficult. A Laser Jet printer should be used to create a sharper barcode font. Photocopies of
barcodes may result in "fuzzy" barcodes, which can be difficult to read. Also, if the barcode sheets are too badly
wrinkled, they may become unreadable as well.
Scanner Brightness - Adjustment of the contrast and/or brightness of the scanner may be required to produce a
better quality scanned document and barcode image. If LAW appears to be detecting barcodes sporadically, this
adjustment will likely resolve the problem. In LAW, choose Scan > Scanner Settings and increase or decrease the
contrast or brightness of the scanner and test the new settings. It may be necessary to run multiple tests to find the
optimal setting for the scanner.
Expected Barcode Values - Verify that the value on the barcode matches the value shown under the Tools >
Options > Imaging tab. The value on the barcode must match the value in the "Doc" field to be considered an actual
document break sheet. If these values do not match, the barcode sheet will be imported as a normal page in a
document.
DPI - The lower the DPI, the lower the quality of the scanned image and barcode will become. The most common DPI
settings are between 200-300 DPI.
LAW Settings - Verify that the current LAW settings appear as listed below:
Scan > Scan Options:
Detect Barcode Breaks is checked

Single Page is not checked (if checked, each new page becomes its own document)
Auto-Deskew may need to be checked
Noise Removal is not checked - feature may ruin the image of the barcode when enabled
Select an image and click Tools > Barcodes > Display Scan Region to verify that LAW is looking in the correct
place when scanning for a barcode.
Tools > Options > Imaging tab: Using all three of these settings will override the "Scan Region" as noted above and
scan the whole page.
Dilate scan region is checked

Scan entire page is checked
Use thorough scan is checked
If a barcode image is already present - Choose the image and click Tools > Barcodes > Detect Barcode to scan
the current document and display the value of the barcode if a barcode has been found. This test may also reveal an
unexpected value of the barcode which could be causing the problem.
101
If the scanner is able to scan all the barcodes but does not detect them - Re-review the items above or split the
documents based on the barcode images using the Split document function. Select the image, right-click, and select
Split Document > Barcode break sheets.
For additional assistance with barcodes, please contact Technical Support.
102
Acquiring Documents
Importing Images
Importing Cases and Load Files
LAW allows the import of existing files in the event the files are obtained from an outside vendor, in an existing project
in another format, or in a case from a previous version of LAW. Imported files must be accompanied by a load file in
one of the supported formats if document boundaries are to be determined. If single-page images exist with no
document breaks defined, then either a load file must be created in one of the supported formats or document
boundaries must be created within LAW after they have been imported. LAW will store imported images in the same
format as the original images; single-page will remain single-page and multi-page will remain multi-page. With the
exception of Z-Print imports, all images imported via load file will be stored in the <case root>\$Image Archive folder.
Rather than copying files into the LAW folder structure during import, LAW offers the option to link to files in their
current location. This applies to Doculex, EDRM, IPRO, Opticon, and Summation load file imports. To toggle the
setting, click Tools > Options > Preferences and locate "Link to source files in place when importing load files."
When enabled, LAW will avoid copying any native files or images associated with the load files and link to their
existing location.
Note: LAW will not link to document text when using the "Link to source files in place when importing load files"
setting. The associated text files will be copied to the applicable location within LAW's case folder structure.
Note: Modifying the images in LAW (i.e., rotating or annotating) will result in the source file being modified. If the
source image should not be altered, do not use the "Link to source files in place when importing load files" option.
To simply import raw images (without a load file or defined format), use the Import Raw Images function detailed in
the Importing Raw Images section.
Import Formats
LAW Case
The LAW Case import function allow users to import an existing LAW case (created in version 4.x or 5.x) into a new
or existing LAW case. To import an existing LAW case, create a new case or open an existing case and select File >
Import > LAW Case. The LAW case list will appear allowing users to select a case from the current list or browse to
one not in the list.
All fields in the source case will be automatically created if they do not already exist. The path structure for the
existing case will be re-created in the current case relative to the current folder. The image and native records,
text, and index information from the source case will be copied into the current case so there is no danger of losing
any existing data. This does, however, mean that the user must manually remove the existing case if everything was
imported successfully and it is no longer needed; otherwise, two copies of the same images will exist.
**KNOWN ISSUES:
The DupStatus, _DupID, and _DupMethod fields will be cleared for EDD records being imported into a new
LAW case.
User-defined page-level fields existing in the source case will not be imported into the target case.
Session databases are not copied from the source case folder to the target case folder, so when attempting
to view the logs in the Session Viewer from the target case, users will notice a "database not found" message.
The logs are still viewable from the source case and users can browse to the location of the databases from
within the target case using the Session Viewer.
Z-Print Load File

The Z-Print import allows users to import images using a log file created by Z-Print during its printing or pre-saving
process. This log file is named <job name>.csv and is located in the root destination path of the processed Z-Print
103
job. Select File > Import > Load File and then select the Z-Print log to import. The incoming fields can be mapped to
existing fields in LAW or selected to be skipped. LAW can also import a pre-saved job that has not yet been
processed to images. This allows users to pre-screen the documents and make detailed selections on the documents
they want to process.
Click the Options button to view the available import settings.
Check for Matching Records - If this option is not selected, LAW will import the images and metadata into the LAW
case regardless of what the DocID value is for the existing documents (normal method). If this option is selected,
LAW will compare the value in the DocID field of the csv file and look for matching values in LAW's DocID index field.
If an exact match is found, there are 3 additional options on how the matching data can be updated.
104
Acquiring Documents
Ignore incoming record - The data in the csv being imported will not be imported if a document with a
matching DocID value exists. This feature is useful if a csv file was only partially imported and skipping the
existing records would speed up the import process.
Replace existing record - If the DocID of the incoming data matches an existing document's DocID value,
the data from the csv will replace all the existing metadata for the specified document and the image itself. So if
the existing record contains 10 fields of data, and you choose to re-import only 1 field, the 10 fields will be
cleared and only the 1 field will be populated.
Update existing record - If the DocID of the incoming data matches an existing document's DocID value,
the data from the csv will update the existing metadata for the specified document and the image itself. So if the
existing record contains 10 fields of data, and you choose to re-import only 1 field, only the 1 field will be
updated with the new information and the other fields will remain unchanged.
Note: This update feature is primarily designed to attach images to existing data. So when updating, it
ignores records without images (those with pagecount=0).
Drop Blank Pages - LAW will drop any blank pages that are detected during the import process to reduce image
sizes and total page counts for documents. By changing the "Blank Sensitivity" option, users can specify the
sensitivity of the drop blank pages filter. Pristine White (recommended) is used for perfectly (all white) documents and
is best suited for digitally converted documents. Scanned images may require a slightly less sensitive filter. Dirty
White allows the document to contain a small amount of (non-white) data, such as speckles, creases, or folds.
Note: If Drop Blank Pages is enabled, at least 1 page will always be retained even if all the pages are blank.
Note: If pages are dropped, the metadata in the csv file will not be updated to reflect the new page size in LAW, this
may result in page count differences between LAW and the Pages field in the csv.
Ignore Unflagged Documents - If this option is set, all records in the csv with a Status value of N (do not print) or D
(duplicate) will be skipped during the import process. This can be useful when using the Update Z-Print Flags feature.
Link to images in place - This feature can be used to link to the source files in their existing location rather than
copying the files into the LAW case folder structure.
Doculex Imagebase
The Doculex import allows users to import images from a Doculex imagebase. A Doculex imagebase does not
contain any index information so only page numbering will apply to the imported documents. To import a Doculex
imagebase, select File > Import > Load File and browse to the desired imagebase (Doculex3.dbf or Doculex5.dbf).
The path structure for the images will be re-created relative to the current folder in LAW. If importing multiple
imagebases, creation of a separate folder for each volume is recommended as the folder structure will frequently be a
sequential numeric format (e.g., \001, \002, etc.). If a separate folder for each volume is not created, images from
different volumes in the same folder may occur. While this will not affect LAW, it can be confusing and interfere with
processing order.
The Doculex import does not require the documents breaks to be defined in the database. Existing breaks can be
overwritten with new ones defined by a range file. A range file is simply a delimited text file with two fields, BegDoc#
and EndDoc#, which specify the ranges to use when rebuilding the documents. If no range file is specified, the
document breaks defined in the Doculex imagebase are used.
Opticon Load File

To import an Opticon volume, select File > Import > Load File and browse to the desired load file (*.opt or *.log). If
text files matching the image filenames are found in the source directory, the text files will be imported as OCR text.
Summation Load File

The Summation import allows users to import images with document breaks defined by a Summation load file. Select
File > Import > Load File and browse to the load file (*.dii). The folder structure will be re-created relative to the
current folder. Depending on the path notation in the load file, users may have to select the image path for the
105
images. If the load file uses CD volume notation (@V), LAW will attempt to find the CD drive letter that contains the
images. If the images have been copied to a local drive from a CD or the image directory notation (@I) has been
used, users must specify the directory in which the images are stored.
OCR is also imported if it exists with the images. LAW will merge page-level OCR (one text file for each single-page
image) into one text file for the entire document during the import process. LAW will also import any existing word list
files (*.ocr) with images if they exist.
A Summation load file may contain index information for each document. This index information may or may not be
imported, depending on the user selections in the Import Fields dialog.
Note: The user must select Yes to the prompt asking to include fields in order for this dialog to appear. A list of
fields found in the Summation load file will be displayed in this dialog.
The Source Name column will list every field contained within the Summation load file. Fields listed in blue are new
fields (do not already exist in the LAW case). The Destination Name column displays the name of the field that will be
created or the existing field name in the LAW case. Both new and existing field names may be changed by double-
clicking in the cell and entering the desired name. To exclude a field, clear the check box in the Include column in the
proper row. The Type field displays the field type for each field. The type can be changed for new fields only.
Note: Summation load files do not contain page IDs (or Bates numbers) for every page; they can only contain a
beginning document number and an ending document number. LAW automatically numbers every page based on
106
Acquiring Documents
the first page of the document, but this may not match the originals exactly if gaps or changes exist in the
numbering scheme within the document.
IPRO Load File

To import an IPRO volume, select File > Import > Load File and browse to the desired load file (*.lfp). If text files
matching the image filenames are found in the source directory, the text files will be imported as OCR text.
EDRM XML 1.0

The EDRM XML format can be used to import any combination of native, text, images, and metadata into an
electronic discovery enabled LAW case. To import an EDRM XML file, select File > Import > Load File and browse
to the desired load file (*.XML).
Note: The XML format is only available for import in ED-enabled LAW cases.
An Import Fields dialog will appear allowing management of fields included in the XML file. The Source Name column
will list the fields contained within the load file. Fields listed in blue are new fields (do not already exist in the LAW
case). The Destination Name column displays the name of the field that will be created or the existing field name in
the LAW case. Both new and existing field names may be changed by double-clicking in the cell and entering the
desired name. To exclude a field, clear the check box in the Include column in the proper row. The Type field displays
the field type for each field. The type can be changed for new fields only.
Any native, text, and image files referenced in the load file will be copied to their respective folders in LAW. If the
"Link to source files in place when importing load files" option in Tools > Options > Preferences is enabled, only text
associated with native or image files will be copied into LAW.
107
Importing Raw Images

To import image files (images without an associated database or load file) into LAW, use the Import Raw Images
utility. To import images with a supported database or load file, use the image import functions described in the
Importing Cases and Load Files section.
To import a set of existing images, select File > Import > Raw Images. The Import Raw Images dialog will appear
(see below) and allows users to select individual images or folders of images and set import options.
Selecting Images
The Import Raw Images utility allows users to select either individual images from the file list on the right or entire
folders from the folder tree on the left. Certain types of images may be filtered out using the drop-down below the file
list, or All Image Files may be selected to view and/or import any supported image file types. To import an entire
folder structure, simply check the "Include subfolders" option; all selected folders and any subfolders will be imported.
When raw images are imported, the folder structure will be created relative to the current folder in LAW, so ensure
that the desired folder is selected prior to import.
Import Options
The Import Raw Images utility provides several options to assist with customizing the import process. These options
can be displayed by pressing the Options... button on the Import Raw Images form.
108
Acquiring Documents
Convert images to binary (B&W)

Use this option to force all images to be converted to black and white during the import process.
Determine document breaks

This setting can be used to split multi-page image files into separate documents during the import process based on
the specified separator type: blank pages or barcodes. If blank pages are selected, click the More... button to specify
the "Sensitivity" for the blank page filter. 'Pristine White' (recommended) is used for perfectly (all white) documents
and is best suited for digitally converted documents. Scanned images may require a slightly less sensitive filter. 'Dirty
White' allows the document to contain a small amount of (non-white) data, such as speckles, creases, folds, etc.
(recommended for scanned documents).
If barcode break sheets are selected, the value of the barcode to be used to break the documents must match the
document break value specified in the Barcode Settings dialog, which may be launched by clicking the More...
button. Each time a barcode with the specified "Barcode Value" is detected, a new document will be created.
The "Capture barcode values" option allows users to capture additional barcode values on the break sheet and place
the values into index fields for the newly created document. For example, a barcode break sheet image contains
three barcode values: DOCBREAK, MEMO, and ABC0001. If two index fields are created, the "MEMO" and
"ABC0001" values can be stored with the newly created document. In this example, the DocType field has been
selected to store the first "non-document break" barcode value ("MEMO"). Then, the next barcode value detected on
this sheet will be placed in the next index field immediately following the DocType field as listed under the Index tab
on the main LAW window.
Note: This feature does not currently support Folder or Attachment barcode breaks; however, support for these
barcodes will be available in a future release of LAW.
Include OCR
When enabled, this option instructs LAW to import any associated text files (*.txt, *.doc, *.wpd, *.htm) that exist with
the images.
109
Link to images in place

When enabled, LAW will link to the selected images in their current location rather than copy the files into the LAW
case folder structure. This feature is extremely useful when hard drive space is limited.
Remove originals
This setting will cause LAW to remove the original images once they have been successfully imported. This feature is
useful in the event the import process is cancelled or gets interrupted for any reason, leaving only the images that
have not been imported. Users can resume at a later time without re-importing any of the same images.
Note: This setting is ignored if the images are on a read-only source (e.g., CD-ROM).
Use filename as BegDoc#

This setting causes the incoming images to be numbered according to their filenames. This feature is very helpful if
the images have been named according to their document numbers. However, if the documents are multi-page
images and have been named sequentially (e.g., AB0001.tif, AB0002.tif, etc.), numbering them in this manner will
cause duplicate page IDs. The "Use Numeric Suffixes" setting accounts for this by allowing users to name the first
page of each document according to the filename and the remaining pages with a numeric suffix. The default setting
(*.###) will force a suffix padded with three digits, separated by a period (e.g., AB0001, AB0001.002, AB0001.003,
etc.). The separator character can be modified or omitted and the number of pad digits can be adjusted with the
format string.
Mirror original structure

This setting causes the original folder structure to be rebuilt relative to the topmost selected folder(s). The selected
images will then be imported into the currently selected folder in the folder list window.
Auto-increment folder
This setting dumps all incoming images into the current folder until the specified "File Limit" has been reached. Once
the file limit has been reached, a new folder is automatically created on the same level as the current folder and
becomes the new image destination.
Note: LAW will not auto-increment the root image folder. If this setting is selected, at least one folder
must exist under the root folder.
Store original filename

This setting can be used to store the filenames of the imported images in an index field.
Store original location

This setting can be used to store the path of the imported images in an index field. If the same field is used for the
filename and location, the full path of the images (path and filename) will be stored in the specified field.
110
Image Display
Image Display
Viewing Images
Images will appear in the Image display on LAW's main interface. LAW gives users all basic image viewing
capabilities provided with any image viewer. LAW allows users to zoom in and out, fit to width or window, view in
grayscale, invert, view thumbnails, and utilize several other features to make image viewing as effective as possible.
LAW even allows launching of the image in a separate viewer by selecting Tools > Launch Viewer. This feature
opens the image in the default image viewer for the specified image type and is beneficial if performing functions not
available in LAW. If the image is modified in any way, the user will need to switch documents in LAW before saving
changes; otherwise, a locking violation will occur.
Zoom Features
Zoom In/Zoom Out
Select View->Zoom In (<Ctrl+PgDn>) to zoom in on an image or View->Zoom Out (<Ctrl+PgUp>) to zoom out. To
zoom to a selected area, simply draw a rectangle (hold left mouse button down and drag mouse to opposite corner of
rectangle). As soon as the mouse is released, LAW zooms to the area defined by the rectangle. Double-click to return
to the "Best Fit" state.
Best Fit/Fit to Width

The Best Fit and Fit to Width features allow users to quickly zoom the image so that the entire image is displayed in
the image window (Best Fit) or the width of the image is zoomed to fit the image window (Fit to Width). The Best Fit
setting is the default when opening images. These settings are both available from the View menu by selecting Best
Fit or Fit to Width. The Best Fit setting can also be quickly restored by double-clicking on the current image.
Zoom Lock
The Zoom Lock feature allows users to use the same zoom factor for all pages opened in LAW. This feature is useful
when inspecting a certain portion of all documents (i.e., lower right-hand corner for a Bates number). To use this
feature, users must first set the zoom lock by selecting Zoom Lock (Ctrl+Z) from the View menu. When the zoom
lock is activated, a small lock icon will be displayed on the Image button to remind users that it is enabled. Once the
zoom lock is activated, simply zoom to the desired area and all subsequent pages will be zoomed to the same
approximate area. Note: The area may appear to jump slightly from page to page due to small discrepancies in page
sizes and the way the zoom area is applied. To reset all pages to the default mode of Best Fit, simply select Best Fit
while Zoom Lock is still enabled. Turn it off by selecting it again.
Scrolling the Image

Once an image has been zoomed and cannot be entirely displayed in the image window, users must scroll the image
to view different areas. When an image is zoomed in, horizontal and vertical scrollbars will appear. These scrollbars
can be used to scroll the image up and down and left and right by clicking the desired scroll bar in the desired
direction. When inspecting documents, the image may be scrolled by holding the <Ctrl> key and using the arrow keys
rather than the mouse.
Pan Window
The Pan Window feature provides another way to scroll the image. To activate the pan window, select View > Pan
Window from the main menu. A small pan window with a black box that represents the zoomed portion of the current
image will open. The black box can be dragged in the pan window; the area that it pans over is displayed in the main
image window.
111
Viewer Options
Scale to Gray
The Scale to Gray setting makes images much clearer when viewed and is the default setting for LAW. To toggle this
setting, select View > Scale to Gray from the main menu. This feature is for viewing only and does not alter the
image in any way.
Invert
To invert an image, select View > Invert from the main menu. This feature is useful when viewing documents that
have shaded or colored backgrounds, making them difficult to interpret. The Invert feature reverses the colors and
clarifies the image. This feature does not alter the image in any way; it is for viewing purposes only.
Rotating Pages
LAW allows users to rotate pages in the event that one or more pages are improperly oriented. Pages may be
rotated automatically while scanning using the 'Output Rotation' setting (see Scan Options for more details). Pages
may also be rotated during the quality control process if they were not corrected at scan time or were acquired from
another source. Rotate one or more pages by selecting Page > Rotate Left (Ctrl+L), Rotate Right (Ctrl+R), or
Rotate 180. If no pages are selected, only the current page will be rotated. If one or more pages are selected, all
selected pages will be rotated the specified direction. Note that rotating an image is for viewing purposes only. The
main image window will display the current page with the new rotation setting; however, the thumbnails view will
display the page with the original orientation. To save the rotation for the image, select File > Save (Ctrl+S) and the
current orientation for all pages will be saved, updating both the thumbnails and Image displays.
Note: Rotating an image that has been endorsed by LAW may result in undesired results if the endorsement is later
modified or removed. See Header/Footer Options for further information on endorsing.
Page Navigation
LAW provides several ways to navigate between pages of multi-page documents. The First Page, Last Page,
Previous, or Next menu items can be selected from the Page menu to move between pages or the navigation
buttons on the main toolbar can be used.
The Page menu is available by right-clicking within the thumbnails display to make the page functions more readily
accessible. Users may also use the left and right arrow keys to move to the previous or next page provided one of the
image windows (main image or thumbnails) or the document list has the focus. The Goto Page (Ctrl+G) function from
the Page menu will launch a dialog that enables users to jump to a specific page.
112
Image Display
Thumbnails Display
When performing quality control of documents, the thumbnails display allows users to see a thumbnail of each page
within a document, making it easy to navigate and select pages for different functions. To view thumbnails, click
either View > Thumbnails or View > Page and Thumbnails.
Selecting Pages
When dealing with large sets of document images, users will most likely be dealing with multi-page documents. This
requires the ability to select multiple pages of those documents to perform certain functions like deleting pages of a
document, deskewing individual pages of a document, or rotating certain pages of a document. LAW provides several
ways to select individual pages of a multi-page document. If working with the mouse, select pages from the
thumbnail display with a combination of the <Shift> and <Ctrl> keys. The selected pages appear highlighted in black.
113
Holding the <Ctrl> key while selecting the desired page with a left mouse click toggles the selection of that page.
Holding the <Shift> key while selecting the first and last page of a range selects all pages in that range. LAW also
allows users to select pages using only the keyboard to avoid switching back to the mouse. The spacebar toggles the
selection of the current page if either of the image controls (main image or thumbnails view) or the document list have
the focus. This makes it very easy to select pages if scrolling through the pages of a document using the arrow
keys. Users may also press Ctrl+A if the thumbnails display has the focus to quickly select all pages of the current
document
Note: The thumbnails display must have the focus in order for this to work. Pressing Ctrl+A will cause all
documents in the document list to be selected if the document list has the focus.
114
Image Display
See the Page-level Cleanup topic for details on enhancing pages of a document.
115
Viewing File Properties

Image Page Properties
LAW allows users to view the properties for both the current page and the entire image when working with records
with associated image files. The Page Properties dialog will provide the height and width of the image in both inches
and pixels, the resolution, the color format, and the compression type for the current page. To view the properties for
the current page, select Page > Properties from the main menu. An information dialog similar to the following will be
displayed.
Viewing Properties for Image Records

Users may also view the properties for the actual image file rather than the current page only. This information is
useful for determining file attributes, file size, and the actual file name for the image. For scanned or imported images
(non-ED), LAW does not display the actual file names for the images in the document list, but users may need to
determine the file names to troubleshoot certain issues. These file names consist of the "ID" field in the database
(zero-padded to 8 characters) with the image extension added. For images created via the TIFF Conversion batch
process, the actual file name will be displayed in the page-level PageFilename field.
To display the file properties for the current image, select Edit > Properties from the main menu. A standard
Windows file properties dialog will be displayed.
116
Image Display
Viewing File Properties for Native Records

For records that have associated native files but no associated images, the native file properties will appear when
choosing Edit > Properties from the main menu. If an image does exist in addition to a native file, the image
properties will be shown by default. However, if the user needs to view the native file properties for a record with both
an image and a native file, this can be accomplished by right-clicking the native file's hyperlink (located above the
Image display) and selecting Properties.
117
Manipulating Documents
Page-Level Cleanup
Image enhancements such as Deskew or rotating pages may be performed at a document- or page-level. Page-level
options are found in the Page menu, which also appears when right-clicking a page in the thumbnail display, with
certain options having buttons on the toolbar and/or shortcut key combinations as well.
Deskew
To manually deskew a page, select Page > Deskew (<F4>). If multiple pages are selected, then all selected pages
will be deskewed. If no pages are selected, only the current page will be deskewed. This is ideal when inspecting
documents on the page level and only a few unacceptably skewed pages exist.
See the Batch Processing section to learn about deskewing larger sets of documents.
Enhancing Images
Select Page > Enhance Image from the main form to launch the Select Image Filters dialog, providing image
enhancement options.
Black-Border Removal: The Black-Border Removal filter will remove black edges. This filter will pick up only even
black edges. If the black edge is uneven or slanted down the page, it will not be dropped. If receiving borders like this,
it is due to the scanner model being used and the scan area will have to be adjusted in order to remove them. The
scan area can be adjusted from the Scanner Settings dialog. Black borders left on pages can prevent LAW from
recognizing blank pages, so this filter should be selected if using the 'Drop Blank Pages' scan option. The black-
border removal filter can also be applied to multiple documents during Batch Processing.
Deskew: The Deskew process is used to straighten images that show a slant from their correct orientation. Skewing
occurs if the original document was unevenly pulled when it was fed into the scanner. Deskewing an image makes
the image contents more legible and can drastically improve OCR results. As such, it is a crucial step in the quality
control process.
Hole Removal: The Hole Removal filter removes black holes from pages such as those left by scanning 3-hole
punched pages. In order for holes to be removed, they must be complete, circular holes (partial holes will not be
removed).
Warning: When using the hole-removal filter, depending on the quality of the image and fonts, bold e’s and o’s can
appear to the filter as holes and be accidentally removed from the document.
119
Line Removal: The Line Removal filter removes black lines from pages and is subject to the same requirements as
the black-border removal filter. The filter will pick up even black lines only, so uneven or slanted lines will not be
dropped.
Noise Removal: The Noise Removal setting allows users to apply a filter to reduce the amount of random dots and
specks that appear on the scanned image. OCR results may improve if Noise Removal is performed on a document
before converting it to text.
Rotate Pages
LAW allows users to rotate pages in the event that one or more pages are improperly oriented. Pages may be
rotated automatically while scanning using the 'Output Rotation' setting (see Scan Options for more details). Pages
may also be rotated during the quality control process if they were not corrected at scan time or were acquired from
another source. Rotate one or more pages by selecting Page > Rotate Left (Ctrl+L), Rotate Right(Ctrl+R), or Rotate
180. If no pages are selected, only the current page will be rotated. If one or more pages are selected, all selected
pages will be rotated the specified direction. It is important to note that rotating an image is for viewing purposes only.
The main image window will display the current page with the new rotation setting; however, the thumbnail view will
display the page with the original orientation. To save the rotation for the image, select File > Save (Ctrl+S) and the
current orientation for all pages will be saved, updating both the thumbnail and page displays.
Note: Rotating an image that has been endorsed by LAW may result in undesired results if the endorsement is later
modified or removed. See Header/Footer Options for further information on endorsing.
120
Moving Documents/Pages
In the event that documents are saved to the wrong folder, LAW allows documents to be moved between folders.
This enables users to rearrange documents that may have been scanned into the wrong folder or group documents
from one or more folders together.
Moving Documents
To move one or more documents located in the same folder, select the document(s) to be moved and select Edit >
Move Document(s) from the main menu. The Edit menu is also available by right-clicking on the document list for
easy access. Multiple documents can be selected from the document list by holding the <Ctrl> key while selecting
individual documents, holding the <Shift> while selecting the first and last documents in a range, or pressing Ctrl+A to
select all documents in the current folder.
Note: Document list must have the focus in order for Ctrl+A to select all documents.
The following dialog appears and allows users to select an insertion point for the documents:
Once the dialog appears, browse normally between folders and documents and then click the Insert button when the
proper insertion point is found. The "Before Current" and "After Current" settings indicate whether the selected
documents should be inserted before or after the current document. If the documents are being moved into an empty
folder, this setting is ignored. If the documents are being moved into a folder with existing documents and a
document is not selected, LAW will prompt the user to select one.
Note: Documents can be moved within the same folder; however, the insertion point cannot be one of the selected
documents.
An alternative to selecting all documents in a folder and using the Move Documents function would be to use the
Move Folder function, located in the Folder menu. See the Establishing Folder Structures topic for more information.
Moving Pages
Pages can be moved within a single document by selecting a document and viewing the thumbnails display on LAW's
main interface. If the thumbnails are not currently visible, click View > Thumbnails or View > Page and Thumbnails
to display them.
Note: Moving pages in the thumbnails display is not currently supported for any image records stored as single-
page, such as images scanned while using the Serialized Storage Schema option or images converted to serialized
TIFF images via single document or batch TIFF conversion.
To move a page (or pages), select the desired page(s) from the thumbnail display, left-click on any of the highlighted
pages (the icon will change) and drag the cursor to the selected insertion point.
121
Warning: This feature does not currently move any page information (page ID, header/footer size, etc.), so pages
may need to be renumbered after the move. Also note that since header/footer size info will not be moved. Pages
should ONLY be moved within a document in which all or no pages have been endorsed with the same settings;
otherwise, unexpected results may occur if re-endorsed.
122
Deleting Documents/Pages
When dealing with large volumes of records, users may need to remove pages or entire documents for various
reasons. LAW allows both types of deletion directly from the main form. Users can delete one or more documents, an
entire range of pages in a document, or specific pages from a document.
Deleting Documents
To delete one or more documents, select the document(s) to be deleted from the document list. Multiple documents
can be selected by holding the <Ctrl> key down while selecting documents or by holding the <Shift> key while
selecting the first and last document in a range. Pressing Ctrl+A while the document list has the focus will select all
documents in the current folder. Once the desired documents are selected, choose Edit > Delete > Document(s) or
press the Delete key or toolbar button. The following verification screen will appear.
Clicking the Yes button will delete the selected document(s). Deleting a document deletes the image and/or native
file, the database reference, and any OCR files associated with that document.
Deleting Pages
Users have the option to delete the current page, a page range, or selected pages when deleting pages from a single
image record. To delete pages from a document, select Edit > Delete > Page(s) (Shift+Del). The Selected Pages
option will only be available if one or more pages have already been selected in the thumbnails display.
Note: If an image has associated OCR text, the deleted pages will be removed from the OCR as well (text-based
OCR only) and the remaining OCR pages will be renumbered if page identifiers are found (i.e., <<< Page 1 >>>).
Deleting Records from the Grid Displays

Another method of deleting records is to use one of the two available grid displays in LAW. To launch a grid, choose
Tools > Display All Records. Use caution when using this feature as anywhere from one record to all records in the
case may be selected at once and deleted from the grids. From the standalone grid, choose Edit > Delete Record(s)
to delete any selected records or use the Delete key or toolbar button. When utilizing the embedded grid, use the
Delete key or toolbar button.
For more information on the grids, see the following sections:
123
Launching the Grids
Customizing Grid Views
124
Splitting Documents
If a user scans several documents to a single record or determines that a document needs to be broken down into
sub-documents, the document(s) may need to be split. The Split Document function can be used to split a document
based on barcode pages, blank pages, every page, or selected pages. This function is commonly
used when scanning documents as quickly as possible and determining document breaks in a separate process. To
split a document, select the desired document and press (Ctrl+U) or Edit > Split Document from the main menu.
The Edit menu is also available by right-clicking on the document list for easy access.
Note: For non-ED records, the index information from the original document is applied to all new documents. This
may cause duplicate values if unique fields are defined, so any duplicate values will automatically be cleared. See
below for information on metadata handling for ED records.
If the selected image is an ED record, meaning the native file was imported with ED Loader and converted to TIFF in
LAW, the "Metadata Options" in the Split Document dialog will apply. Three Metadata Retention options for splitting
ED records are:
Discard all metadata - All field data populated during an ED import associated with the original record will
be discarded permanently, with the exception of the DocID field. This includes important values used to indicate
duplicate record status, metadata pulled from the native file, and ED Loader session information.
Note: All records created after the split (including the first record) will lose the value used to indicate the
file is an ED record. You will no longer be able to perform ED-related operations with these records such
as converting to TIFF and exporting native files.
Copy to all records - All index field data associated with the original record will be inherited by all records
created as a result of the split. The original native file will be associated with all new records. The native file is
NOT copied; all new records will point to the same file. For new records beyond the first record, this native file
link is created by placing the path to the native file into the "NativeFile" field in the LAW case. Because of this
behavior, if the newly split records are included in a TIFF conversion process, the same native file will be
converted for each of the records involved in the split.
125
Copy to first record only - All index field data associated with the original record will be retained by the first
record created as a result of the split ONLY. The other records created as a result of the split will have no
metadata (or other field contents generated during an ED import) with the exception of DocID. Other user-
defined index field data will be retained for all records.
Users also have the option to auto-number DocID values with a suffix for records created as a result of the split
operation. To use this feature, enable the "Auto number remaining DocID's" setting in the Split Document dialog and
enter the value in the "Starting Suffix" field. The default is ".002". The value in the "Starting Suffix" field value will be
appended to every record created as a result of the split with the exception of the first, or original, record. The suffix
will increment by one for each record.
Split Options
Barcode Break Sheets
If this setting is selected, the document will be scanned for barcode break sheets. The settings for the break sheets
can be specified from the Imaging tab of the Options form. If no pages with barcode breaks are found, the operation
will be cancelled. This setting may be useful if the 'Detect Barcode Breaks' scan option was inadvertently disabled
while scanning. LAW will split the document if a document break is detected or create a new folder if a folder break is
detected. The attachment barcode break sheet can also be detected using this feature and will create attachments
accordingly. For each barcode break sheet detected, the barcode will always be deleted from the image after being
processed. Click the Configure button for more supported barcode settings and types. See the Using Barcodes topic
for additional barcode information.
Blank Pages
This setting causes LAW to scan for any blank pages within the specified document. Any blank pages that are found
will be used as the separator pages and dropped. If no blank pages are found, the operation is cancelled. Click the
Configure button for blank page filter options.
Pristine White is used for perfectly (all white) documents and is best suited for digitally converted documents.
Scanned images may require a slightly less sensitive filter. Dirty White allows the document to contain a small
amount of (non-white) data e.g., speckles, creases, and folds (recommended for scanned documents).
Every Page
This setting causes every page of the document to be split into its own single-page document.
126
Selected Pages
This setting causes all selected pages to be used as the starting page of new documents. This setting is only
available if one or more pages are selected when the function is activated. Because the first page (of the current
document, prior to splitting) is automatically included as the start of the first sub-document, selection of this page is
not necessary. The "Drop selected pages" setting causes all selected pages to be dropped. This will also be the case
if barcode break sheets or blank pages as the separator pages are manually selected.
127
Merging Documents
LAW can merge two or more documents together in the event they were scanned as separate documents and later
discovered to be part of the same document. ED records, meaning records imported with ED Loader that have been
converted to TIFF in LAW, may also be merged with other image records in a case. Use caution when merging ED
records as important metadata and file links may be lost depending how the documents are merged. The documents
to be merged must be located in the same folder. If documents in different folders need to be merged, the Move
Documents function may be used to move them into the same folder.
To merge two or more documents, select the documents to be merged. If a single document is selected, the Merge
Documents menu item will not be enabled. Multiple documents can be selected from the document list by holding the
<Ctrl> key while selecting individual documents, holding the <Shift> key while selecting the first and last documents
in a range, or pressing Ctrl+A to select all documents in the current folder.
Note: The document list must have the focus in order for Ctrl+A to select documents.
Once the documents are selected, select Edit > Merge Documents or Ctrl+M. The Edit menu is also available by
right-clicking on the document list for easy access.
The documents will be merged in the same order they appear in the document list. To merge them in a different
order, move the documents prior to the merge operation. All Page ID information for the pages will be retained when
merging documents; however, the index information for the first document will be used as index information for the
new document. Be sure to verify this information after the merge.
Because LAW stores multi-page documents in multi-page image format, the image file has to be physically rebuilt,
with all pages from the 2nd to the Nth documents being appended to the first document selected. This can take some
time depending on the number of pages being merged. LAW can typically merge 100 pages in less than 5 seconds,
but as the number of pages increases, the average time per page increases, making the process somewhat slower
once users approach 1,000 pages. This process can be cancelled at any time by pressing the <Esc> key.
128
Inserting Document/Pages
LAW allows users to insert scanned documents, scanned pages, and existing images in the desired locations within
the current folder. For information regarding the Insert->E-Document feature, see the Inserting Electronic Documents
topic.
Inserting Documents
LAW allows users to insert documents in a particular place within the current folder by selecting Edit > Insert >
Scanned Document(s). Users can insert a document that was missed at scan time, for example. This feature is very
important because, unless documents are specified by a query, all processing functions (batch processing, exports)
are executed in scan order.
The Insert Document function can be used to insert multiple documents if the Detect Barcode Breaks setting is
enabled and the pages are separated by barcode break sheets.
The inserted document will be placed above the currently selected document.
Inserting Pages
Inserting a page is often used when a page, such as the back of a page, was skipped during the initial scan process.
To insert a page, first select the thumbnails display on the main form. If thumbnails are not displayed, click View >
Thumbnails or View > Page and Thumbnails.
129
LAW will always insert a page or document prior to the one highlighted. To insert a page, first select the page the
inserted page will precede and highlight it by pressing the space bar. In the example above, the new page will be
inserted between pages 21 and 22. Next, select Edit > Insert > New Page(s) from the menu.
Inserting Existing Pages

In addition to inserting scanned documents and pages, LAW also allows the insertion of existing images. To use this
feature, click Edit > Insert > Existing Page(s), browse to the image file to be inserted and click Open. The image will
be inserted as a document above the currently selected document.
For information regarding the Insert > E-Document feature, see the Inserting Electronic Documents topic.
130
Replacing Document/Pages
A document or page is commonly replaced when the image of a page or pages is poor. The Replace feature simply
replaces a page or document that already exists in the case.
Replacing a Document
Select the document to be replaced in the document list. Insert the replacement document into the scanner
and select Edit > Replace > Document from the main menu. Choosing OK at the prompt will replace the selected
document.
Both Replace->Page(s) and Replace->Document work in the same manner as the Insert > Page(s) function in
that the detection of barcode breaks will be disabled when using these features.
Replacing a Page
To replace a page, first select the thumbnails display on the main form. If thumbnails are not displayed, click View >
Thumbnails or View > Page and Thumbnails.
131
Select the page to be replaced and highlight it by pressing the space bar. Insert the replacement page into
the scanner and select Edit > Replace > Page(s) from the main menu. Choosing OK at the prompt will replace the
selected page. Multiple pages may be replaced similarly by holding down the <Ctrl> key while clicking on additional
pages to highlight them and then using the Edit > Replace > Page(s) function.
Replacing Documents with Existing Images

Documents may also be replaced with an existing image file rather than with a scanned document. To use this
feature, click the document to be replaced and choose Edit > Replace > Image from File(s). Browse to the
desired image file and click Open to replace the current document with the new image file.
132
Working with Attachments

In order to simulate original source documents, LAW allows documents to be identified as attachments to other
documents. This feature can aid in reassembly as well as provide logically grouping and relationships between
certain documents. When referring to attachments, two principal types of documents exist: parent documents
and attachments (children). Any document that is not attached to another is said to be a parent or standard
document. The two primary ways to manually assign documents as attachments are at scan time using scan
functions or by assigning existing documents as attachments via the Edit menu. See the section on Scanning in LAW
for more information on assigning attachments at scan time. Attachments will be assigned automatically when
importing records with attachments via the ED Loader (i.e. e-mails with attachments), LAW case import, and load file
import (Z-Print, Summation (requires "ParentID" field for attachment records), IPRO, and EDRM only).
Attachments must always immediately follow their corresponding parent, allowing visual identification of documents
with attachments in the document list. Attached documents' ItemNo values will appear indented in the document list
to indicate they are attached to the previous document.
(In this figure, document #0002 is attached to document #0001 and document #0008 is attached to document #0007)
Adding Attachments
To manually add an attachment or attachments, select the documents to be attached in the document list and select
Edit > Attachments > Attach to Previous (Shift+Ins). All selected documents will be attached to the previous
document. The documents to be attached must be consecutive and on the same level if attaching multiple
documents. This means that all selected documents must be currently unattached and cannot have attachments of
their own. Because the documents are always attached to the previous document, if the parent and documents to be
attached are not consecutive, the documents must be rearranged so the documents to be attached are positioned
immediately after the designated parent.
Removing Attachments
To remove an attachment from its parent, select Edit > Attachments > Detach Document. Although multiple
documents may be selected, only the current document will be detached. To detach all attachments from a
document, select any one of the attachments and then select Edit > Attachments > Detach All (Shift+Backspace).
Note: When removing individual attachments from a document with multiple attachments, if an intermediate
attachment is removed, it will be shifted down in the document list to the position immediately after the last
attachment for the current parent. This is necessary to ensure parent/children integrity.
133
Validating Attachments
This function performs checks on the database to ensure that documents marked as parents have children, and
documents marked as children have parents. LAW automatically corrects any errors found and writes to a log file for
later verification. To perform the validate function, select Edit > Attachments > Validate.
134
Annotations
Annotations allow users to make visible changes to documents by creating filled boxes, lines, circles, etc. to hide or
highlight important information in a document. All annotation functionality can be accessed from the Tools >
Annotations menu.
Creating Annotations
Select Tools > Annotations > Toggle Toolbar from the main menu or press Ctrl+T to display the available
annotation tools.
To create an annotation, select the image in the preview window to activate the toolbar, select the desired tool, and
then apply the tool to the image. Any annotation changes or additions are saved with the document when the
document loses focus. The user will be prompted to save the changes if any have occurred. The 'Save by Default'
setting will automatically save the changes made to the document, eliminating the save prompt.
Note: Annotations can ONLY be added, deleted, or modified if the annotation toolbar is displayed. Displaying the
annotation toolbar changes the mouse behavior from image to annotation mode.
Warnings: Merging annotations with color pages will convert the image to B&W. Pop-up note annotations will be
merged as an image icon.
Viewing and Printing Annotations

Once an annotation has been created on a document, the user has the choice to display or hide the annotations on
all documents by selecting the Hide Annotations option (Shift+F12). This option not only affects how the annotations
are displayed but how they are printed as well. When the annotations are hidden, the documents can be printed in
their original form. If the annotations are visible, any documents containing annotations will also be printed with the
annotations visible. A 'Do not print annotations' option also exists in the Print options in the Batch Process utility to
allow the user to choose not to print annotations, whether currently visible or not.
Merge Annotations
This function allows users to permanently mark a document with the annotations that have been applied to the
document. To perform this function, select Merge Annotations under the Tools > Annotations menu (Ctrl+F12).
Note: Only annotations on the currently selected page will be merged. If annotations exist on other pages of the
document, the Merge Annotations feature will need to be performed on each page.
Merging a color annotation onto a B&W document will result in the annotation being converted to a B&W annotation
to match the color properties of the document. To preserve the color information of the annotation, the images will
need to be exported out of LAW using the Merge Annotations + Retain Color settings in the Options tab of the
Export Utility.
Caution: Once the annotations have been merged with the document, they are "burned" onto the image and
CANNOT be removed.
135
Editing Annotation Tool Properties

Each annotation object can be selected prior to being merged and properties of that object can be modified. To
modify the objects' properties, select the object on the image (annotation toolbar must be active).Then, right-click and
select Item Properties. A form will appear and provide options about the specific object; for example, fill colors or line
thickness. Most commonly used tool properties can also be modified by selecting Tools > Annotations > Default
Properties.
Sticky Mode
Sticky Mode (Tools > Annotations > Sticky Mode) keeps the currently selected tool available after applying the tool
to the image. If Sticky Mode is not selected, the mouse cursor will return to the selection tool after each annotation is
applied.
136
Working with Native Documents

Extracting Page Counts
LAW has the ability to provide estimated page counts for most of the common native file formats that have been
imported into a LAW case via the Electronic Discovery Loader ("ED Loader"). These page counts may be obtained
without the requirement of printing to paper or converting the native file to TIFF. LAW performs the page count
extraction by opening the files in the native application listed in the SourceApp field and retrieving the page count
value. Since some source applications are unable to provide an exact page count without actually sending the
document to a printer, the page counts returned using this process should only be considered an estimated page
count. To obtain a more accurate page count, convert the native files to TIFF.
To utilize this feature, return records to the standalone grid display by running a query using Query Builder or clicking
Tools > Display All Records. For more information, see Launching the Grids. Only records visible in the standalone
grid will be processed. Therefore, the process can be executed on all records in the case at once or on certain
subsets only. Once the grid has been launched, click Tools > Extract ED Page Counts from the grid menu. A status
window will appear and update throughout the process, indicating the total number of files, files processed thus far,
the number of errors if any have occurred, elapsed time, and remaining time. Once the process has completed, the
Page Count Extraction Complete message box will contain the elapsed time and speed, total number of files, pages,
and errors. If any errors had occurred during processing, the user will be prompted to view the error log after clicking
OK on the message box.
Note: Certain source applications do not support page count extraction, such as Microsoft Outlook and Quick View
Plus. See the table below for a complete list. If a page count cannot be extracted, a warning message will be
returned to the error log. Also, the page counts for items with a source application of Microsoft Excel will be
estimated based on the TIFF/E-Print Excel print options currently set in the LAW case (Tools > Batch Process >
Options > TIFF Options > Excel).
Note: All source applications supporting page count extraction may return an estimated page count. Converting the
native files to TIFF or printing to paper will yield a more accurate page count result.
Source Applications Supporting Page Count Extraction:
Source Application Supports Page Count Additional Notes

Extraction
Adobe Acrobat Yes
AutoVue Suite Yes
Binary/Hex Printer Yes
Corel WordPerfect Yes
eDrawings Viewer Yes
Image Printer Yes Reads the page count from the image.
Internet Explorer Yes Uses the alternate HTML engine to calculate

page counts. Therefore, the output may not
exactly match the output printed with Internet
Explorer.
137
Microsoft Excel Yes
Microsoft Outlook No
Microsoft PowerPoint Yes
Microsoft Visio Yes
Microsoft Word Yes
Quick View Plus No
Shell Printer No
Snapshot Viewer Yes
Text/RTF Printer Yes
VoloView Express Yes Always returns a page count of 1.
<No Source Specified> No Always returns 1 page to account for a slip

sheet.
The resulting page count estimates are logged for each record in the EDPages field. This field is created
automatically if a case is enabled for electronic discovery when creating a new case in LAW. The EDPages field is
also used to store the number of pages actually printed to paper when using the E-Print batch process. If this field
does not exist in the case, it may have been created with an older version of LAW that did not create this field
automatically. If this occurs, create the field manually using the field editor (Index > Modify Fields). Name the field
EDPages, choose Document-Level as the table, and Numeric as the field type. The absence of the EDPages field
can also indicate the case is not ED-enabled. This feature is not supported for non-ED records.
If an error occurs during the page count extraction process, the error message generated by the native file will be
logged in a log file and the EDPages field will be set to value of zero pages. Since the default value of the EDPages
field is empty, the query "EDPages Is Empty" will return all of the records in the case which have not been processed
by the page count extraction process. This is useful for resuming the process on a case.
The page count extraction process, by default, is a multi-threaded process, where multiple files are being scanned for
page counts at the same time. To do this, multiple instances of the print server (lawprnsrvr.exe) are launched, one for
each thread. Each print server then loads the source application needed for processing its native file into memory and
returns the page count of the file back to LAW. In some situations it may be necessary to adjust the number of
threads LAW is able to use for this process. This adjustment can be made using an INI setting located in the
Law50.ini file in the LAW50 installation directory.
[EDPageCount]
Threads=0
The value of 0 uses the default thread count which is the number of local CPU cores multiplied by 2. For example, if a
dual core PC is used, 4 threads are created by default. A value of 1 will force LAW to create one thread, 2 will create
two threads, and so on. Using a high number of threads can lead to decreased performance due to the increased
resources used by each thread.
Each thread utilizes a default timeout value of 60 seconds. If a document takes longer than 60 seconds to return a
page count, the thread will log a timeout error and skip to the next document. For example, some large HTML files
138
containing web content may take longer than 60 seconds to load. The default timeout value can also be adjusted
using an INI setting in the Law50.ini file located in the LAW50 installation directory.
[EDPageCount]
Timeout=60
Note: If the [EDPageCount] section already exists in the Law50.ini file, simply add the key under the existing
section. For example:
[EDPageCount]
Threads=0
Timeout=60
139
Launching Native Files

Once native documents are loaded via the Electronic Discovery Loader, the files may be launched from within LAW in
any application installed on the current computer. Files may be launched using any of the three methods:
Using the native file hyperlink located above the Image display
By right-clicking the native file hyperlink and choosing Open
Using the Open File button located above the native file hyperlink
Launching Files Using Hyperlinks

When a user clicks the hyperlink to launch a native file, the file will launch in the application that is specified for that
document in the SourceApp index field. This field is populated automatically during an ED Loader session and is
based on the specifications in the file type database. If the value is set to "<No Source Specified>", LAW will attempt
to launch the file in the application assigned to this file type in the operating system. If no application is assigned in
the OS, LAW will attempt to launch the file in a text editor.
The native file may also be launched by right-clicking the hyperlink and selecting Open. The application to open the
file will be determined using the methods explained in the previous paragraph.
Launching Files Using Open File Button

The Open File button is similar to the hyperlink in that it will launch the native file using the application specified in
the SourceApp field, in the operating system, or a text editor (see above section for details). However, this option
provides more control as it allows the user to choose the application with which to open the native file. To choose an
application, click the downward pointing arrow located beside the Open File button. Next, choose one of the popular
applications in the list to view the file in that application or select "Choose Program..." to select any other application
installed on the computer.
Another option available in the Open File drop-down list is Change Source Application. This option can be used to
change the value listed in the SourceApp field for the current document. The change will affect the TIFF/E-Print
process since the SourceApp values determine the application used when printing or converting the file.
140
Locating Native Files in the Case Folder

Native files are stored in a special folder structure within the case folder when imported using the Electronic
Discovery Loader. These files are not stored in the folders that appear in the folder list on the main form but are
instead stored within the <case root>\$EDD\$NativeFiles folder.
If a user needs to quickly locate a native file outside of LAW, the easiest method is to right-click the hyperlink (located
above the Image display on the main form) and select the Open Containing Folder option. This launches the folder
that contains the native file with the native file already selected for easy access.
Another method of locating a native file for a particular record is to view the ID field in LAW. For records containing
native files, the ID field value will make up the folder structure for the native file (relative to the $NativeFiles folder).
For example, if a record's ID value is 1234, then the path to the native file would be <case
root>\$EDD\$NativeFiles\00\00\12\34.NTV.DOC (file is a Word .DOC file in this example).
Note: ID values are padded with zeroes to form an 8-digit number when used for this purpose; for example, an ID
value of 1 for a native record would result in a native path of 00\00\00\01.NTV.DOC.Understanding how this
function works will allow users to browse to the native files when not using the Open Containing Folder option.
Native File Review Mode

The Open File drop-down list includes options for reviewing common file types quickly and efficiently using a
combination of LAW and either Quick View Plus or AutoVue. The selected review mode application needs to be
installed to use this option. If using Quick View Plus version 9 or later, please see Avantstar's license agreement prior
to using this application with LAW.
Selecting Quick View Plus Review Mode from the Open File drop-down list opens the native file in Quick View
Plus. Selecting AutoVue Review Mode opens the file in AutoVue.
Selecting the Synchronize Native View option in addition to a review mode automatically opens the native file in the
selected review mode when a new record is selected. Each record opens in the same window, closing the previously
opened record. The active record's DocID is displayed in the title bar.
When selecting non-EDD records, the native file review mode options are ignored since native files do not exist for
these record types.
Native E-Mail Review

Lotus Notes and Outlook e-mail messages may be launched in their respective native applications after import into
LAW, regardless of how ED Loader converted the file during the import process. This feature supports top-level, or
parent, messages in mail stores as well as top-level loose messages (MSG and EML) on disk.
To enable this feature, click the arrow to the right of the Open File button located above the image display and then
click Review Parent E-Mails Natively. With the option now checked, LAW will open e-mails in either Microsoft
Outlook or Lotus Notes when launching the files via the hyperlink above the image display or the Open File button.
Note: The mail stores and loose messages MUST be in their original locations from which they were processed by
the ED Loader. If they have been moved, LAW will not be able to locate them when attempting to launch the native
e-mail. If this occurs, an error message will appear stating the file could not be found and then LAW will launch the
version of the file located in the <case root>\$EDD\$NativeFiles folder.
E-mails can also be launched natively without enabling the option above by right-clicking the hyperlink above the
image display and choosing Open Source E-Mail Natively.
141
Inserting Electronic Documents

Inserting an electronic discovery record in an existing folder of records may be useful to add any skipped files or
when dealing with unsupported embedded files.
Four insert modes are available:
Edit > Insert > E-Document(s) > Before Current - Inserts record(s) before currently selected record.
Edit > Insert > E-Document(s) > After Current - Inserts record(s) after currently selected record.
Edit > Insert > E-Document Attachment(s) > Before Current - Inserts record(s) as attachment to the
record before the currently selected record.
Edit > Insert > E-Document Attachment(s) > After Current - Inserts record(s) as attachment to the
currently selected record.
After selecting one of the above options, the ED Loader will appear in "Insert Mode."
For information about placement of the inserted documents, click the Details button. The Insert Mode Details dialog
will appear.
142
This screen will indicate where the document is to be placed. Ensure the information is correct and then click OK.
Select the file(s) to be inserted to add them to the Source Queue. Set any desired options in the Settings tab. Click
Start and click OK on the Confirm Settings dialog to initialize the import process.
Note: The Default Target Folder setting cannot be configured inserting e-documents. The value will be set to the
folder that was selected when choosing to insert an e-document.
The selected file(s) will be imported into the specified location in the case.
143
Single Document TIFF Conversion

Single document TIFF conversion, also referred to as "manual TIFFing", makes it easy to review a native file, make
adjustments if needed, and process (or re-process) to TIFF. Once printed, users can review the image and choose to
either save or discard it. Saving the image will commit the image to LAW by either replacing an existing image or by
inserting the image, depending on whether or not an image previously existed for that record.
This feature provides a simple method of opening and printing otherwise unsupported file types, provided the native
application is installed on the machine. This feature is also useful when reviewing and re-processing "problem"
supported file types.
Multiple options should be reviewed prior to using this method of converting to TIFF images. Decide whether to store
the resulting image as serialized (single-page) or multi-page and whether or not to generate printed text (text created
during a TIFF conversion when using the LexisNexis Image Driver). Determine the desired color reduction setting and
whether or not to drop blank pages. Select the desired options by clicking Tools > Batch Process. From the Batch
Processing dialog, click Options > TIFF Options. Select the TIFF Output category. Set the options as needed and
then click OK. Close the Batch Processing dialog. The selected options will now apply to the single document TIFF
conversion process in addition to the batch TIFF Conversion process.
To utilize the single document TIFF conversion feature, select a document to be printed from its native application.
Launch the native file by clicking the hyperlink or by clicking the Open File button (both located above the Image
display on the main form). If necessary, make adjustments to the settings and then click the Print option within the
native application. When the Print dialog appears, choose the Informatik Image Driver or the LexisNexis® Image
Driver and click Properties to adjust settings, as needed. Print the file.
Once the file has been converted to a tiff image, the Image Acquired dialog will appear.
144
If the image is acceptable, click the "Save the Image" button ( ) to commit the image to the selected record.
If the image is unacceptable, click the "Discard the Image" button ( ).
145
Grid Displays
Grid Displays
Launching the Grids
The grid displays are often used for quality control, filtering, viewing and working with query results, and tagging.
Before reviewing data and documents, it is important to become familiar with the grid displays in LAW. There are two
grids available: standalone and embedded. The standalone grid is launched in a separate window, while the
embedded grid is part of LAW's main user interface.
Note: The grid displays do not currently support Unicode. However, Unicode data can be displayed by resting your
pointer over a cell containing Unicode. The Unicode data appears in a pop-up text box beside the cell.
Specifying the Preferred Grid

A user's preferred grid view may be set as the "default" grid by setting the 'Send query results to grid on main form by
default' option in the Preferences tab (Tools > Options). This setting will determine which grid view is displayed
when launching from the main toolbar or using certain menu items. If checked, the embedded grid will be launched by
default.
147
Methods of Launching the Grids

The setting in LAW Preferences (see above) will determine which grid view is displayed when launching a grid using
one of the following methods:
"Globe" button on the main toolbar ( )

Tools > Display All Records (returns all records in current LAW case)
Folder > Grid View (returns records in currently selected folder)
Folder > Grid View (Recurse) (returns records in current folder and its subfolders)
The embedded grid may also be launched by clicking the Grid View button on the main form (located beside Index).
LAW will then prompt the user to run a search to populate the grid. If Yes is chosen, the Database Query Builder will
appear. Check the box to Send results to grid on main form, add additional search criteria (if desired) and click
Execute.
If no additional search conditions were specified, all records will be returned to the embedded grid. If the option to
"Send results to grid on main form" is not selected when using the Query Builder, the search results will be returned
to the standalone grid.
148
Grid Displays
Note: Full text searches cannot be returned to the embedded grid. If the "Full text search" check box is selected,
the "Send results to grid on main form" option will be disabled.
149
Customizing Grid Views

LAW allows users to customize each grid to meet individual or group preferences and save the desired view to a
user-, shared-, or global-level profile. The profile will store the visible fields, order of the visible fields, column width,
and row height (see the "Working with Columns and Rows" section in the Grid Functions topic for information about
sizing columns and rows). In each LAW case, a Default profile, or view, will be used when the grids are initially
launched. Use the steps below to create a new "view" for the grids.
Creating Grid Profiles

As mentioned above, grid profiles are used to store customized grid settings. A "Default" view is provided with each
new case and is displayed until a new profile is created and set as the default. To create a new view, or profile,
launch one of the grid displays (see Launching the Grids) and then click Grid Views > Save As. Profiles may also be
created by choosing Grid Views > Manage Views > File > Save As.
When the Save As dialog appears, choose a storage level and name for the profile.
Three storage levels are available when creating field profiles:
150
Grid Displays

Shared - Available to any user in the LAW case in which the profile was created. If a profile is shared, LAW
will automatically display "(Shared)" after the profile name.
Global - Available to any user in any LAW case. If a profile is global, LAW will automatically display
"(Global)" after the profile name.
The name of the profile can be no more than 50 characters and must be a valid file name, meaning it cannot contain
any invalid characters such as question marks or colons. Click Accept to create the profile.
The user and shared profiles are stored in the case folder structure ($UserData), while global profiles are stored in
<application path>\Shared. The default storage location for global profiles can be changed via the Preferences tab in
Tools > Options.
Switching Profiles
Once one or more profiles have been created (in addition to the default), users may switch between profiles within the
active grid. To switch, select View > Grid Views from the menu bar in the grid display (or click Grid Views on the tool
151
bar) and choose the desired profile from the list. The profile that is active when the grid display is closed will become
the new default for the current case or current user (depending on the storage level chosen when the profile was
created). An alternate profile may also be selected by clicking Grid Views > Manage Views, selecting a profile from
the Views section and clicking Done.
Selecting Fields to Display

Grid profiles will store all fields visible in the grid. To choose fields to display, click View > Field List. The Field List
may also be accessed by right-clicking on any column header. When the Field List dialog appears, select or deselect
the boxes beside the fields. To show all or hide all, right-click within this dialog and choose either Show All Fields
(Ctrl+A) or Hide All Fields (Ctrl+X).
Moving Fields
The order in which the fields are displayed in the grid may be adjusted by the user and saved to the current profile if
desired. To move a field, click and hold the column header for the field to be moved and then drag the field to the
desired location. Red arrows will indicate the new field placement prior to "dropping" the field (or releasing the mouse
button). To move a field to the right-most position in the grid, right-click any cell in that column and choose Send
Column Right-most. To move a field to the left-most position in the grid, right-click any cell in that column and choose
Send Column Left-most.
Changing Grid Colors

Row colors (odd and even), grid line colors, and grid text colors may be customized for each profile. To change the
colors from the grid display, choose Grid Views > Manage Grid Views > Tools > Grid Colors.
152
Grid Displays
When the Grid Colors dialog appears, make the desired selections for each item and click OK. The Reset button will
return the colors for all items to the LAW defaults.
Deleting Profiles
User-defined profiles may be deleted from the grid displays. If a profile's scope is Shared or Global, then it may be
deleted by any user that enters the case. If a profile was created at a user level, only that user will be able to delete
the profile.
To delete a profile, launch a grid display and click Grid Views > Manage Views. Choose the profile to delete from the
Views section and click Edit > Delete.
153
Grid Functions
The grid displays are often used for quality control, filtering, viewing and working with query results, and tagging.
Before reviewing data and documents, it is important to become familiar with the grid displays in LAW. There are two
grids available: standalone and embedded. The standalone grid is launched in a separate window, while the
embedded grid is part of LAW's main user interface. This topic will cover a number of functions available within these
grid displays.
Selecting Fields to Display

Grid profiles will store all fields visible in the grid. To choose fields to display, click View > Field List. The Field List
may also be accessed by right-clicking on any column header. When the Field List dialog appears, select or deselect
the boxes beside the fields. To show all or hide all, right-click within this dialog and choose either Show All Fields
(Ctrl+A) or Hide All Fields (Ctrl+X).
Sorting Records
Once records have been returned to the embedded or standalone grid, users may sort the records based on visible
index fields. Fields may be displayed or hidden by clicking View > Field List (standalone grid only) or right-clicking any
column header and then choosing the desired field or fields from the list.
Sorting by a Single Index Field

To sort records using a single index field, click within any cell in the column for the desired field, and then click either
the Ascending ( ) or Descending ( ) button located on the grid toolbar or choose Tools> Sort Records >
Ascending | Descending (standalone grid only).
Sorting by Multiple Index Fields

The standalone grid offers an Advanced Sort feature which allows sorting by up to four index fields at one time. A
different sort direction may be specified for each of the four fields: ascending or descending. To access this feature,
click Tools > Sort Records > Advanced Sort or click the Advanced Sort button on the toolbar ( ) from within the
standalone grid display. The Advanced Sort dialog will appear.
154
Grid Displays
Choose fields from one or more of the drop-down lists; memo fields cannot be sorted and therefore will not appear in
the lists. Records will be sorted in the order in which they appear in this dialog. For example, in the above image,
records would first be sorted by DateSent in Ascending order, then by From (Descending), then by EDFolder
(Ascending), then by Importance (Descending). Click OK to apply the sort to the current set of records.
Saving Records to File

The visible field data associated with records displayed in the grids may be saved to a *.TXT or *.CSV file. This
feature can be useful for a number of reasons including import into a different application or review by another party.
Only fields visible in the grid will be included in the output file. See the "Selecting Fields to Display" section in this
topic to learn how to display and hide fields.
Once the desired records have been returned to the grid and fields have been chosen, click File > Save or click the
Save button in the toolbar. The Save Options dialog will appear.
155
In the Output Filename section, click Browse to change the location and file name of the output file if the default
value (<current case path>\results.<ext.>) is not acceptable. In the Text format drop-down, choose the desired
format for the output file. The available options are: CSV (Comma delimited), Text (Tab delimited), Unicode UCS-2
(Tab delimited), Unicode UTF-8 (Tab delimited). The text format may also be specified from the "Save as type" drop-
down after clicking Browse to choose a new location and/or file name
Note: In order to view Unicode in Microsoft Excel, the Unicode UCS-2 (Tab delimited) text format must be used.
The Documents section is used to specify if all records in the grid should be written to the output file or if only
selected records should be written. The Save all records option would save all records currently shown in the grid to
the output file. The Save selected records option would include any records that are highlighted in the grid. If no
records are highlighted, then only the currently selected record (indicated by an arrow beside the left-most column)
would be included in the output file if this option is chosen. The total number of records to be written to the file will be
shown in this section below the two aforementioned options.
The Override Default Delimiters option can be used to modify the delimiters of the output file rather than using the
default delimiters set for the selected text format. Click the box to enable the delimiter selections, then specify the
desired characters for Field (separates each field in the file), Text (wraps the values in each field), and Newline (to
replace hard and soft returns found within the field values). To restore LAW's default delimiters and discard any
changes that were made, click the Restore Defaults button. The default values can also be restored by deselecting
the Override Default Delimiters option.
Once the above options have been set, click the Save button to create the file. LAW will prompt to open the TXT or
CSV file for viewing after the file has been written.
Printing Records
The visible field data associated with records displayed in the grids may be printed to file or paper. Only fields visible
in the grid will be included in the output. See the "Selecting Fields to Display" section to learn how to display and hide
fields. Use the Print Preview
To print only selected record(s), first choose the records to include by selecting a single row (or cell in a row) or by
using the Ctrl or Shift keys and clicking on desired rows. Then, choose File > Print > Print Selected Records Only
in the standalone grid or click the Print button in either grid toolbar and choose Print Selected Records Only.
Choose a printer, change any necessary printer settings, and click OK.
156
Grid Displays
To print all records visible in the grid, choose File > Print > Print All or click the Print button in either grid toolbar and
choose Print All. Choose a printer, change any necessary printer settings, and click OK.
Batch Updating
LAW allows users to track information about records to aid in retrieval. This information is stored in the index fields
created when setting up the case. LAW allows multiple documents to be updated with the same values at one time.
To update fields for multiple documents from within a grid display, launch the desired grid using one of the methods
discussed in the Launching the Grids section. Return only records that are to be updated using the Batch Update
feature.
To update fields for multiple documents, click Edit > Batch Update in the standalone grid or click the button in
the standalone or embedded grid toolbar. The Batch Update dialog will appear. Click within the cell in the Field
column to force the arrow to appear which allows the selection of a field that can be edited from the drop-down list.
Choose a field and then enter the desired Value in the cell beside it (Value column).
To update multiple fields at once, click the Add Field button, choose an additional field from the new cell that appears
in the Field column, and enter a value. The Remove Field button will allow the removal of an update entry from the
dialog.
The Auto-increment selected text/memo fields will cause any values entered for text or memo type fields to
increment by one for each updated record. This feature could be used to assign a new, unique identifier to all or a
subset of documents in a case.
After entering all desired information for the current set of records, click OK. LAW will report the number of records
updated.
Deleting Records
Records in LAW, along with their associated files and field data, can be permanently deleted from the standalone
grid. To delete a single record, click within a cell in the row of the record to be deleted, or highlight the entire row, and
157
then click Edit > Delete Record(s) in the standalone grid. Click Yes on the warning message box to permanently
delete the record or records.
Warning: Use extreme caution when deleting records as the operation CANNOT be undone.
Viewing Attachment Fields

Four fields containing information related to attachments can be generated by clicking View > Attachment Fields in
the standalone grid. Due to its dynamic nature, the data is collected and placed into a table that is built on the fly
when this setting is invoked and therefore, the fields may not appear for several seconds (longer on larger cases).
The percentage complete will appear in the title bar of the standalone grid. The four fields displayed are: BegAttach,
EndAttach, AttRange, and Attachmt. For more information about these fields, please see the Field Descriptions topic.
Viewing Document and Page Totals

The number of documents currently displayed in the grid is shown at the bottom of the dialog in between the
navigational arrows. If a page-level query was executed, this number will be the total number of pages instead. To
display both the document count and the total of pages associated with the documents in the current query, click
View > Doc/Page Totals within the standalone grid. The document and page counts will then appear in the lower
right corner of the grid (e.g., Documents: 660 / Pages: 21,166). This menu item controls this feature for both the
standalone grid and the embedded grid.
Warning: Since additional time is needed to calculate the total documents and total pages information, this feature
will introduce a slight delay, relative to the size of the case, when opening either grid or when returning records from
the query builder. To prevent this delay, simply disable this setting via the standalone grid under View > Doc/Page
Totals.
Working with Columns, Rows, and Cells

Columns and rows can be manipulated in a number of ways to make certain aspects of quality control easier and
more efficient.
Rows may need to be adjusted in order to see multiple lines of data in the cells. To resize the rows, position the
mouse pointer between two rows until the resize cursor appears and then click and drag until the desired row height
is obtained.
Individual columns can be sized in a similar manner. Position the mouse pointer to the right of the column to be sized
and then click and drag until the desired width is obtained. If unable to position the mouse in this manner due to the
column lining up with the edge of the grid window, right-click a cell in that column and choose Shrink Column to
Window first and then resize the column if needed.
To move columns, or fields, to another location in the grid, click and hold the column header and then drag the field to
the desired location. Red arrows will indicate the new field placement prior to "dropping" the field (or releasing the
mouse button). To move a field to the right-most position in the grid, right-click any cell in that column and choose
Send Column Right-most. To move a field to the left-most position in the grid, right-click any cell in that column and
choose Send Column Left-most.
The contents of a field, or column, can be copied into another column in the grid. After ensuring a field to accept the
incoming data has been created and the desired grid has been launched, highlight the source column by clicking the
column header. Click Edit > Copy. Next, highlight the target column by clicking the column header, and then click
Edit > Paste. Click Yes to proceed with the copy. LAW will not allow the copying of data into locked or system fields.
Warning: Copying data into a field of a different type (e.g. memo to text) in this manner could result in a loss of
data.
158
Grid Displays
Building Control Lists

Control lists can be used to import text files into CT Summation or any other application that supports this
functionality. This feature generates a *.LST file containing the record's BegDoc# and the path to the associated text
file. and, if directed to do so, will export one form of each document's associated text (OCR, printed, or extracted, in
that order) to a new location. A control list may also be created via the Export Utility in LAW.
To create a control list, launch the standalone grid (see Launching the Grids), and click Tools > Build Control List.
The following message will appear:
Selecting No will link the control list text path to the current location of the text. If Yes is selected, LAW will ask for a
new location to which the text files will be copied. Click New Folder to create a new folder for the text files. By default,
LAW will place no more than 1,000 text files in the selected output folder. If more than 1,000 files are found prior to
the text export, a notification will appear (explained below). This files per folder limit can be modified by placing the
following setting in the <application path>\law50.ini file:
[Summation]
ControlListFileLimit=1000
If the [Summation] section already exists, then just place the ControlListFileLimit key below the existing section.
Change the value of 1000 to the desired value. After invoking the Build Control List menu item and choosing Yes to
export the text files to a new location, if LAW determines the number of text files will exceed this value, the following
message will be displayed:
The number in parentheses will match the value in the INI setting (see above) or the default of 1,000. Specify the
name of the first folder to hold the exported text files. Once the specified number of text files are placed in this folder,
LAW will automatically create a sequential folder to hold the next set.
If a case is enabled for electronic discovery ("ED-enabled) and the records in the standalone grid have associated
images, LAW may prompt to choose between the DocID or BegDoc# fields for the image tag (or document identifier).
159
If the BegDoc# is not populated for the images in an ED-enabled case, the DocID field will be used automatically.
Lastly, LAW will offer to launch the control list file once it has been created. The file extension is .LST and can be
viewed in any text editor.
Creating Outlook PST Files

LAW can create Outlook PST files for messages imported from Outlook mail stores, loose Outlook messages (*.msg),
and loose RFC-822 messages (*.eml) on disk. This feature is located in the standalone grid which means only
records currently loaded in the grid will be included, provided they match one or more of the aforementioned
message types. Only top-level messages and loose e-mail items will be added when creating a store - any
attachments to these messages will be part of the parent items, regardless of whether or not these attachment
records are shown in the grid.
To create an Outlook PST file, first load the desired records into the standalone grid (see Launching the Grids). Next,
click Tools > Create Outlook PST.... Provided supported message records exist in the grid when this feature is
invoked, the Create Outlook PST dialog will appear next. If no supported message records exist in the record set,
LAW will report this in a message box and return to the grid. If both exist in the grid at the same time, LAW will ignore
the unsupported files and proceed with the launching the Create Outlook PST dialog.
160
Grid Displays
Click the Browse button to specify a path and file name for the new PST. If an existing PST is selected, LAW will
present an option to either append to or overwrite that file.
The Root Output Folders area below the output path contains two columns. The first column will display "Loose
Messages" for any supported loose e-mail message records found in the grid and will display the file name (minus the
extension) of the original PST mail store from which the store-based records originated. These values will be used as
the root folders in the output PST file. To change any of these default folders, simply key the desired values into the
text box or boxes.
The second column will display <Loose E-Mails on Disk> for the supported loose e-mail message records found in
the grid and will display the path to the original PST mail store for any store-based records. The Create Outlook PST
feature creates new PSTs (or appends existing) by accessing these original stores and/or loose messages.
Note: The mail stores and loose messages MUST be in their original locations from which they were processed by
the ED Loader. If they have been moved, LAW will not be able to locate them and the new PST files cannot be
generated. LAW will present a list of mail stores that have been moved when invoking the menu item in the grid.
Once the output path and root folders have been specified, click OK to begin generating the PST. The title bar of this
dialog will display the percentage completed and once the process is complete, LAW will report the total number of
top-level messages added, the number of errors, elapsed time, and average speed. If errors occurred during the
process, the error log may be launched from the status screen as well. Error logs are stored in the root of the case
folder in a file named pst errors.txt.
161
Resetting Text Flags

The Tools menu in the standalone grid will allow the resetting of both OCR flags and full text index flags for
documents. These functions are explained in other topics in this help file. For information on resetting OCR text flags,
please see the Flagging Documents/Pages for OCR topic. For information on resetting OCR text flags, please see
the Full Text Indexing topic.
Spell Checking
The spell check feature can be used to locate misspelled words within index fields in the LAW case. Prior to starting
the spell check, ensure the user-defined, unlocked field to be searched is visible in the standalone or embedded grid
display. System and locked fields cannot be accessed for the spell check. Next, select any cell in the column and
then click Tools > Spell Check in the standalone grid or click the following button in the toolbar in either grid:
LAW will launch the Spelling Check dialog to display misspelled words which can be ignored, replaced, or added to a
custom dictionary file (custom.dic in LAW50 folder).
Generating an Index Summary

An index summary can be performed from the standalone grid. When invoked, this feature will display a message box
containing three pieces of information: total number of documents currently displayed in the grid, total number of
pages associated with the documents currently displayed in the grid, and the total number of fields associated with
the currently displayed documents that are coded with information. To generate this summary, load the desired
records into the grid (see Launching the Grids), then click Tools > Summary from the standalone grid.
162
Searching
Searching
Grouping
The grouping feature allows users to organize records based on field values. This feature is useful when users wish
to locate specific values in a field and review those records.
To group records, launch one of the grid views (standalone or embedded) and determine the field to be grouped
(e.g., DocExt). Click and hold the column header for the chosen field, drag it into the grouping area located just above
the column headers ("Drag a column header here to group by that column" area), and release the mouse button.
Documents will then be grouped by each unique value found in that field.
The number of records that contain a particular value is listed beside the value for each group. To expand an
individual group, click the plus sign (+). To collapse an individual group, click the minus sign (-). To expand or
collapse all groups at once, right-click on any of the groups and choose either Expand All Groups or Collapse All
Groups.
To add a second level of grouping, simply choose another field and click and drag the field into the grouping area.
When a top-level group is expanded, a second grouping will appear below it. Up to four levels of grouping may be
applied at one time.
Removing Groups
To clear a grouping, click and drag the column header from the grouping area to the area containing the column
headers. If multiple groups are applied, and a user wishes to remove all groups at once, simply right-click on any
grouping in the grid and choose Clear All Groups.
163
Filtering
Documents may be filtered in the grids based on values present in the index fields. This feature allows users to
choose any field value in the current case and quickly locate any records with that same value, removing the records
without that value from the grid. Filtering can be performed on the entire database or on search results.
Filtering Records
To filter a record, first launch the desired grid display. Choose a field to be used when filtering such as DocExt and
ensure it is displayed (View > Field List). To view the filtering options, right-click on any cell in the field column.
Choosing Filter by Selection will only return the records containing the selected value to the grid.
164
Searching
Choosing Filter Excluding Selection will only return the records that do NOT contain the selected value to the grid.
Users may continue performing filters on the filtered sets as needed.
Note: To process the filtered documents, simply launch the Batch Process or Export Utility from the grid; only the
current record set will be selected for processing.
Removing Filters
LAW allows users to easily remove the filter and return the original set of records when needed. To remove a
filter, right-click on any record in the filtered grid. The filtering options will appear.
165
Choosing Remove Filter will return the original record set that was loaded prior to the first filter performed in the grid.
166
Searching
Query Builder
It is common for clients to request that documents are produced based on certain criteria. LAW’s searching tools
allow users to perform advanced database and full text searches to locate the necessary documents and utilize a
field or fields to flag those records. The flagged records may be easily returned using the filtering methods discussed
in the Filtering section or by using the tool discussed in this topic.
Benefits of the Query Builder tool include the ability to build advanced searches by adding multiple conditions, using
clauses within searches, saving common queries to re-execute as needed, and searching any fields in a case.
To launch the Query Builder, select Tools > Search Records from the main menu or click the binoculars ( ) icon
on the main toolbar. The Database Query Builder dialog will appear.
167
Specifying Search Criteria

To add search criteria, users must select a field name, an operator, and a value (for most operators). Once this is
done, click the Add Condition button to add the search criteria to the current list. Once the first condition has been
added, select either "AND" or "OR" from the Join drop-down to specify another condition, depending on the desired
result of the search.
Field Name
The Field Name drop-down lists all of the index fields in the current case. Select the field to be searched from this list.
Operator
The Operator determines what type of search to apply for the specified value. Available operators are:
Equals - matches specified value (NOT case sensitive)

Does Not Equal - does not equal specified value (NOT case sensitive)
Greater Than - greater than specified value
Less Than - less than specified value
Greater or Equal - greater than or equal to specified value
Lesser or Equal - less than or equal to specified value
Is Empty - field has no value
Is Not Empty - field has any value
Value
The Value field is used to enter the string or value to search for in the specified field. Wildcard characters ("*" for any
string of characters, and "?" for any single character) can be used with the "Equals" and "Does Not Equal" operators.
The "Is Empty" and "Is Not Empty" operators do not require a value. The Value field will be removed if either of these
operators is selected.
Removing Conditions
To remove an existing condition, select it from the list of current conditions and click the Remove button. To clear all
items from the current list, click the Remove All button.
Note: If there are no items in the list of current conditions and the user clicks the Accept button, the query will return
all records in the current case.
Returning Additional Records

Return all Page ID's with query results - Select this option to return a page-level query for the returned documents.
The grid view will display a record for every page of each document. Additional page-level fields also become
available after selecting this option.
Return parent/attachment groups - This setting will display documents matching the specified search 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.
Note: Due to the nature of this query, setting this option may take significantly longer to return results than without it
on larger cases.
168
Searching
NOLOCK Setting
The setting, "Use NOLOCK setting to improve performance (SQL only/read-only)", is available for SQL cases to
improve query performance. When SQL Server executes a query that returns a large number of records, it will often
escalate to a table lock to improve performance. When a table lock is active, updates cannot be performed in LAW.
This can block batch processing, exports, and any other process that updates the database.
With smaller cases, table lock is generally not an issue since the lock is for a very short period. As cases scale to
several million records, a query that returns all or an excessive number of records could potentially lock the database
for several minutes. Using this setting instructs SQL Server to not lock records while the query is being executed. The
performance of the query is slightly improved. More importantly, it does not block database updates by other users.
However, because locking is not used, the result set is read-only and updates will not be available in the grid. The
NOLOCK setting should only be used in cases where updates in the grid are not necessary, for example, when
executing a query that will be used to run a batch process or export.
Saving Queries
Once a particular query is identified, it can be saved by selecting File > Save from the Database Query Builder
dialog. The Save As dialog will appear.
Three storage levels are available when saving queries:

Shared - Available to any user in the LAW case in which the query was saved.
Global - Available to any user in any LAW case.
Enter a name for the query (must be a valid filename) and a description (optional). Click Accept. The query will now
be available in the Saved Filters tab each time the Database Query Builder is accessed in the current case or all
cases, depending on the selected storage level.
The user and shared queries are stored in the case folder structure ($UserData), while global queries are stored in
<application path>\Shared. The default storage location for global queries and profiles can be changed via the
Preferences tab in Tools > Options.
169
Executing a Saved Query

Select a saved query by selecting Tools > Search Records from the main menu or by clicking on binoculars ( )
icon on the main toolbar. Next, click the Saved Filters tab from the Database Query Builder dialog.
170
Searching
Choose from User, Shared, Global, or All Available Views in the Storage Level/Scope drop-down. This value will
determine which queries will be displayed in the form. Click on a query's Title to view a Description and Preview of
the selected filter. Double-click on the Title (or right-click > Open) to apply the query to the Advanced tab. On the
Advanced tab, click Execute. The query results will be returned in one of the grid displays.
Search History
The Search History tab will save the last 50 filters that were executed from the Query Builder for each user. Users will
only see their own history in this tab.
171
The queries in the search history may be re-executed by simply double-clicking the desired query in the Request
column. It will be loaded into the Advanced tab. Click Execute.
Once the desired records have been returned in the grid, the records may be flagged (see the Tagging Documents
topic) and sent for further processing. When the Batch Process or Export Utility is executed while a set of records is
displayed in the grid, only that record set will be selected for processing. If needed, the documents to be processed
may be changed using the folder selection options within each of these utilities.
Note: For information on executing full text searches, please see the Full Text Searching topic.
172
Searching
Full Text Searching

The full text search option is used most often when using LAW as a "mud room" to identify relevant documents based
on key word searches. In order to perform full text searches, the LAW case database must be SQL or SQL Express.
The records in LAW must also be indexed prior to searching; please see the Full Text Indexing section for more
information.
Full Text Search Options

The full text search engine in LAW contains several options to help customize searches. These options may be
accessed by clicking the Options button within the Database Query Builder dialog or within the Fulltext
Dictionary dialog.
Using the Full Text Search Options dialog, the special directives listed below can be used.
Character Meaning
? matches any character
* matches any number of characters
% fuzzy search
~ stemming
173
& synonym search
~~ numeric range
: variable term weighting
## regular expression searching
Wildcards (* and ?): Wildcard characters can be used to represent any number of characters (*) or any one
character (?) in a word. Wildcard searching is particularly useful when wishing to return all variables of a particular
word or a combination of a portion of a word. Examples: appl* matches apple, application, etc; *cipl* matches
principle, participle, etc; ap*ed matches applied, approved, etc; appl? matches only apple.
Synonym Searching: Finds synonyms of a word in a search request. The word "fast" would also return "quick." If
using the Full text search options dialog, synonym searching will be performed on all words within the query. Users
can utilize synonym searching selectively by adding the "&" character after a certain word in the request.
Fuzzy Searching: Finds words, even if misspelled. The slider on the Options dialog dictates the amount of fuzziness
to apply to a search. Fuzziness can also be performed selectively by using the "%" character. The position of the %
character determines how many letters at the beginning must match exactly.
Examples:
ba%nana: words must begin with "ba" and have only one difference between it and banana
b%%anana: words must begin with a "b" and have only two differences between it and banana
Phonic Searching: Finds words that sound like the word being searched. If using the Full text search options dialog,
phonic searching will be performed on all words within the query. Phonic searches can be performed selectively by
putting a "#" in front of the word being searched.
Example: #Smith returns smith, smythe, and smithe
Stemming: Finds words that cover grammatical variants of a word.
Example: fish would also find fished and fishing
If using the Full text search options dialog, stemming will be performed on all words in the search criteria. Selective
stemming may also be performed by using "~" at the end of the word to be stemmed (i.e. fish~).
Retrieval Thresholds
Max files to retrieve - Limits the number of full text results returned by the search. Files are returned by the highest
score or number of hits. The default returns 500 hits. Setting this value to 0 will return an unlimited number of hits.
Note: Limiting this number improves full text performance.
Abort Search After - Rather than returning the documents with the highest scoring, this setting returns the results
found up to the point when the threshold is equaled.
Search Syntax
Boolean - Supports standard AND/OR connectors between search terms.
All Words/Any Words - Alternative to using Boolean that implies all AND’s and OR’s respectively between words.
Results Options
Include hits by word in search results - When enabled, LAW will include a temporary ft_HitsByWord field in the
search results in the standalone grid. For each document, this field will display the search words that For each
174
Searching
document, this field will display the search words that yielded the document, paired with the frequency of those
words. Search words and their frequency are comma-separated and multiple search words are separated by a
carriage return. See the "Persist Text Hits" section below for information on storing the actual hits returned by full text
searches in a user-defined memo field.
Performing Full Text Searches

In LAW, full text searches are performed using the Query Builder tool (Tools > Search Records or click the
binoculars icon). To invoke the full text section of the Query Builder, select the "Full text search" check box.
Note: If this option is grayed out, consider three possible causes. One cause may be that the case is not a SQL or
SQL Express case. Another possible reason is that the "Send results to grid on main form" option is enabled in the
Query Builder. Full text search results cannot be returned to the embedded (main form) grid. A third possible cause
is that none of the documents have been indexed (see Full Text Indexing).
Enter the desired search terms into the text box provided. If needed, use the AND/OR connectors to join search
phrases. An alternative to typing the search terms would be to launch the Fulltext Dictionary dialog by clicking the
Dictionary button.
In this dialog, users can begin typing letters into the "Lookup" field to locate words. Once located, click the Add
button to add the word to the Query Builder. The AND/OR connectors are available in this dialog as well for joining
search terms. Click Done to exit the dictionary. Any full text search terms and connectors will be displayed in the text
box as shown.
Full text search terms can also be loaded through the Query Builder. Click the Load Terms button and browse to a
TXT file containing the list of terms. Once the TXT file has been selected, LAW will prompt the user to choose a
175
connector which will be inserted between each term found in the list. A "NONE" option is also available when the
AND/OR connectors are not needed.
Click the Execute button from the Database Query Builder dialog to perform the search. Full text search results will
only be returned to the standalone grid. Full text searches can also be executed and records with hits can be tagged
instead of returned to the grid. See the "Full Text Reports" section below for more information.
When returning full text search results, the standalone grid will have an additional text pane to display the text for the
document and highlighted hits. The location of this pane may be changed by clicking View > Text Pane in the grid
and choosing one of the following options: Left, Bottom, Right, or Off.
The hits within a document can be navigated using the directional buttons located below the text in the text pane. The
buttons with a line to the left or right of the arrow will navigate to the first hit or last hit in the document, respectively.
The single arrow buttons will navigate from hit to hit. When the final hit for a document is reached, the right arrow will
navigate to the next document, unless the last document in the result set is currently selected. Hits can also be
navigated by entering a number within the text box in between the navigational buttons and then pressing the Enter
key.
Two fields will be added to the grid when displaying full text search results: Fulltext Hitcount and Fulltext Score. The
Fulltext Hitcount indicates the number of hits within the record.
Tagging Text Hits

The Tag Text Hits feature can be used to flag a user-defined index field for all records that contain text matching the
specified search terms. This feature can be used in place of executing a search, waiting for the search results to
return to the grid display, and tagging documents from that interface (if needed). This is a much faster way to flag
results when dealing with large amounts of data. The flagged field can later be queried to pull results or used in
conjunction with other queries.
To use this feature, first create a document-level tag (Boolean) or numeric index field (Index > Modify Fields, see
the Creating Index Fields and/or Creating Tag Fields topics). If a tag field is used, LAW will simply tag the field as
"Yes" for records with text hits. If a numeric field is used, LAW will populate the field with the number of text hits found
for the record.
Once the field has been created, launch the Query Builder (Tools > Search Records), check the box beside "Full
text search", and then enter the desired search term(s). Next, click the Tag Text Hits button. The Select Target Field
dialog will appear.
176
Searching
All user-defined tag and numeric fields will appear in the list. Choose the field to be used as the target field and then
click the OK button. LAW will perform the text search and change the field value to "Yes" (if a tag field was selected)
or populate the field with the number of hits found per document (if a numeric field was selected). When this
operation has been completed, LAW will return a message box containing the total number of affected documents,
the total number of hits, and the elapsed time.
Note: This feature does not incorporate any database conditions that may be selected when performing the text
search. Only full text searching is supported.
Term Searching
Searching for multiple words that occur in a specified sequence is done by simply entering the sequence of words to
be searched into the full text search request input. If the search syntax is set to Any Words or All Words, then the
sequence of words must be wrapped in quotes to prevent the search from inserting AND's or OR's between the
words in the sequence.
Example:
Request: Security Code (If using Any Words/All Words syntax, then use: "Security Code".)
Matches: "I entered the security code". (Words occur in sequence.)
Does Not Match: "To disable security enter the code". (Words occur, but not in sequence.)
Wildcards can be incorporated into term searches to match all or part of the words in the sequence similar to a single
term search with the added restriction that the wildcard occur in sequence.
Example:
Request: Enter * Code (If using Any Words/All Words syntax then use: "Enter * Code".)
Matches: "enter unique code" , "enter key code"
Does Not Match: "Enter Code"
Note: Each word in the term is always counted as a hit in the ft_HitCount column and highlighting view. The search
request "Security Code" will return a minimum of two hits (one for each of the two words that comprise the term).
Full Text reports count the occurrence of the entire term as one hit, as do counts in the ft_HitsByWord column
which is controlled by the "Include hits by word in search results" Full Text Search Option.
Noise Words
Noise words are words that are ignored by the indexer because they occur so commonly that they are of little use in
searching content. LAW manages noise words at the application level in a file named noise.dat. This file is located in
the \dtconfig folder which can be found in the LAW installation path. The noise.dat file may be edited to remove noise
words from the list, causing the removed words to be included in the index. Any change to the file requires that the
index be completely rebuilt for changes to take effect (Tools > Full Text Index > Re-Index All Documents).
The effect of noise words in a search request typically manifests itself when searching for terms or word sequences.
The search engine effectively treats a noise word in a search request as a word level wildcard, matching any word
that occurs at that position.
Example 1 (Noise Word: "The"):
Request: The Car (If using Any Words/All Words syntax then use: "The Car")
Matches: "Red Car","Blue Car","Fast Car"
Example 2 (Noise Word: "The"):
Request: Harold The Cat (If using Any Words/All Words syntax then use: "Harold The Cat")
177
Matches: "Harold my cat"
Does Not Match: "Harold My Friend" (Term search, only matches one of the required words in the sequence).
Note: Effectively, a noise word is processed as an "any word" wildcard (*), so in the above example the search
request is processed as: Harold * Cat.
Note: Removing noise words should be done with care as these words occur so commonly that indexing and
search performance can be drastically degraded by the inclusion of some words.
A single word search request for a noise word will return no records. For example, a search request for the term
"because" would yield no results.
Combining Database and Full Text Searches

LAW enables users to combine database and full text conditions into one query. Within the Query Builder, select the
Field, Operator, and Value for the database search. Click Add Condition to add to the list of conditions.
Next, enable full text searching by checking the box beside this option. Select a Boolean connector (AND/OR) to
connect the database query to the full text query. Enter the desired full text search terms.
Click Execute. The search results will be returned to the standalone grid view.
Full Text Reports

The Full Text Reports feature can be used to create reports based on a single search or multiple search requests and
to run multiple text search requests at once to obtain document and hit counts without returning records to the grid.
To access this feature, click Tools > Search Records, check the box beside Full text search, then click the Full
Text Reports button. The Full Text Search Reports dialog will appear.
178
Searching
Start by submitting search requests. The requests can be added to the queue by importing a list (Import Searches) or
by entering them manually (Add New). Once added, the searches can be executed (Run Searches) and the results
added to a report (Save Report) or flagged using a tag field (Tag Text Hits). This feature is for text searches only and
will always search across the entire LAW case and not subsets of records. Below is a list of the functions included in
this dialog and a description of how each can be used.
1. Search Options - This function launches the Full Text Search Options dialog, also accessible from the
Advanced tab in the Query Builder by clicking the Options button. See the "Full Text Search Options"
section in this topic for more information regarding these options.
2. Import Searches - This function is used to import search terms from a text file into the queue. After clicking
this button, browse to the text file containing the requests (input file should contain one request per line) and
then click Open. One request will be added per row in the Search Results queue. If requests in the input text
file match any requests that are already in the queue, the duplicate items will be ignored. To edit an existing
entry, double-click in the Search Results cell or press the F2 key. Press the Esc key to cancel edit mode.
Note: Imported text files may contain Unicode terms. Unicode text files must be in UTF-8 or UCS-2
format.
3. Add New - This function is used to add search requests to the queue manually. Click the button to add a
row to the queue. Type the search request into the Search Requests column and then click away from the
row or press the Enter key to complete the addition of the term(s). Click the Add New button as needed to
add more rows to the queue for additional search requests. Each row is executed as a separate search
request and not combined with the terms in other rows within the queue. Duplicate search requests cannot
be entered. To edit an existing entry, double-click in the Search Results cell or press the F2 key. Press the
Esc key to cancel edit mode.
179
4. Export Searches - This button will become available after one or more search requests have been added to
the queue. This feature will export the search requests in the queue to a text file, one request per line. After
clicking the button, browse to the desired output location, specify a file name for the text file, and then click
Save.
Note: If any of the specified terms contain Unicode, the output file will be formatted as UTF-8; otherwise,
ANSI will be used.
5. Clear All - This function will clear all search requests from the queue. Click Yes on the prompt message to
proceed with the deletion(s) or click No to cancel.
6. Delete - This function will delete the selected search request from the queue. Select a row by clicking on
any cell within the row, or select multiple, adjacent rows by clicking a row, holding down the Shift key, and
selecting the last row in the range to be deleted.
7. Run Searches - This function will execute all search requests listed in the queue. Each row is treated as an
individual search; they are not combined or joined in any way. LAW will calculate the number of documents
affected by the search and place it in the Docs column. The total number of hits found across all documents
will be placed in the Hits column. Unlike the full text search in the Query Builder, this feature does not return
records to the grid. The state of the check boxes shown at the beginning of each row will determine which
searches are executed when the Run Searches button is clicked. If the box is not checked for a particular
row, that row will not be included in the search process. Once the searches have completed, a report may
be generated or the affected documents can be flagged using the Tag Text Hits feature.
Note: When new documents are added to a case, re-running a set of searches will not search the entire
case again. It will only search documents added since the successful completion of previous searches.
Attempting to run the same search again if no new documents have been added since a previous run will
have no effect unless the search has been modified, or had its search status reset by clicking the Reset
Counts button.
The screen below shows a populated Search Requests queue. Only the selected searches were executed
after clicking the Run Searches button.
180
Searching
8. Save Reports - This function can be used only after the Run Searches feature has been executed to return
document and hit counts for the search requests in the queue. The state of the check boxes shown at the
beginning of each row will determine which search requests are included in the report. Click the Save
Reports button, browse to the desired location, enter a file name for the HTML report, and then click Save.
The report will open automatically once it has been generated. The report has two sections:
a. Custodian Summary - This summary shows document and hit counts for each custodian in the case. For
each custodian, the Total Docs column shows the number of documents returned by the search request(s)
(documents are counted only once, even if they hit across multiple searches). The Hits column indicates the number
of the text hits found in the documents based on the search requests in the queue. The Total Size column contains
the total file size in megabytes of the native files (in LAW) associated with the documents returned in the search(es).
b. Search Summary - This summary contains a list of every search request and shows the total document and
hit counts for each. The ID column contains a unique value assigned to records by the search engine for internal use
and does not match any field within LAW. The Total Size column contains the total file size in megabytes of the native
files (in LAW) associated with the documents returned in the search(es).
9. Tag Text Hits - This feature can be used to "flag" a tag (Boolean) type index field for all records that contain
text matching the specified search terms. To use this feature, start by creating one or more tag fields (Index
> Modify Fields or see the Creating Index Fields topic). Next, open the Query Builder and add one or more
search requests to the queue, and then click the Run Searches button. When the searching has been
completed, click the Tag Text Hits button. The Select Target Field dialog will appear containing a list of all
tag fields that exist in the current case. Choose the desired tag field, check the box to tag parent/attachment
families if needed, and then click OK. When using the Tag parent/attachment families feature, the document
containing the hit will be tagged as well as the entire family if the document is a parent or attachment record.
See the "Tag Text Hits" section in this topic for more information related to the Tag Text Hits feature.
181
Note: The Tag Text Hits feature in the Full Text Search Reports dialog does not have the ability to populate
a numeric field with a hit count, as opposed to the Tag Text Hits feature in the Query Builder. Unlike the
Query Builder itself, the Full Text Search Reports feature can run multiple search requests at once;
therefore, the hit count would be different for each request versus the single hit count returned by the Query
Builder.
10. Check All - This function will select the check boxes for all search requests currently listed in the queue.
11. Uncheck All - This function will de-select the check boxes for all search requests currently listed in the
queue.
12. Reset Counts - This function will clear the values in the Docs and Hits columns allowing the search
requests to be re-executed.
13. Accept - The Accept button will save all information currently shown in the Search Requests queue and
close the dialog. When the Full Text Search Reports dialog is re-launched, the contents of the queue will be
restored from the previous session. This data is stored in an Access database in <case
root>\$UserData\TextReports\Searches.mdb.
Note: Clicking the Run Searches or the Save Reports button will automatically save all changes from the
current session to the search reports database.
10. Cancel - If any changes have been made to the queue in the current session, clicking the Cancel button will
result in a warning prompt that all changes will be discarded. Click Yes to confirm or No to return to the Full
Text Search Reports dialog.
Persist Text Hits

After a full text search is executed, the search hits can be placed in a user-defined memo field for later usage. LAW
will populate the field with unique hits only and separate them by semi-colons. This feature exists in the standalone
grid only, as full text search results cannot be returned to the embedded grid display.
To utilize this feature, first perform a full text. Once the standalone grid has appeared containing the results of the
search, click Tools > Persist Text Hits from within the grid. The Persist Text Hits dialog will appear.
The "Target field for preserving text hits" drop-down will contain all user-defined, unlocked memo fields that exist in
the current case. To use an existing field, select it from the list. To create a new memo field instead, select <Create
New Field...> from the list. The Add Field dialog will appear.
182
Searching
Since only document-level memo fields may be used for this feature, these options are pre-selected and the Table
and Type fields are disabled. The "Insert at top of list" setting also does not apply at this time and is disabled. Enter a
new field name, choose the desired "Rows Spanned" value, and then click OK.
Once the field has been selected, click Accept to execute the Persist Text Hits feature. If hits already existed in the
field, the new, unique values will be appended, with each hit separated by a semi-colon as previously mentioned.
Note: If a term, or multi-word, search is executed, each word of that term is treated as a separate hit. For example,
if the term search request is "good software", then the Persist Text Hits target field will contain: good; software
183
Document-Level Coding
Document-Level Coding
LAW allows users to track information about records to aid in retrieval. This data is stored in the index fields which
are typically created when setting up the case. Information that applies to the entire document is considered
document-level and can be displayed on the Index display on the main form (see below). User defined page-level
fields can also be displayed in the Index display, but are not editable. Page-level fields created by users can only be
edited using the Import Tag List and Auto-Numbering features.
Updating Documents
Single Document
To update an index field for a single document, select the document in the document list, enter the desired values
into the field or fields on the Index display, and click the Update button (or ALT+U). The values will then be validated
based on the field types (date, text, etc.) and saved if accepted. If any of the values are not accepted (e.g., invalid
date values for date fields or duplicate values for a unique field), the user will receive an error message and the
update will be cancelled.
When documents are being scanned, any values in the index fields at the start of the scan are stored for every
document in that batch (except for fields defined as "Auto-Increment", which will increment from document to
document). This allows users to code common fields (e.g., box- or folder-level information) at scan time without
having to re-enter the same values for multiple documents.
Multiple Documents
LAW can update multiple documents with the same values. To update fields for multiple documents, select all
documents to be updated in the document list (using Ctrl, Shift, Ctrl+A), enter the common values in the desired field,
and click the Update button. If the <Update> button is clicked while multiple documents are selected, the Batch
Update dialog will appear allowing the user to select only those fields to be updated. See Batch Updating for
additional information.
Coding Options
LAW provides the following two features to save time for users who are coding large batches of documents.
185
Auto-Advance
LAW can auto-advance after updating a document. This feature causes the next document to be loaded as soon as
the current document has been updated, thereby eliminating the need to switch to the mouse and select the next
document, or tab and down arrow to the next document. To activate this feature, check the 'Auto-advance after
updating a document' setting on the Preferences tab of the Options form (Tools > Options).
Default Field
The default field is useful when coding large batches of documents by allowing users to specify the field that receives
the focus whenever a document is selected. This eliminates the need to tab around or use the mouse to set the focus
back to the index fields. With a combination of the auto-advance feature and a default field, users can practically
eliminate the need for the mouse when coding documents. To set a field as the default, select the desired field name
from the Index > Default Field menu. The default field is denoted by a check mark. To disable the default field
setting, simply select the same field again.
List Field Options

List items may also be added automatically when coding documents from the main form. To enable this feature,
check the 'Add all new list field values to list on update' option on the Preferences tab of the Tools > Options form. If
this option is enabled, and a value is typed directly into a list field and the document is updated, the value will be
added to the list (if not already present in the list).
To select multiple list items when updating a single document, select the 'Allow selection of multiple list items' setting
on the Preferences tab of the Tools > Options form. With this option selected, the user must also select a separator
character to separate each selected list item in the field.
186
Coding
Importing Data
LAW can import delimited text files to link records in LAW with existing index information stored in delimited text
format. This feature is useful when coding was performed in another application, for example. To use this feature,
select File > Import > Delimited Text from the main form.
When the Import Delimited Text dialog appears, select a delimited text file (*.csv , *.txt) to import. A sample of the
data contained in the file will be displayed. This preview can be used to double-check the order of the fields being
imported and whether or not the first record contains the field names. The Character Encoding value can be
adjusted if needed to ensure the file is parsed correctly. If the first record does contain field names, check the First
row contains field names option to ignore the first row. The records must either be already numbered (i.e., PageID
for image records) or have at least one coded field to act as the image tag. Otherwise, the coded data cannot be
linked to the images.
Next, select the fields being imported from the list of Available Fields in the same order as they appear in the text file.
If there are any fields not to be imported, select the <!-SKIP FIELD-> field to ignore values appearing in that column.
The Data Delimiters may be used to allow other types of delimited files to be imported as well. Click the Restore
Defaults button to reset the delimiters back to the default comma/quote delimiters.
Note: The Image Tag field must be one of the fields selected for import.
187
The Image Tag field is used to match the imported data with existing records. It acts as a "link" between the records
in the imported field information and the existing records in the LAW case. If no match is found for the incoming
record, it will be ignored. If a duplicate match is found, both records matching the Image Tag value found in the LAW
case will be updated with the same information. When ready to import, click Begin and LAW will import the coded
data, displaying the number of successfully imported records. LAW will also log any errors that may occur during this
process.
188
Coding
Batch Updating
LAW allows users to track information about records to aid in retrieval. This information is stored in the index fields
created when setting up the case. LAW allows multiple documents to be updated with the same values at one time.
To learn about updating documents individually, see the Document-Level Coding section.
Batch Updating in the Grid Displays

To update fields for multiple documents from within a grid display, launch the desired grid using one of the methods
discussed in the Launching the Grids section. Return only records that are to be updated using the Batch Update
feature.
To update fields for multiple documents, click Edit > Batch Update in the standalone grid or click the button in
the standalone or embedded grid toolbar. The Batch Update dialog will appear. Click within the cell in the Field
column to force the arrow to appear which allows the selection of a field that can be edited from the drop-down list.
Choose a field and then enter the desired Value in the cell beside it (Value column).
To update multiple fields at once, click the Add Field button, choose an additional field from the new cell that appears
in the Field column, and enter a value. The Remove Field button will allow the removal of an update entry from the
dialog.
The Auto-increment selected text/memo fields will cause any values entered for text or memo type fields to
increment by one for each updated record. This feature could be used to assign a new, unique identifier to all or a
subset of documents in a case.
After entering all desired information for the current set of records, click OK. LAW will report the number of records
updated.
189
Batch Updating in the Index Display

Batch updating may also be performed on the main interface using the fields visible in the Index tab. To batch
update, first select all documents to be updated in the current folder. The <Ctrl>, <Shift>, and Ctrl+A keys may be
used to select multiple documents. Enter the common values in the desired fields and click the Update button. When
the <Update> button is clicked with multiple documents selected, the Batch Update dialog will appear, allowing users
to select only those fields to be updated.
190
Coding
Numbering Documents/Pages
LAW allows users to assign document- and/or page-level numbers to records in a case. When a user-defined
numbering scheme is assigned to a document-level index field, this is considered document-level numbering. To
number records at a page-level, users may number the PageID field or a user-defined page-level index field (records
with images only).
LAW provides a Page ID field (or Bates number) that is displayed in the document list by default. Unlike the
document-level coded fields that are the same for all pages of a document, the Page ID field can be set to a unique
value for each page of a document. This allows every page in a job to be uniquely identified. Note that the Page ID
must be unique (with the exception of blanks) for every page in an Access case. If duplicates are encountered during
any of the numbering processes, the user will either receive an error or LAW will modify the Page IDs by adding a "-
DUP1", "-DUP2", etc. to the end of them. SQL and ADS cases allow duplicate page IDs. When the Page ID field is
numbered, LAW will automatically update the BegDoc# and EndDoc# fields to match those values. Other user-
defined page-level fields may be numbered as well.
Settings related to document and page numbering can be found in Tools > Options on the Numbering tab.
Auto-Numbering
Auto-Number Function
The Auto-Number function allows users to quickly and easily number or renumber document-level or page-level
fields of the current document or all of the documents from the specified page or document to the end of the current
191
folder. To use the auto-number function, select Auto-Number from the Edit menu. The Number Document dialog will
appear.
Choose between Page Level or Document Level. The Page Level option will only apply to records with associated
images. If a user attempts to auto-number one or more documents at a page level, any records without images will be
ignored.
The Target Field drop-down will contain a list of fields that are available for numbering (i.e., user-defined fields). If
Page Level is chosen, then only page-level fields will appear in the list. If Document Level is chosen, then only
document-level fields will appear in the list.
The Starting # will default to the current value of the Target Field for the currently selected page or document. Enter
the starting number to be placed in the selected field.
For both document and page level numbering, users may also include a specific field name in the Starting # field
using the following notation: &[<field name>]. For example, &[BegDoc#] will number the selected target field with the
current BegDoc# values. Multiple fields can also be used in the Starting # field. For example, "&[Page] of &[Pages]"
(without the quotes) will result in the text "1 of 20" in the selected target field.
The following fields can be used when numbering with field codes:
&[Page] – Current page of the document.
&[Pages] – Total pages in document.
&[Page ID] – Page ID value.
&[0] - &[000000000000] (12 zeroes) – Displays an incrementing value starting at 1 and resets at the
beginning of each document. The zeroes are used to format the string with zero padding.
&[<fieldname>] – Valid for all other LAW fields.
Note: If a numbering string ends with "]" it is assumed the string ends with a field. This string will not be
automatically incremented by LAW to avoid the confusion of the extra digits in the string. For example, &[Page]_001
becomes: 1_001, 2_002, 3_003,... but 001_&[Page] becomes: 001_1, 001_2, 001_3,...
Note: The field notations explained above can also be used in the Document Numbering batch process Starting #
field.
Note: The field replacement feature is not supported if the Document Level Attachment Numbering setting is
enabled under the Tools > Options > Numbering tab.
If the currently selected record has an associated image, the Pages boxes will be populated with the currently
selected page and the ending page. If numbering image records, set the starting and ending pages. If the ending
page exceeds the page count of the current image, LAW will only number to the end of the current document.
If the "Auto-number to end of folder" option is selected and the user plans to number a page-level field, the ending
page is disabled and LAW will number all the way to the end of the current folder. This feature makes it very easy to
192
Coding
fix numbering mistakes in a single document that caused all subsequent documents in the folder to be incorrectly
numbered. If numbering a document-level field, LAW will automatically auto-number to the end of the folder. If
only the current document requires updating with a document-level number, simply edit the field value in the Index
display after ensuring the field is visible.
To number multiple folders or the entire case in one process, use the Document Numbering feature in the Batch
Process utility.
Numbering during the Scan Process

LAW also allows users to automatically number pages as they are scanned in order to save time and catch any gaps
in the numbering (if originals are already numbered) at scan time. To auto-number pages while scanning, set the
Increment Mode (Index > Increment Mode) to Automatic, Manual, or Manual (Auto). The "Automatic" setting will
force all pages to be numbered based on the previous document. If no previous document exists or the previous
document is not numbered, LAW will prompt for a starting number. The "Manual" setting prompts the user for the
starting number whenever a new scan is started or a break sheet is detected. This is helpful if there are frequent gaps
in the numbering, allowing the user to verify the starting page of each new batch. The default Page ID will be the next
logical Page ID (the same as would be used with automatic numbering), so if the page matches, simply click <OK> to
begin scanning. The "Manual (Auto)" setting performs the same way as the manual mode, but LAW does not prompt
to enter a starting bates number during a batch when break sheets are used. To disable the auto-numbering of
documents, set the Increment Mode to "None".
Document/Page Level Numbering

When using the auto-numbering features in LAW, pages or documents are numbered sequentially from page to page
or doc to doc. Values ending in a numeric suffix are incremented numerically (e.g., ABC001, ABC002 ... ABC027),
while pages ending in an alpha suffix will be incremented alphabetically (e.g., ABC001a, ABC001b ... ABC001z). This
is the standard method of numbering records. However, if numbering the documents using a split document/page
level scheme (e.g., ABC001-001, ABC001-002, ABC001-003, with the next document starting with ABC002-001), the
user must select the "Use document/page level separator for Page IDs" option and specify the character to use for
the breaks (underscore is default). This option is available on the Numbering tab of the Options dialog box (Tools >
Options from main form). If this option is enabled, and the break character is detected when switching between
documents, the portion of the string before the break character will be incremented by one. The portion after the
break character will be reset to one (using the same number of characters for padding as the previous document).
Alpha-Numeric Numbering
LAW allows users to create a Bates number ending in either a number or an alphabetical character. Bates numbers
created with an ending alpha character are incremented as abc001a, abc001b, abc001c, etc. This functionality
can be disabled by clearing the "Use alpha-numeric bates numbering" check box under the Numbering tab in
the Options dialog box (Tools > Options). By disabling this setting, LAW will number the same sequence as follows:
abc001a, abc002a, abc003a, etc. This is useful for Bates numbering if the Bates numbers all contain the same alpha
suffix.
Document Level Attachment Numbering

To account for a new standard in document numbering, the option "Use document level attachment numbering" can
be selected from the Tools > Options > Numbering tab and will force LAW to assign a special suffix to a user-
specified document level numbering scheme for parent and attachment records. Records that are not parents or
attachments will not receive this suffix. This feature only applies to editable document level index fields (as opposed
to page level numbering) and applies to the Document Numbering batch process and Edit > Auto Number.
When this option is enabled, and the collection to be numbered contains parent and/or attachment record types, the
value specified by the user will be appended with a suffix in the format of [<attach number>-<total # of attachments>].
The user can access this feature by first creating a document level index field to populate with the desired numbering
scheme.
193
Example
A parent document contains two attachments in LAW. A Starting # of ABC0001 is entered into the Number Document
dialog box (Edit > Auto Number) and the "Use document level attachment numbering" option in the Numbering tab
is selected. The user has created a document level text field named "ProdNo" which is selected in the Number
Document dialog box.
The selected document level field, after numbering is complete, will contain the following:
ABC000001[00-02] - parent
ABC000001[01-02] - attachment 1
ABC000001[02-02] - attachment 2
Note: If an attachment is included in a collection to be numbered without its parent, the parent will also receive a
value in the selected field, since the attachment's value relies on the parent's value. Any other attachments of the
same record not included in the selected range will not be numbered. If the parent already contained a value, the
attachment value will be based on the parent's numbering scheme even when attempting to auto-number.
Therefore, the parent's field must be cleared or the entire family range must be selected in order to renumber with a
different scheme.
Note: If an attachment range is modified after numbering a family using this feature, the family will need to be
renumbered. This will not be done automatically.
Note: Prior to using this feature and exporting from LAW, ensure the target application supports the brackets and
dashes included in the scheme if utilizing the field containing these values as the image tag or file naming scheme.
Modifying the Default Suffix

An INI setting is available to modify the default suffix of [<attach number>-<total # of attachments>]. Place the setting
below in the Law50.ini file in the C:\<Windows> directory. If the [Preferences] section already exists, simply place
AttNumSuffix=[00-00] below it.
[Preferences]
AttNumSuffix=[00-00]
The value shown, [00-00], is the default format. This suffix is used if the INI setting does not exist or is invalid. The
value needs to contain opening and closing characters (such as brackets or parentheses - ensure the two characters
are different), a separator character (such as a hyphen), and at least one "zero" character before and after the
separator character. The minimum value is: [0-0]. The number of zeroes before or after the separator pads the value
with zeroes. For example, [000-000] displays as [002-009].
Note: This feature is not supported when auto-numbering with field codes included, such as &[Page ID].
194
Coding
Rolling Numeric Sections

The "Use rolling numeric sections" option is located under Tools > Options on the Numbering tab and may be used
to change the way LAW increments values when certain numbering schemes are utilized. The setting applies to auto-
numbering, the batch Document Numbering process, and both document-level and page-level fields. The Section
delimiter is used to specify the character used to separate sections in a numbering scheme. The default is a "."
(period). For example, the following contains four sections if the period is the chosen delimiter: ABC.0001.001.0001.
Note: Rolling will not occur in sections containing non-numeric characters.
Example:
The "Use rolling numeric sections" setting is enabled and the value ABC.0001.001.0001 used to number a document-
level index field.
ABC.0001.001.9998
ABC.0001.001.9999
ABC.0001.002.0001
ABC.0001.002.0002
If the "Use rolling numeric sections" setting is disabled, the values will be incremented as follows (using the above
example values):
ABC.0001.001.9998
ABC.0001.001.9999
ABC.0001.001.10000
ABC.0001.001.10001
Note: By default, when the numbering sequence increments high enough to roll into the next section, the section
that rolled will increment back to the value of "1" instead of "0". So 001.999 becomes 002.001 (not 002.000). An INI
setting is available to disable the auto-increment after a rollover if this is desired. To toggle the setting, place the
entry below into the LAW50.ini file in C:\<Windows>. If the [Preferences] section already exists, simply add the key,
IncrementAfterSectionRollover=1, below it.
[Preferences]
IncrementAfterSectionRollover=1
1 = enabled, 0 = disabled
The other settings on the Numbering tab can be used with the rolling numeric sections option. When the
document/page level separator is enabled, the number will first be split into prefix and suffix sections and then
incremented accordingly. If either the prefix or the suffix contains a matching rollover character, rollovers will occur at
the page and document levels.
The alpha-numeric Bates numbering setting may be used with rolling sections as well. For example,
ABC.999.999.9999 would increment to ABD.000.000.0001 with both settings enabled. If the alpha-numeric option is
disabled while rolling numeric is enabled, the value would become ABC1.000.000.0001. However, if a non-numeric
character exists in a section, that section will not rollover. For example, 001.99z would increment to 001.99aa.
If "Use document level attachment numbering" is enabled, the [00-00] suffix will be applied to the end of the user-
defined starting value. The rollover calculations occur prior to appending this suffix.
The sub-option, Allow page level numbering to span across sections, will determine whether or not pages of a
document will span across more than one document level. An example with this setting disabled is shown next:
Doc 1) ABC.001.001.001 - ABC.001.001.333

Doc 2) ABC.001.001.334 - ABC.001.001.600
Doc 3) ABC.001.001.661 - ABC.001.001.990
If the next document is larger than nine pages, it will start on the next level:
195
Doc 4) ABC.001.002.001 - ABC.001.002.234
With the setting enabled, the fourth document's pages would span across sections:
Doc 4) ABC.001.001.991 - ABC.001.002.225
Manually Numbering Pages

The auto-numbering functions work well for numbering batches of sequentially numbered pages. However, if frequent
gaps in the numbering scheme or intermittent alpha suffixes on pages exist, users may have to manually edit Page
IDs. To edit individual pages, select Index > Edit Page ID (<Ctrl+E>) or simply double-click on the Page ID display
located below the Image display. Doing so will launch the Edit Page ID dialog, which allows users to edit individual
Page IDs and provides the option to auto-number to the end of the document.
Once opened, the Edit Page ID dialog stays synchronized with the Image display and selecting one of the page
navigation buttons causes the display to update with the specified page.
Finding Specific Page IDs

To locate specific Page IDs, use the Find Page ID (<Ctrl+F>) function from the Index menu. LAW will prompt for the
desired Page ID and if found, the document will be opened to the page with the specified Page ID. To locate groups
matching a specific pattern or ranges of Page IDs, use the Query Builder.
196
Coding
Creating Tag Fields

LAW allows users to create tag fields at a document or page level. Tagging may be performed on individual records,
on all records in a case, or on filtered results. Users may also import a list of unique IDs to toggle tag values.
The tagging feature in LAW has multiple uses. Users may choose to tag documents that need to be converted to tiff,
produced to paper, responsive documents, etc. Users may even wish to tag documents that should be produced at a
larger paper size or produced in color. This feature makes it easier for any project, scanned or electronic discovery, to
be produced.
Before documents can be tagged, one or more tag type index fields will need to be created. Tag fields may be
created by first selecting Index > Modify Fields from the main menu or by clicking the "Manage Your Profiles" button
( ) button on the Index display. The Modify Fields dialog will appear.
Click Add Field to launch the Add Field dialog.
197
Enter a Name for the tag field and select the Table (document-level or page-level). Select Tag (Boolean) for the type.
Choosing "Insert at top of list" will insert the field at the top of the list in the Index display, making the field easier to
locate. Click OK to create the tag field.
The process of tagging documents is discussed in the Tagging Records topic. For more information on creating index
fields, see the Creating Index Fields topic.
198
Coding
Tagging Records
Tag field values will be reflected in one of two ways in the Index display: "Yes" or "No". In the grid displays, the "Yes"
values will appear as a green check mark and an empty field will indicate the value is "No".
Records may be tagged in the grids (using the mouse or hot keys), on the Index display, using batch update, using
batch tagging options in the grids, or by importing a tag list.
To learn how to create a tag field, see the Creating Tag Fields topic.
Tagging Individual Records

To tag an individual record, users can simply launch a grid display and check the box to apply the "Yes" value to the
document or deselect the box to apply a "No" value. The value of the tag field may also be changed for individual
records by locating the tag field in the Index display on the main form, changing the value from "No" to "Yes" or vice
versa, and clicking the Update button.
Hotkeys
Another method of tagging individual records is by assigning hotkeys to tag fields and utilizing those hotkeys in the
grids to toggle the value. Hotkey tagging will often be more efficient than using the mouse, especially when reviewing
large sets of documents for re-processing.
Assigning Hotkeys
Once tag fields have been created in a case, users can assign hotkeys to each field via the grid display (for use in the
grids only). To assign hotkeys, click the "Tagging Hotkeys" button ( ) in either the standalone or the embedded
grid display. The Tagging Hotkeys dialog will appear.
199
All existing tag fields will be listed in the Tag Field column. The Hot Key cells will contain drop-down lists of keys that
may be used for hotkey tagging. Click OK after assigning the desired hotkeys to the fields.
Review Mode
Because the tagging hotkeys may also be used as shortcut keys for other functions in LAW, users will need to enable
"Review Mode" in order to make use of the hotkey tagging feature. To enable Review Mode, click the "Review Mode"
button ( ) located on the toolbar in the standalone and embedded grid displays. After clicking this button, a
message will appear at the bottom of the standalone grid indicating that review mode is enabled:
When enabling review mode in the embedded grid, a "Review Mode Enabled" message box will appear after clicking
the review mode button. The button will appear "depressed" to indicate that review mode is enabled (in both grids).
To disable review mode in either grid, simply click the "Review Mode" button once again.
Using Hotkeys to Tag Records

With review mode enabled, use the up and down arrow keys to navigate through the records in the grid display. Once
a relevant record is found, use the assigned hotkey to edit the tag value in the tag field. The cell will display a green
check mark when a record is flagged with the "Yes" value. Press the hotkey a second time to toggle the current
value.
Tagging Multiple Records

In addition to tagging individual records, users can assign the same value to a tag field for multiple records at one
time. This method of tagging is often performed on a filtered set of records. There are generally three methods of
tagging multiple records at once: using batch tagging options in the grid, using the Batch Update feature, or using the
Import Tag List feature. The Import Tag List method is discussed in a separate topic.
200
Coding
Batch Tagging Options

The batch tagging options can be found when right-clicking a tag field in the grid display. These options provide quick
methods of tagging either all records currently displayed in the grid or only the selected (or highlighted) records. The
<Ctrl> and <Shift> keys may be used to select only certain records in the grid; the Ctrl+A combination will select all
records in the grid (standalone only).
A brief explanation of each batch tagging option is listed:
Tag Selected Rows as Yes - Assigns a "Yes" value to selected rows only.
Tag Selected Rows as No - Assigns a "No" value to selected rows only.
Toggle Tag for Selected Rows - Changes the tag value to the opposite value for selected rows only (i.e., if
record is currently "Yes", then value will be changed to "No").
Tag All Rows as Yes - Assigns a "Yes" value to all records currently in the grid.
Tag All Rows as No - Assigns a "No" value to all records currently in the grid.
Toggle Tag for All Rows - Changes the tag value to the opposite value for all records currently in the grid
(i.e., if record is currently "Yes", then value will be changed to "No").
After utilizing any of the above options, LAW will generate an "Update Complete" message box stating the number of
records updated.
Batch Updating
Batch updating is the process of applying the same value to an index field for multiple records. This feature can be
used for tagging in addition to updating any other type of user-defined or any other unlocked index field. In most
cases, the batch tagging options mentioned above will be more efficient than using this feature when working with tag
fields.
Perform a search or filter to ensure only the desired records are displayed in the grid. Then, click Edit > Batch
Update to launch the Batch Update dialog. Click within the cell in the Field column and choose a tag field from the
drop-down list. When a tag field is selected, a check box will appear in the associated Value cell as this type of field
will only accept two states. If updating the current record set to "Yes" values, check the box in the Value field.
Deselect the check box to change the records to "No" values. To edit additional tag fields (or any other type of field)
at the same time, click the Add Field button. Click OK to update all records currently displayed in the grid.
201
See the Importing Tag Lists topic for information on the third method of tagging multiple documents.
202
Coding
Importing Tag Lists

The Import Tag List feature can be used to flag multiple records using a *.txt or *.csv file containing a list of document
identifiers (i.e., DocIDs). This feature is especially useful when native or imaged files have already been distributed
and further action such as tiffing or printing a production set with specific documents is required. Another use would
be if a different type of database was used to flag records and a list of documents to be produced was created. This
list may be easily imported into the existing LAW case and later queried to locate the records for further processing.
To access this feature, select File > Import > Tag List from the main menu. The Import Tag List dialog box will
appear.
Click Browse to locate the tag import file. The tag import file is typically a text file containing a list of unique identifiers
allowing LAW to locate the records in the case. A list of DocIDs or BegDoc#s are commonly used for this purpose. If
the import file's first record contains the field name, check the "First row contains field names" box. The range
delimiter is used when importing ranges of records to be updated rather than a list of individual ID numbers (i.e.
ID0001-ID0048).
The Document ID Field drop-down contains a list of fields in LAW that may be used as the linking field between
the incoming import file and the existing records. For example, if the user is provided a text file containing a list of
DocIDs that match the DocIDs in the LAW case, then the user would select DocID as the Document ID Field.
For greater performance in cases with a large number of records, it is recommended to apply an index to the selected
Document ID field. An index can be manually applied to a field using the Index->Modify Fields dialog box. However,
203
LAW will check for the existence of an index on the selected Document ID field. If the field is not indexed after
initializing the import, LAW will allow the addition of an index for the selected Document ID field at that time. When
adding an index using this method, the grid displays will need to be closed prior to adding the index. If the grid is
active, LAW will display a prompt requesting the grid be closed in order to continue.
Note: A memo field cannot be used as the Document ID field.
The Target Field is the field to be updated with the "tag" value. If a tag field is selected, the Flag Values will appear
as "True" and "False". The Action drop-down will have two options: Update (which will update the records with the
specified Flag Value) and Reverse (which ignores the Flag Value and simply toggles the current value of the tag field
for each affected document). If other field types are selected, such as a text field, the Action options will change to
Update (explained above) and Append, which allows users to append the specified Flag Value to any existing field
data. Date fields will only have an Update option.
Once the Target Field, Action, and Flag Value options have been configured, click Add to add the entry to the list of
Selected Fields. Additional target fields may then be selected as needed.
Click OK to initialize the import. Once complete, LAW will report the number of records that have been updated and
any errors that may have occurred during the import. These records may then be returned by a search using the filter
functions or query tools.
204
Batch Processing Overview
Batch Processing Overview

The Batch Processing utility allows certain processes to be performed on multiple documents. Batch processes can
be applied to all documents in the current case, selected documents, or a single document. This feature can be used
to number, perform cleanup functions, endorse, print (to tiff or paper), and OCR documents. To begin batch
processing, select Batch Process from the Tools menu on the main form or on the standalone grid form. The Batch
Process utility may also be launched by clicking the button found on the main toolbar as well as the standalone
and embedded grid toolbars.
The Batch Processing dialog is broken into three sections: Processes, Selected Documents, and Sharing.
Processes - This section lists all available processes that may be executed as a batch.
Selected Documents - This section allows the selection of documents to be processed and displays total
document and optionally page counts of the selected records. The All Documents option will result in the
entire case being included in the batch. The Selected Documents option will be selected if the Select button
is clicked and boxes are checked next to any folders or ranges of documents to be included in the batch.
The Calculate total documents option may be selected to include document counts (and possibly page
counts - see next section) in addition to the number of folders selected. Enabling this option could cause a
delay when returning to the Batch Process screen in large cases. The Current Record Set option will be
selected when launching the Batch Process utility from a grid display and will only include
documents currently loaded into the grid.
Sharing - This section is used to enable distributed batch processing, view, edit, or join batches, assign a
batch name, and edit the invitation type. See the LMC Configuration topic for more information on setting
invitations and the LAW Management Console.
Document and Page Counts

In cases with a large number of documents and/or pages, a delay may be experienced when launching the Batch
Process or Export Utility dialogs while LAW calculates the total number of pages to display. To avoid the potential
delay, the page count can be disabled by navigating to Tools > Options > Preferences tab and then deselecting the
Calculate total pages in batch/export dialogs prior to launching the Batch Processing dialog. The number of pages
will no longer appear beside the number of documents.
205
Document Numbering
Document numbering is used to assign numbering schemes at a document- and/or page-level, including the
assignment of Page IDs to uniquely identify each page of a document with an associated image. Document-level
fields may also be numbered using this process. Choose Page or Document to determine which fields will show in the
Target Field drop-down. Then, the field to be numbered is selected as the Target Field and a Starting # is entered.
The value will increment by one for each document in the batch based on the starting number.
Image Cleanup
Image Cleanup performs the specified cleanup function(s) on all included images. The deskew filter straightens
image alignment. The black-border removal filter removes black borders from images. In order for black borders to be
removed, the borders must be of uniform width (angled black edges will not be removed). The Noise Removal
(despeckle) filter attempts to remove dust or scratches on an image. These functions may be performed as each
page is scanned (see Scan Options) or all at once in a batch process.
Note: The image cleanup filters are only applied to bitonal (black & white) pages.
206
Batch Processing
Endorse
The Endorse process endorses all documents with a specified header and/or footer. To display or modify the current
header and footer settings, select Options > Header/Footer from the Batch Processing dialog. See the
Header/Footer Options for details.
Use the First Page Only feature to endorse only the first page of each document.
Warning: If the first page contains annotations, the annotations will be lost.
A watermark (overlaid image) can also be burned into the endorsed images. To do so, select the desired watermark
image from the Watermark Settings dialog (Options > Watermark) and ensure the "Apply watermark to endorse
process" option is checked. No resizing is performed on the watermark; it is simply applied at the location specified in
the Alignment option.
Warning: Endorsing with a watermark should be used with extreme caution as endorsed watermarks CANNOT be
removed. Users should either back up the entire case and images before running this process or run it on small
controlled batches that can easily be replaced.
OCR
The OCR process performs optical character recognition on all selected documents that are flagged for OCR. (See
the Flagging Documents/Pages for OCR section for details.) Only documents with pages flagged for OCR will be
processed. The OCR settings may be displayed by selecting Options > OCR Settings from the Batch Processing
dialog. These settings are also used for single-document OCR, so be sure to validate the OCR settings before
starting any OCR process. When selecting the output format, keep in mind that most third-party applications cannot
use non-text formats for search and retrieval capabilities.
Note: Documents may be skipped, even if flagged, if they already have OCR for the specified output format and the
"Overwrite Existing Files" OCR setting is not selected.
Print (Standard-Image Only)

The Print process prints the selected image records to the printer specified in Options > Print Options. If a header
or footer is specified, it can either be included on the printed images or ignored. If the images have already been
endorsed, select "No" when prompted to include the header/footer information as it is already contained on the
images. Selecting "Yes" will cause LAW to unnecessarily re-endorse the selected images. If the images have not
been endorsed, and the user does not wish to permanently alter the images, selecting "Yes" will add the current
header/footer information for the print process only.
A watermark can also be applied during batch printing. To do so, select the desired watermark image from the
Watermark Settings dialog (Options > Watermark) and ensure the "Apply watermark to print process" option is
checked. See Watermark for additional information.
Advanced batch print options can be specified from the Batch Print Options dialog, available by selecting Options >
Print Options.
E-Print (ED-Native Files)

The E-Print process prints the selected native files to the printer specified in Options > E-Print Options. The E-Print
Options dialog also contains options for various native file types such as MS Word and MS Excel. See E-
Print/Tiff Output Settings for details.
207
Scan for Suspect Footers

The Scan for Suspect Footers process scans all pages for footers appearing to be 1" or larger and will flag an index
field (of the user's choosing) with Y if any pages in a document contain suspect footers (N if not). This feature is
useful if images already containing an endorsement have been imported into a case and the documents were re-
endorsed again, creating a double endorsement. This feature will assist in finding the documents that were double
endorsed.
TIFF Conversion
This process will use the LexisNexis® Image Driver, LexisNexis® Image Driver (300 DPI), or Informatik Image Printer
to convert the selected files to TIFF images. Version 7 of the Peernet image printer is also supported for tiff
conversions, but must be purchased directly from Peernet.
The TIFF Conversion batch process may be used to convert native files to TIFF images or to reprocess files that are
already in TIFF format. The application displayed in the SourceApp field for each record will be used to convert the
native document to a TIFF image. For example, if Microsoft Word is the value in SourceApp, then Microsoft Word will
actually be used to convert the document. The selected SourceApp must be installed on the computer in order to be
used for TIFF Conversion. See the E-Print/Tiff Output Settings section for information about native application options
and TIFF printer settings. For a list of source applications and supported file types, see Supported File Types.
Update Page Data

The Update Page Data batch process can be used to populate the PageColor, PageSize, PageWidth, and
PageHeight fields for any images in the selected record set missing this information. PageSource is not affected
during this process as the source can only be captured at the time the image is acquired.
208
Batch Processing
OCR Overview
The OCR (Optical Character Recognition) process attempts to recognize text on an image and convert it to one of the
supported formats allowing the contents of an image to be searched. (See OCR Options for details.) As such, it
provides an excellent companion for manually indexing the documents. Although this process is very time-
consuming, it provides excellent search capabilities and allows users to avoid the re-typing of scanned documents.
Also, while the Electronic Discovery Loader has the ability to extract text, not all file types that are imported will have
text within them (e.g., JPG files). The OCR process is often used in this situation as well.
The processing time for OCR varies, averaging between 1 to 2 pages per second depending on the selected OCR
engine and settings. The processing time also largely depends on each PC's processor and system memory, the
amount of information on the pages, and the quality of the originals.
The Text display on LAW's main interface will indicate the presence of text for the current document, which may be
OCR text, text extracted during an ED Loader import, text imported with load file records or raw images, or text pulled
during a TIFF conversion. To choose which type of text is displayed, right-click within the Text display and click the
desired type from the context menu. When an image is selected, the Text button has a small "page" icon on it if there
is text for that image, with the actual text displayed below the button.
Note: WordPerfect and HTML formats cannot be displayed in this viewer.) The Text display is for viewing purposes
only. If a user needs to edit the OCR, simply double-click the text to launch the text in the editor registered for that
file format. If there are multiple OCR formats for the same image, users can right-click on the OCR text and
specifically select the format to open from a pop-up menu.
OCR Indicator
LAW may also display a green, yellow, or red flag (or no icon at all) when selecting a record, depending on the OCR
status for that image. LAW allows users to flag all, none, or selected pages only for the OCR process. (See the
Flagging Documents/Pages for OCR topic for more details.) The OCR indicator gives users a quick visual
representation of the OCR status for the current document. One of the following icons will be displayed on the Text
button when a document is selected:
- Page icon, the OCR has been completed for the document (or text has been extracted during an
ED Loader import)
- Green flag, the document has one or more pages flagged for OCR
- Yellow flag, OCR process was cancelled while processing a document
- Red flag, error occurred during OCR
If no icon is displayed, no pages for the current document have been flagged for OCR.
209
Flagging Documents/Pages for OCR

Low quality originals or cluttered pages (e.g., detailed graphs and charts) can lead to excessive processing time,
frequent crashes of the OCR engine, and very poor OCR results. As such, they do not provide good OCR candidates.
In order to make the OCR process as efficient as possible, LAW allows users to specify which pages of an image will
be included for OCR. All non-flagged pages are skipped during the batch OCR process.
Note: All pages will be included if using the single document OCR process regardless of the OCRFlag value.
Tracking OCR Status

OcrStatus Field
LAW maintains two fields in the database to track the status of pages with regard to OCR. The OcrStatus field is a
document-level field that indicates the OCR status of a document. Possible values for the OcrStatus field are:
Y = One or more pages are flagged for OCR
N = No pages are flagged
C = OCR is complete on the document
I = OCR was cancelled
E = Error occurred during the OCR process
P = Processing (special flag used by LAW during the OCR process)
LAW uses the processing flag (P) to mark a document in the process of being OCR'd. This allows multiple
workstations to OCR the same set of documents simultaneously without having to worry about overlapping OCR.
Using multiple stations to share the OCR process provides an extra layer of redundancy. If one machine locks up or
crashes during the OCR process, one or more other stations can continue to OCR that set of documents.
OcrFlag Field
The OcrFlag field is a page-level field that tracks the OCR status of each page of a document. Possible values for the
OcrFlag field are:
Y = Page is flagged for OCR
N = Page is not flagged (will be skipped)
C = Page is complete
E = Error occurred OCRing page
Manually Flagging Pages

LAW provides several ways to flag pages for OCR. If the user only wants to flag certain pages for OCR, they must do
so one document at a time. To accomplish this, select the image to be included in the OCR process, select the pages
to be flagged, and click Page > Flag for OCR (or right-click on thumbnails to display the pop-up Page menu).
210
Batch Processing
Resetting the OCR flags for multiple documents can be done in one of two places. If all of the documents are in one
folder, select the documents in the document list (Ctrl+A to select all or use Ctrl or Shift to select certain documents)
and select Edit > Reset OCR Flags > ON|OFF from the main form. If the documents span multiple folders and can
be logically grouped in a query, or to reset all documents in a case, utilize the grid display. From the standalone grid,
select Tools > Reset OCR Flags > ON|OFF to reset the OCR flags for all documents in the current record set.
Flagging Pages at Scan Time

Pages may be flagged for OCR at scan time. This allows users to set the OCR status of all new pages as they are
being scanned. This setting can be toggled by selecting Scan > Scan Options > OCR All New Pages. This setting is
also displayed in the status bar at the bottom of the main form for easy reference (as "OCR(Y)" or "OCR(N)") and can
quickly be toggled by double-clicking the status.
Displaying Flagged Pages

To display the pages for the current document that are flagged for OCR, select Page > Show OCR Flags. This
highlights all flagged pages in the thumbnail display. If the thumbnail display is not active when this function is
selected, it automatically becomes active so that the thumbnails are shown. This function only highlights pages that
are flagged for OCR. It will not highlight pages that have already been completed.
211
OCR Options
The OCR tab shown below will allow users to specify various OCR options, giving more control over the OCR
process. To open the Options form and modify the OCR Options, select Tools > Options from the main form and
select the OCR tab or choose Options > OCR Settings from the Batch Processing utility.
Available Options
OCR Engine
LAW PreDiscovery supports two different OCR engines: ExperVision OpenRTK and ABBYY FineReader. Older
versions of LAW also shipped with a Xerox TextBridge engine and while this engine will still work with LAW, it cannot
be supported by LexisNexis.
ExperVision is included with the LAW installer; ABBYY FineReader is a separate installer and can be obtained by
LexisNexis when purchasing the ABBYY OCR license. The main differences between the two supported engines are
speed, language support, and output formats. The ExperVision OCR engine is much faster (2-3x) than ABBYY
FineReader. ABBYY FineReader includes more language support, including CJK (Chinese, Japanese, and Korean
languages) and is able to create PDF/A files. Both engines support the creation of searchable PDF files and are able
to produce <image>.ocr files which are used in the Storm and IPRO applications for on-image hit highlighting.
212
Batch Processing
The options on this form (discussed in the remainder of this topic) will change with the selection of the OCR engine.
Page Layout
This feature can be used to improve OCR results by specifying the layout of the pages. The default value of Auto
Detect automatically determines the layout of the page. If Single Column is selected, the OCR engine presumes that
only one column of text exists on a page.
For the unsupported Xerox TextBridge engine, two special page layouts are available that can be used to OCR pages
that are broken into even quadrants: "Quadrants, left to right" and "Quadrants, top to bottom." Both settings will OCR
the page as if it were 4 separate pages condensed onto a single page. The left to right setting will OCR the 4
quadrants in the following order: upper left, lower left, upper right, lower right. The top to bottom setting will process in
the following order: upper left, upper right, lower left, lower right.
Quality
This setting can be used to specify the quality of the pages to be included in the OCR process. The default setting is
"Normal" for both OCR engines and can be changed to more closely match the types of images included in the LAW
case. For example, the ABBYY engine supports a Quality setting called MICR (Magnetic Ink Character Recognition),
which can be used to detect a specific set of numeric characters printed with special magnetic inks (often found on
personal checks and a variety of other documents).
When a setting other than Normal is selected, the engine may spend more time on the images in an attempt to gain
better results on lower-quality images or images with fonts that require a special type of detection.
The Auto Detect setting is recommended for the unsupported Xerox TextBridge engine as it accounts for varying
quality levels among originals.
Language
The Language setting is used to specify the language dictionary the engine should use during the OCR process. If
the correct language is not selected prior to the OCR process, the characters may not be recognized properly. If
ABBYY is the selected engine, English will automatically be used as a second language if a non-English language is
selected. For example, if Greek is selected and both Greek and English exist in the source image, ABBYY should be
able to detect and perform recognition for both languages. However, if a document contains Greek, and English is
selected as the language, Greek characters will not be interpreted or rendered correctly in the text. Note: This only
pertains to languages containing Unicode characters (i.e. Chinese, Japanese, Korean, Greek, Russian). Languages
that share a common alphabet (i.e. English, Spanish, French, German, Dutch, Portuguese) will be interpreted
correctly when existing in the same document if any of these languages are selected.
For the unsupported Xerox TextBridge engine, the System Default setting uses whichever language is specified by
Windows as the default.
Output Format
This feature is used to select the output format produced by the selected OCR engine. The available output formats
and licensing requirements are in the following table:
Output Format Required License(s)

Smart Text Document

-OR-
Standard Text Document
213

-OR-
HTML

-OR-
Word for Windows

Word for Windows (2007)

WordPerfect
OCR (ExperVision OpenRTK) + OCR (ExperVision PDF

add-on)
Adobe PDF (Normal) -OR-
OCR (ABBYY FineReader
OCR (ExperVision OpenRTK) + OCR (ExperVision PDF

add-on)
Adobe PDF (w/ Hidden
-OR-
Text)

Adobe PDF/A (Normal)
Adobe PDF/A (w/ Hidden OCR (ABBYY FineReader)

Text)
Warning: If planning to export the OCR results for searching functionality, using one of the text settings is
recommended as most export formats do not support non-text OCR.
The Smart Text and Standard Text are essentially the same, both producing standard ANSI text output. See Creating
Searchable PDFs for more information when using the Adobe output options to create searchable PDF files.
Page Markers
This option allows LAW to "stamp" the resulting OCR with a bates number or page value using information retrieved
directly from the LAW database. This feature is useful for providing 100% accurate bates values in the OCR text to
aid searching in certain applications.
Note: Only the text-based output formats can be modified using this feature.
Page Markers can be customized via the law50.ini file located in the <Windows> directory. By placing the
PageStampText= section under the [OCR] key, the text stamped by the Page Marker feature can be customized.
214
Batch Processing
Currently supported fields are:

&[Page] = Current page
&[Pages] = Page count
&[Page ID] = Bates number
&[BegDoc#] = Beginning document number
<CR> = Carriage return (new line)
Example: PageStampText=###&[Page]|||Page &[Page ID]^^^ results in a stamp of: ###1|||Page ABC0001^^^ and
changes for each OCR page stamped.
Auto-Rotate
This option specifies if the OCR engine should automatically rotate images for the OCR output. The three options are
"Always ON", "Always OFF", and "Binary Images Only." The Binary Images Only setting, available to the ExperVision
engine only, setting can be used to auto-rotate black & white images only, which can help prevent color/grayscale
images with little or no text from being improperly rotated.
Auto Deskew
Enable this option to force the OCR engine to deskew the image before OCRing the document. This can often lead to
more accurate OCR (depending on the type of document). However, if the document contains graphics or angled
vertical lines, the deskew feature may align to these graphics and cause unexpected results. Disabling this option will
OCR the document with its current orientation. This feature is only available if the ExperVision OCR engine is
selected.
Create PDF Thumbnails

The OCR engines automatically create thumbnails during the Searchable PDF creation process. Use this setting to
set the "visible" property of the thumbnails when opening the PDF file in Adobe Acrobat. If this setting is checked, the
thumbnails will be viewable automatically in Adobe Acrobat; otherwise, the thumbnails will be hidden under the Pages
tab in Adobe Acrobat.
Retain Page Layout

This setting determines whether the layout of the page (columns, etc.) will be preserved in the OCR results (non-text
output formats only).
Retain Pictures
This setting determines whether pictures in the original will be preserved in the OCR results. This setting does not
affect the results if the output format is set to text. (Pictures are not retained in text files.)
Overwrite Existing Files

Use this setting to prevent or allow the replacing of existing OCR text. This feature is useful if some documents
already contain usable OCR text files and the only the files that do not contain an existing text file should be included
for processing. If an existing text file is detected for the current document, the OCR engine will skip the document and
move onto the next, thus saving processing time. It may also be necessary at times to replace all existing text files;
checking this option will replace the OCR for each document.
215
Reset Text Index Status

De-selecting this option will prevent LAW from re-flagging the document for indexing after the OCR process is
performed. This means the OCR text for affected records will not be searchable in LAW. See the Full Text Indexing
topic for more information.
216
Batch Processing
OCRing Documents
The OCR process can be performed at the document level, page level, or by region. Before performing OCR on any
documents in LAW, verify that the OCR Options have been set to ensure the proper output format. For example,
if planning to export documents into a retrieval application that uses OCR text for searching, select standard or smart
text as the output format; otherwise, the OCR results will be useless and processing time wasted. OCR should be
performed once document boundaries are no longer expected to change. For any non-text format, LAW may not be
able to merge or split the OCR files if document boundaries change after the OCR has been created. If the OCR files
cannot be modified, the OCR process will need to be run again on the document(s) in the modified range.
OCRing
Single Document
To OCR a single document or pages of a single document, use the OCR functions from the main form. Open the
desired document and select Tools > OCR > Document (<Ctrl+O>) to OCR all pages of the current image. To OCR
only certain pages of a document, first select the desired pages in the thumbnails display. If pages of the document
have already been flagged for OCR, select Page > Show OCR Flags and LAW will automatically select the flagged
pages. (See Flagging Documents/Pages for OCR for more details.) Then, click Tools > OCR > Selected Pages.
Multiple Documents
To OCR multiple documents, click Tools > Batch Process and select the OCR process from the Batch Processing
utility. During batch processing, only documents and pages flagged for OCR will be included in the OCR results. See
the OCRing Documents topic for more information.
OCRing a Region
Another available option is to OCR a specified region of an image. This feature is useful for coding information
directly from a document to a field without having to retype it. To use this feature, draw a rectangle over the desired
region while holding the <Ctrl> key. A highlighted region will appear. Click Tools > OCR > Region or right-click on
the selected region to display the OCR Region menu. This function will OCR the highlighted region and display the
results in an OCR Results dialog.
Using this dialog, the results can be copied to the clipboard, sent to an existing index field in the LAW case, and
optionally parse the results into "field name/value" pairs (e.g., DocType=Fax, DocDate:12/31/2004). Multiple lines will
be parsed and field names and values can be separated with colons (:) or equal (=) signs.
217
The highlighted region can be removed by pressing the <ESC> key or moving to a new document.
218
Batch Processing
Creating Searchable PDFs

The following feature requires the OCR (ExperVision OpenRTK) +OCR (ExperVision PDF add-on) licenses -OR- the
ABBYY FineReader license for LAW.
Checking the OCR Settings

Prior to creating the searchable PDF files, check the OCR Options form and verify the required settings are selected.
From the main menu, select Tools > Options and navigate to the OCR tab. Depending on the available licenses,
the OCR Engine should be set to either ExperVision OpenRTK or ABBYY FineReader. Next, set the Output Format
to Adobe PDF (w/Hidden Text) or Adobe PDF/A (w/ Hidden Text). PDF/A is only available with the ABBYY
FineReader engine selected.
Create PDF Thumbnails

The OCR engines automatically create thumbnails during the Searchable PDF creation process. Use this setting to
set the "visible" property of the thumbnails when opening the PDF file in Adobe Acrobat. If this setting is checked, the
thumbnails will be viewable automatically in Adobe Acrobat; otherwise, the thumbnails will be hidden under the Pages
tab in Adobe Acrobat.
219
Once the options are set, the documents are ready for the OCR process. See OCRing Documents for information on
how to OCR documents in LAW.
Exporting the Searchable PDF Files

Once the searchable PDF files have been created, those records will have an associated image file, a text file
containing the OCR text of the document, an .OCR file (containing coordinates for on-image hit highlighting in Storm
and IPRO), and a PDF+ file. This PDF+ file is the searchable PDF created by the selected OCR engine. To export
the searchable PDF files from the LAW case, launch the Export Utility (Tools > Export Utility).
In the Export Utility's Formats/Documents tab, select the PDF Conversion format as Multi-Page. (If the single-page
export is chosen, the resulting single-page PDF files will not be searchable.) The "Include Full Text" option does not
need to be selected. Provided the previous instructions were followed and the Output Format on the Options tab of
the Export Utility is set to "PDF" (and not "PDF (Image Only)"), LAW will export searchable PDF files.
Set the remaining export options according to the specifications for the project. See Export Utility Overview for
additional information about the Export Utility. See the PDF Conversion topic to learn about more PDF export options.
220
Batch Processing
Header/Footer Options
A header and/or footer may be stamped on images during Batch Processing with the 'Endorse Image' process. This
same header/footer may also be applied to printed images during batch processing, although it will not be stamped
on the image unless the endorse process is selected. To specify the header/footer, select Options > Header/Footer
from the Batch Processing form. LAW allows users to specify a maximum of 8 lines per section for a header/footer.
When applying header/footers, LAW adds a border to the image to eliminate the chance of overwriting image
data. This also makes it easy to remove or replace them after an image has been stamped.
Setting Border Size

LAW allows users to control the size of the border added to the images to hold the header/footer text. The default
size of 1/2" is adequate for 2 lines of text at the default font size. If the header/footer text is too large for the specified
border size, it will be cropped. Keep this in mind before stamping a large set of documents. Users should first test the
specified header/footer on a small subset of documents to ensure it will fit within the specified border.
Note: Setting the border size has no effect on the image if no text is entered for a header or footer.
Setting Fonts
Fonts can be specified for each line of each section. To specify a font for a specific line, place the cursor anywhere
on that line before pressing the font button ( ). The "Synchronize fonts for all sections" setting allows users to
automatically use the same font for all header/footer text. If this setting is checked, setting a font for any line will
cause the fonts for all header/footer text to be updated to the selected font.
Note: If trying to position text using spaces, it is easiest to use a font like "Courier New" in which all characters are
the same width.
221
Setting Text
To set the text for any area, place the cursor on the desired area and either enter the text or press one of the buttons
to enter a pre-defined value. The pre-defined values that can be entered are:
- Inserts "&[Page]", which represents the current page number.
- Inserts "&[Pages]", which represents the page count.
- Prompts user to select an index field, of which the contents will be used (e.g., &[DocID]). This allows users to
endorse or print document level coding on the images.
- Inserts "&[Page ID]", which represents the Page ID. This will cause the Pages IDs or Bates numbers to be
endorsed and/or printed on all of the pages.
Auto-Incrementing Using Index Fields

LAW can endorse documents with sequential values based on a starting value in a specified index field. To use this
feature, add "++" to the end of the field notation in the header/footer code. For example, a footer value of
"&[DocID]++" would cause the documents to be endorsed sequentially, starting each document with the value in the
DocID field.
Removing a Header/Footer
LAW allows users to remove headers/footers, although this is not necessary if the user simply wishes to modify the
existing header/footer. Restamping with a new header/footer automatically removes any existing headers/footers and
adds the new ones. If the user does, however, need to remove a header or footer, do so in one of two ways. Either
restamp with the border size set to 'None' or clear out the header/footer information of the part to be removed and
restamp.
Caution: Use caution when working with rotated images containing an existing endorsement. If the endorsement
does not appear on the top or bottom of the image due to a manual rotation (as viewed in LAW), removing or
modifying the existing endorsement on this image will cause LAW to remove the endorsement (which LAW thinks
exists on the bottom of the image) and may remove actual document data located at the bottom of the image. The
only way to prevent this from occurring is to first re-rotate the image so the endorsement that LAW applied to the
image appears as it was applied.
222
Batch Processing
Watermark
The Watermark Settings dialog can be accessed using the Options menu under Batch Processing. This feature is
used to permanently "stamp" a group of documents with a specified watermark image selected in the Watermark
File section.
The watermark image may either be applied during the endorse or print batch processes. Use the Alignment setting
to specify the starting location of the watermark. This can be useful when applying a specially formatted endorsement
which may require graphics or special formatting not supported with the Header/Footer settings.
Warning: Endorsing with a watermark should be used with extreme caution as endorsed watermarks CANNOT be
removed. Users should either back up the entire case and images before running this process or run it on small
controlled batches that can easily be replaced.
Special Notes:
It is important to understand how this feature works to avoid accidentally ruining documents in the case. The
watermark cannot be removed once it is applied, so it is a good idea to run a few tests with a practice document to
ensure the image is being applied as desired. A few common problems can result from the situations below:
Unlike endorsements, watermarks cannot be removed once applied. If a watermark is applied during an
endorsement where text is also being applied, the watermark will be aligned to the additional header or footer
applied to the document. If the text needs to later be modified, re-applying the endorsement will cause LAW to
remove the old header/footer and re-apply the new header/footer text. Some of the watermark's image data
may exist in this region and would be lost in this situation. Avoid this situation by either creating watermarks
that contain wide margins so image data does not exist outside the header/footer regions or apply the
watermark as a final step.
Different image formats will be applied differently on the various image types. For best results, if the source
documents are TIFF images, use/create a watermark which is also a TIFF image using the same resolution as
the original document. If the watermark appears expanded or shrunk more than expected, it could be due to a
large difference in the image resolutions. Color formats should also be considered. Applying a color watermark
on a black and white document will result in a black and white watermark.
223
White is considered the transparent color in a watermark. GIF images with transparent regions are not
compatible with this feature.
If the dimensions of the watermark are greater than the size of the document, the watermark will be shrunk
and fit to page. When testing the watermark, also consider testing rotated or oversize images which may exist
in the case.
Creating a Custom Watermark

A custom watermark may be created using any type of image editing application. The following is an example of
creating a black and white semi-transparent watermark using Microsoft Paint as the image editor.
First, open MS Paint. Then, using the Text tool, type the word to include in the watermark.
Choose Image > Invert Colors.
Using the airbrush tool, airbrush the white text to the desired ’r;thickness’ and re-invert the color again.
Saving this image as a BMP and using it as a watermark will provide the effect of a transparent watermark. Different
textures in other image editors may be used. The dimensions of the image will determine the location of the image
once applied to the image. Some test runs will be required to get the desired location.
224
Batch Processing
Print Options
The Batch Print Options dialog contains advanced print options available during the batch printing process. (This
batch process if for image printing only-see E-Print/Tiff Output Settings for native file printing settings.) This dialog
can be displayed by selecting Options > Print Options from the Batch Processing form.
Auto-Rotate Pages
This setting causes pages to be rotated 90 degrees if they are landscape.
Auto-Size Paper
This option will allow images to be printed on the corresponding paper size determined by the dimensions of the
image to be printed. For example, a legal sized document may have been scanned as 8 ½" x 14" and endorsed in
LAW with a ½" footer resulting in an image size of 8 ½" x 14 ½". LAW will detect the page size and send it to the
paper size that most closely matches the original size of the image; for this example, the document would be printed
on legal sized paper. This feature will also work with documents containing mixed paper sizes.
In order for this option to work, the "Send jobs in batches of N pages" must also be enabled. If Auto-Size Paper is
selected while "Send jobs..." is not selected, a message box will appear stating the feature requires it and will enable
the option automatically. Enabling these two options also enables the printing of color separator pages.
225
Do Not Print Annotations

Use this setting to exclude non-merged annotations from printed output. If this setting is disabled, any non-merged
annotations will appear on the printed output.
Include Separator Pages

This setting causes separator pages to be included in front of each document. The Paper Source setting determines
the paper tray used for the separator pages, enabling separator pages to be pulled from an alternate tray than the
actual images. This allows the separator pages to be printed on color pages if the printer contains multiple trays. The
available trays are determined by the specified printer driver and frequently apply to a wide range of models. As such,
some trays listed may have no effect on the specific printer model used. Experiment to determine the actual trays
used before batching a large set of documents when using this feature.
Clicking the Options button will launch the Separator Page Options dialog and allow customizing of separator pages
for the print job. See the Separator Pages topic for more information on this feature.
The Print separator pages only option can be used to print only the separator pages for the selected documents.
The actual documents will not be printed. If needed, select the Options button (above) to configure the separator
pages prior to printing.
The Print folder break separator pages will instruct LAW to print a separator page each time a new folder is
encountered while printing the selected documents. Folder breaks can also be configured by clicking the above
Options button.
Limit Jobs in Print Queue

This setting causes LAW to monitor the print queue for active jobs and limit the number of jobs in the print queue to
the specified number. This can be beneficial for slower printers by minimizing the amount of information queued at
any one time. If this feature is activated, LAW will stop sending documents to the printer once the limit has been
reached and wait until the document currently being printed is complete before sending another.
Rip to PDF Before Printing

This setting causes LAW to convert images to PDF format before sending them to the printer. This feature can speed
printing if using a PostScript printer driver as PDF is very similar in format to the PostScript format, requiring less
work by the printer driver when printing.
Send Jobs in Batches

This setting allows users to control the size of jobs sent to the printer. It can significantly improve printer performance
for high-speed printers, especially when printing a large number of documents with only a few pages each. For
example, using the default spool limit of 100 to print 100 3-page documents would cause LAW to send 3 100-page
documents to the printer as opposed to 100 3-page documents. This eliminates the majority of the extra time required
by the printer for cycling down and then up again between documents.
Using this feature also corrects the problem with documents being printed out of order by various digital printers. The
spoolers used by many high-speed printers, in an attempt to reduce printing time, will actually reorder documents in
the print queue causing documents to be printed out of order even though they were sent to the printer in the original
order. Batching the documents into large print jobs prevents the print spooler from reorganizing documents in most
cases.
With this feature enabled, separator pages cannot be printed to a separate tray unless the "Auto-Size paper" is also
selected.
226
Batch Processing
Staple Documents
This setting has been added specifically for the Canon iR110 printer to staple documents during the print process in
LAW. This is the only printer supported for stapling, although other models may in fact work as well.
Tracking Print Jobs in the Spooler

Each document sent to the print spooler will be named in the following format, making QC of print jobs via the print
spooler easier to perform: LAW Batch 000000 - <Description>. The count to the left of the hyphen will increment by
one for each job. The <Description> will be replaced with the DocID, BegDoc#, or ID for documents. LAW will use
whichever item is found first in the order shown. If "Send jobs in batches of N pages" is enabled, the <Description>
portion will not be present as the job would contain multiple documents. For separator pages, the <Description> will
be followed by a hyphen and then "Break" for document separator pages or "Folder Break" for folder separator
pages.
Example (folder break):

LAW Batch 000276 - Folder Break
Example (document break):

LAW Batch 000277 - Break
Example (document):
LAW Batch 000278 - ABC00382
227
E-Print/TIFF Output Settings

The E-Print and TIFF Conversion options are essentially the same, with the exception of specific output and printer
settings, as both processes involve the printing native files in LAW. The E-Print batch process is used to print native
files in a LAW case to paper. The TIFF Conversion batch process is used to convert native files in a LAW case to
TIFF images. See Supported File Types for a list of source applications and supported file types.
The E-Print settings can be launched by clicking Options > E-Print Options in the Batch Processing dialog, while
the TIFF Conversion settings may be found under Options > TIFF Options.
E-Print Options
The "E-Print" category in the E-Print Options contains the active printer and separator page settings.
Active Printer - Indicates the printer that will be used to print the native files to paper. Click Setup to
configure any printer-specific settings, such as tray assignments.
228
Batch Processing
Print Separator Pages - When selected, this feature enables the printing of separator pages between
documents and/or folders.
Template - Contains a list of available templates for the separator pages. Select <Custom> to enable the
Options button. Clicking Options will launch the Separator Pages Options dialog and will allow customizing of
separator pages. See the Separator Pages topic for more information.
Included - Select a printer tray from the drop-down to print separator pages in front of any "included" file
types (supported for printing).
Excluded - Select a printer tray from the drop-down to print separator pages in front of any "excluded" file
types (files without a valid source application for printing).
Folders - Select a printer tray from the drop-down to print separator pages at the beginning of each new
folder when printing.
Print separator pages only - This option can be used to print only the separator pages for the selected
documents. The actual documents will not be printed. Select a predefined template from above or click the
Options button to configure custom separator pages.
Print Jobs
Each separator page or placeholder sent to the print spooler will be named in the following format, making QC of print
jobs via the print spooler easier to perform: LAW Batch 000000 - <document identifier> - <description>. The count to
the left of the hyphen will increment by one for each job. The <document identifier> will be replaced with the DocID,
BegDoc#, or ID for document separator pages and placeholders that are generated for documents that error during
TIFF conversion. LAW will use whichever item is found first in the order shown. Folder breaks will not have the
document identifier as they are not associated with a single document. The <description> will be replaced by
"Separator" for document separator pages and "Placeholder" for documents that error during TIFF Conversion. The
name of the print job for native files will display in the spooler as the filename stored in LAW, such as 01.ntv.doc.
Example (folder break - E-Print):

Example (document break - E-Print):

LAW Batch 000277 - ID000384 - Separator
Example (error placeholder - TIFF Conversion):

LAW Batch 000278 - ID000385 - Placeholder
TIFF Output Options

The "TIFF Output" category in the TIFF Options will contain options specific to the tiff image output (i.e., format and
color) and placeholders.
229
Active Driver: Stores the active tiff printer driver. LAW currently supports the Informatik Image Driver,
LexisNexis® Image Driver, and LexisNexis® Image Driver (300 DPI) (both included with LAW), and Peernet
TIFF Image Printer version 7.0 (must be purchased from Peernet). Click Setup to configure printer-specific
settings.
Note: The Informatik Image Driver is no longer included in LAW full installs for versions 5.2 and higher,
but can still be used for batch and single document TIFF Conversions. The Informatik Image Driver
version 4.0 is not officially supported on Windows Vista. Limited technical support will be provided for
this driver; the LexisNexis Image Driver is the supported printer for TIFF conversions.
Note: The LexisNexis Image Driver, based on the Zan Image Printer, is now included in LAW full installs
and can be used for batch TIFF conversion and single document TIFF conversions. Unlike other
supported drivers, the LexisNexis Image Driver supports text extraction during conversions. Also
included with the LAW full installer is the LexisNexis Image Driver (300 DPI) printer. The images created
by this printer will always be forced to 300 DPI.
Color Reduction: The 'Reduce to Optimal Palette' setting will cause the image to be saved as a color
image or a black and white image based on the image color properties. If the image contains any color, then
230
Batch Processing
the tiff image will be saved in a color tiff format; if no color is found, the image will be saved as black and white.
The 'Reduce to grayscale' setting will reduce color images to a grayscale format.
Color Compression: The Color Compression setting allows users to specify the compression type of the
produced images. The most widely supported and more commonly used format is the JPEG compression
format. This format will also produce the smallest file sizes compared to the other two formats. The Packbits,
LZW, and no compression settings may also be used, but the file sizes will be larger than the JPEG format and
may not be viewable in the destination application.
Output Format: LAW can produce output tiff images in either single-page (serialized) or multi-page format.
If the multi-page format is selected, each document will have its own tiff image associated with it containing all
the pages of the document in the single tiff file. LAW stores the output tiff images in the <case root>\$Image
Archive folder.
The Multipage unless size is over: N KB option can be used for printing large files where documents may
contain thousands of pages per document (text files for example). Use this feature to force those documents
over a certain file size to be converted serialized instead of multi-paged.
Drop blank pages: When selected, LAW will detect any blank pages created during the tiff conversion and
remove them from the output tiff image.
Overwrite Existing Files: With this option selected while tiffing, LAW will overwrite any existing images that
were created as a result of the TIFF Conversion batch process.
Print placeholders for unsupported/excluded docs: With this setting enabled, LAW will print a
placeholder image for any documents that were included for printing but did not have a source application
assigned. See "Template" below for more information.
Print placeholders for documents that error during conversion: When enabled, LAW will produce a
placeholder image for any documents that received errors and could not be converted to tiff. See "Template"
below for more information.
Template: The Template option offers a drop-down list of placeholder templates to be used in conjunction
with the "Print placeholders for unsupported/excluded docs" and "Print placeholders for documents that error
during conversion" settings. To customize these placeholder images, select <Custom> from the drop-down list
and then click the Options button. See the Separator Pages topic for information on customizing placeholders.
Save text with images (LexisNexis® Image Driver only): When enabled, the LexisNexis Image Driver will
extract text from documents during the TIFF conversion process. This text can be viewed from the main LAW
window. Select the document and then select the Text tab. Right-click the text and select Open Text (Printed).
Note: Adobe PDF files are not supported for text extraction during TIFF Conversion.
Reset text index status - De-selecting this sub-option of "Save text with images" will prevent LAW from re-
flagging the document for indexing after the TIFF conversion and printed text is created. This means the printed
text for affected records will not be searchable in LAW. See the Full Text Indexing topic for more information.
Treat native TIFF images as image for record (bypass TIFF conversion): When enabled, LAW will copy
the native TIFF image file from the $EDD\$NativeFiles folder and place it in the $Image Archive folder. This
feature saves time during TIFF conversion because it skips the printing process by making a copy of the native
TIFF image instead of creating a new image using the LexisNexis Image Driver.
By default, this feature applies to the following TIFF image file type IDs: 321, 298, and 146. These file type
ID numbers correspond to the ID numbers stored in the file type database used by the ED Loader. To view a
list of all file IDs and their associated file extensions, click File > Import > Electronic Discovery and then
click Tools > File Type Manager within the ED Loader. The File ID column contains the ID number for each
file type. To edit the default list of file types for this feature, place the following setting in the LAW50.ini file
located in the application path (i.e. C:\Program Files\Law50):
[TreatNativeAsImage]
ImageFileTypes=321;298;146
The default types are shown above, separated by semi-colons. File IDs can be removed from the list and/or
other image file IDs can be added. This feature is limited to image files that are supported by the imaging
toolkit used by LAW. An error will be logged if an image is not a supported file type.
231
Note: Use caution when adding file types to the list if planning to endorse the "native image" files. If the
image dimensions are very small, such as 2x2, the endorsement may appear quite large on the image or
be unviewable. Converting the image to a larger TIFF image (i.e. 8.5x11) instead of using the treat native
as image setting can prevent this issue.
▪ Force TIFF conversion settings on native TIFF images: When enabled, LAW will apply the
active color reduction, color compression, output format (multi-page or serialized), and drop blank pages
settings to a copy of the native image. The modified image is then saved and moved into the $Image
Archive folder. This setting is useful for matching the image format of previously printed TIFFs which
maintains the format consistency of the images throughout the case while using the treat native as image
feature.
Saving Defaults
An option to "Save settings as default" appears as a check box at the bottom of both the E-Print and TIFF Options
forms. When selected, any currently selected settings will remain as the default selections for all new cases.
Tracking Print Jobs in the Spooler

Each separator page or placeholder sent to the print spooler will be named in the following format, making QC of print
jobs via the print spooler easier to perform: LAW Batch 000000 - <document identifier> - <description>. The count to
the left of the hyphen will increment by one for each job. The <document identifier> will be replaced with the DocID,
BegDoc#, or ID for document separator pages and placeholders that are generated for documents that error during
TIFF conversion. LAW will use whichever item is found first in the order shown. Folder breaks will not have the
document identifier as they are not associated with a single document. The <description> will be replaced by
"Separator" for document separator pages and "Placeholder" for documents that error during TIFF Conversion. The
name of the print job for native files will display in the spooler as the filename stored in LAW, such as 01.ntv.doc.
Example (folder break - E-Print):

Example (document break - E-Print):

LAW Batch 000277 - ID000384 - Separator
Example (error placeholder - TIFF Conversion):

LAW Batch 000278 - ID000385 - Placeholder
232
Batch Processing
Supported File Types

LAW supports printing images and Microsoft Office documents. In addition to the default file types, you can specify
custom file types for printing, provided that they can be opened and printed by one of the supported source
applications. The source applications are the programs used to open and print documents, and MUST be installed on
the system with LAW to print documents of that type. The following table lists the supported source applications and
their common corresponding file types.
Source Applications Supported File Types
Microsoft Word *.doc, *.dot, *.htm, *.rtf, *.txt, *.wpd
Microsoft Excel *.xls, *.xlw, *.wk?
Microsoft Outlook *.pst, *.msg, *.eml, *.idx
Microsoft PowerPoint *.pps, *.ppt
Microsoft Visio *.vs*, *.v?x
Internet Explorer *.htm, *.html
Adobe Acrobat/Reader *.pdf
Lotus Notes *.nsf
WordPerfect *.wpd
VoloView Express *.dwf, *.dwg, *.dxf
Snapshot Viewer *.snp
eDrawings Viewer 2009** **(2008 *.eprt, *.easm, *.edrw, *.eprtx, *.easmx, *.edrwx (eDrawings Files);
not supported in versions 5.3.14 and *.sldprt, *.sldasm, *.slddrw (SolidWorks Files); *.dxf, *.dwg (DXF/DWG
above-2009 not supported in Files); *.3dxml (3DXML Files); *.stl (STL Files); *.prt, *.prt.*, *.xpr,
version 5.3.08 and below) *.asm, *.asm.*, *.xas (Pro/E Files); *.prtdot, *.asmdot, *.drwdot
(SolidWorks Template Files)
AutoVue Suite Supports over 450 file types. Please view the product website for a list
of supported formats: www.cimmetry.com/_products/formats.html.
Built-in Sources Supported File Types
Binary/Hex Printer *.bin, *.hex
233
Text/RTF Printer *.txt, *.rtf, *.ini, *.bat, *.vbs, *.java, *.cpp

(and various other text based types)
Note: Unicode text files are not supported with the Text/RTF
Printer. However, RTF with Unicode is supported. This is a limitation
of the underlying component. To print Unicode text files, use
Microsoft Word or the Shell Printer as the source application.
If using the Shell Printer, you must ensure that the application
registered on the system for text files supports shell prints. For
example, Notepad supports shell prints.
Image Printer *.awd, *.bmp, *.dcx, *.gif, *.jpg, *.pex, *.tif, *.xif
Shell Printer The Shell Printer source application can be used to print file types
through any application that supports command line printing. In other
words, if you can right-click on a file in Windows and select Print, to
print the file through the associated application, then the application
supports command line printing.
When the Shell Printer is set as the SourceApp for a document in

LAW, then the application associated with that file type in Windows
will be used to convert the file to TIFF or print the file to paper in LAW.
For example, a user imports a text file into LAW and sets the
SourceApp to Shell Printer. On the user’s computer, text files are
associated with Notepad. When the user converts the file to TIFF in
LAW, Notepad will be used to print the file to TIFF. The output image
will be added to the record in LAW, as it would when using any other
SourceApp.
LAW also supports printing zipped archives (*.zip) and self-extracting zip archives (*.exe). Zipped files will
automatically be included in both file and e-mail print jobs. The contents of the archive will be processed according to
the specified file types for printing. If a zip file happens to contain a zip file, Z-Print will recursively open the archives
and process the supported file types. The filename extraction format for Zip files is in the format
<Archive>^<Filename>.
Special File Type Notes

LAW does not support printing Lotus 1-2-3 documents directly. In order to print these documents, you must
have Microsoft Excel installed.
Printing WordPerfect files to MS Word may require an additional add-on found on the MS Office installation
CD. If this add-on is not installed prior to printing WordPerfect files, Word will be unable to recognize the file
format and an error will be logged.
In order to use the "Snapshot Viewer", you must install support for the Microsoft Access Snapshot Viewer. If
Microsoft Office with Access is installed, it can be added from the Office installation media. If Microsoft Access
is not installed, a free viewer can be downloaded from Microsoft.
234
Batch Processing
Both Internet Explorer and Word are capable of printing *.htm and *.html files. By default LAW prints these
two file types to Internet Explorer due to issues with Word. If you experience any problems printing certain htm
or html files using Internet Explorer then try printing the problematic files using Word as a backup print source.
Note: HTM and HTML files will always return a page count of 1 if the source application is set to Internet
Explorer. If the source application is MS Word, the page count will return 1 if the file is exactly 1 page
long, or it will return 2 pages for any document containing more than 1 page. Accurate page counts for
HTM and HTML files will be determined and logged after the file has been printed to either an image or
paper.
Printing files with VoloView Express (*.dwg) automatically centers the drawing and fills the page.
Note: VoloView Express may not work correctly for the first document printed if the 'Drawing Settings'
tab of the Page Setup is not the active tab. The last viewed tab remains the default. To ensure it works
correctly, open a document, select the Drawing Settings tab, and click OK. This tab should remain the
default tab allowing LAW to send the appropriate messages to the dialog.
In LAW versions 5.3.14 and above, 2009 is the only version of eDrawings supported as a print source
application, as opposed to 2008 which is the only version supported with previous versions of LAW. It is
recommended to uninstall version 2008 prior to installing 2009 and using it as a source application in LAW.
235
Acrobat
If experiencing problems while printing Adobe Acrobat files, try changing the PostScript Options in the Acrobat
category.
LAW will print PDF documents with a default PostScript level of 3 to prevent possible problems with certain
PostScript printers. If necessary, this setting may be modified by enabling Allow Binary Data, and choosing the
desired Print Method.
236
Batch Processing
E-Mail
The E-Mail option allows printing e-mails directly from Lotus Notes instead of using the HTM output file created during
ED Loader imports. Using this option, the output retains the original Lotus formatting, including inline images and RTF
content. The E-Mail option is selected by default for new cases.
Note: When using this option, the Lotus mail stores (*.NSF) must remain in same location from which they were
imported. The E-Mail option requires access to the source mail store during the print process. If the mail stores are
moved after the import, attempts to access the store will fail and error messages will be logged for all e-mails.
237
Excel
The many options in LAW for printing Excel documents can be found in the Excel category in the e-Print and TIFF
Options. These options will help standardize the format of the Excel files being processed. Since spreadsheets are
not limited to physical paper constraints like a Word document, page boundaries can be difficult to determine through
Excel. In some rare cases, the spreadsheets’ page boundaries may need to be adjusted manually to format the
output correctly. QC of Excel files for readability and formatting purposes after being printed to TIFF or paper is
recommended.
The Override Default Settings option will allow LAW to ignore the default settings saved in the Excel spreadsheets
and force Excel documents to print according to the print options in LAW. If this option is not checked, Excel
documents will be printed based on how the document was saved. For example, if an Excel file contains page breaks
and the user wishes to ignore the page break information and print the entire contents of the file, then the user would
check the "Override Default Settings" option. If this option is not checked, only the information contained within the
page break boundaries will be printed. This feature is helpful for guaranteeing that all Excel files are being processed
with the same settings.
Note: Excel automatically determines the printable area of a document when using this feature. An Excel file
can contain a very small amount of information (e.g., a space or formatting data) in row 10,000 column AAA, for
example. If this data exists, Excel will determine it to be important printable information, which may then result in
numerous (sometimes thousands) of blank pages being printed. LAW is currently unable to prevent this type of
situation, so it is important to QC Excel files after printing.
238
Batch Processing
Orientation
Use this option to select the orientation of the pages to be printed (portrait or landscape).
Scaling
Auto-Size Columns - Adjusts the column sizes so the information contained within the cells is not "cropped"
or hidden by an adjacent cell.
Fit to Page - Forces the entire spreadsheet to fit onto one page when printed. Caution: This option may
cause unreadable or extremely small font sizes if the sheets are very large. This feature is not
recommended if printing Excel files with unknown content or large amounts of data per sheet.
239
Print
Gridlines - Displays the gridlines or cell outlines in the spreadsheet if selected.
Footers - Prevents sheets from including footers on processed documents when disabled. This can be
helpful if a footer contains date information that the user does not want included in the output.
Headers - Prevents sheets from including headers on processed documents when disabled. This can be
helpful if a header contains date information that the user does not want included in the output.
Hidden columns/rows - Prints any columns and rows that have been hidden when selected.
Hidden sheets - Prints any hidden sheets contained in the Excel file when selected.
Print black & white - Forces Excel documents to be printed as black and white only, removing all
background colors and forcing all text to black. If this setting is enabled, all background fills and patterns are
cleared, which can prevent unnecessary parts of a worksheet from being printed.
Remove repeating columns - Prevents any columns set to repeat from repeating in the tiff output when
selected.
Remove repeating rows - Prevents any rows set to repeat from repeating in the tiff output when selected.
Row and column headings - Includes the headings in the printed spreadsheet when selected.
Comments - Comments saved in the Excel files can be printed using this option. They can be shown 'As
Displayed' (as saved in the Excel file) or at the 'End of the Sheet'.
Limit output to <N> pages: Limits the number of printed pages to the number specified in the text box. The
minimum value for this setting is 0, which will act the same as disabling the setting (does not limit pages
printed). The maximum value is 99999. When LAW limits the number of pages for a file, the following
warning will be logged to the ErrorMsg field: [tiff]: Output limited by Excel page count threshold (ErrCode=-1,
Line=3780). This warning will also be logged in the event the actual page count happens to match the limit
specified in the options - LAW cannot filter out these occurrences.
Page Order
Down, then Over - Causes the spreadsheet to be printed down the sheet, then over and back down, if
selected.
Over, then Down - Causes the spreadsheet to be printed across first, then down the columns and back
over, if selected.
Field Replacements
The following Field Replacement options allow users to specify the actions LAW should take when encountering
these types of dynamic fields in a document.
Date/Time Fields - This option allows the selection of one of five items: Do not modify (print as is), Do not
print, Replace with date created, Replace with modified date, and Show field codes.
Filename Fields - This option allows the selection of one of four items: Do not modify (print as is), Do not
print, Replace path from filename, and Show field codes.
Both of these settings are useful for preventing Excel documents from printing current date or file path information
which may only apply to the production machine and not to the project being printed.
240
Batch Processing
HTML
This category contains options for HTML documents printed to paper or tiff through LAW.
Remove indentation from presaved e-mails (HTML) when printing - Removes the indentation from e-mails
converted to HTML for printing. If enabled, all indentation will be stripped when printing to prevent e-mail threads from
being pushed so far to the right that the output ends up with very few characters per line. This setting affects only
printed output and does not directly affect the native files.
Use alternate HTML rendering engine for Internet Explorer - This HTML engine will increase print speeds
dramatically for HTML documents printed using Internet Explorer. However, it is not as mature and tested as Internet
Explorer for handling extremely complex HTML and all the possibilities of malformed HTML that may occur. Although
substantial effort has been taken to verify the output of a wide array of HTML documents printed using this engine,
there is no way to test every possibility and LexisNexis cannot absolutely guarantee the quality of any third-party
product. Before using this alternate engine for large scale productions, LexisNexis STRONGLY encourages users to
perform their own tests on some small samples and perform periodic QA on any output produced with this engine.
241
Image Printer
This category contains options for documents printed to paper or tiff via the Image Printer source application through
LAW.
Auto-Rotate Images - This feature will automatically rotate images printed through the Image Printer ONLY so each
image is oriented consistently, making the printing of such images easier to print to paper. This is useful for images
containing a mixture of landscape and portrait orientations. If printed directly to paper, some of the images would
appear correctly in portrait, and others would appear as a landscape image printed on portrait paper.
242
Batch Processing
Passwords
The Passwords category will allow users to enter any known passwords for password-protected files contained within
the collection, allowing the files to be printed or converted to tiff without error. Up to three passwords may be
specified at one time for Adobe Acrobat, while an unlimited number of passwords may be specified for Microsoft
Office applications. Click Add to enter a password.
243
PowerPoint
This category contains options for Microsoft PowerPoint documents and will be used when printing to paper or
converting to TIFF through LAW.
Do not print date/time stamps - Removes the auto-date and auto-time fields from a slide if they exist and prevents
the printing of that information.
Do not print headers/footers - Use this setting to disable the values placed in the header and footer sections of a
slide. The contents of the header and footer fields can be viewed in PowerPoint under View > Header and Footer...
These are the header and footer sections which will be disabled for each slide if either of this option is enabled.
Print hidden slides - Forces PowerPoint to print any hidden slides which may exist in the presentation.
Scale to fit paper - Forces the PowerPoint slide to be scaled to the current page size.
Print What - This setting allows users to select the information to print from the document. The two options are to
print only the Slides or Slides and Notes. The 'Slides and Notes' option will place the slide at the top of the page and
any notes made by the creator at the bottom of the page.
244
Batch Processing
Color mode - Use this setting to adjust the color settings of the printed slide to either Pure black and white,
Grayscale, or Color.
Note: This setting only affects how PowerPoint will send the file to the printer, not the actual printed output. Setting
the mode to Color will not necessarily print in color. If color output is desired, the printer must also support color and
be set to color, and if printing to TIFF, the color reduction must be set to None or Reduce to optimal palette.
245
Word
This category contains options for Microsoft Word documents and will be used when printing to paper or converting to
TIFF through LAW.
Settings
Do not print headers - Disables printing of headers contained within the Word document. This can be
useful if the original document contains information in the header which is not desired in the printed output.
Do not print footers - Disables printing of footers contained within the Word document. This can be useful if
the original document contains information in the footer which is not desired in the printed output.
Force manual repagination before printing - This option causes Word to repaginate itself before printing
which can prevent the last line from running onto the next page in certain conditions.
246
Batch Processing
Log warnings for Word 95/6.0 documents - This option is used to log a warning message for the purpose
of reviewing these documents for possible formatting issues that can occur with some older Word
documents. This makes it easier to isolate, QC, and optionally reprint all Word 95 documents if needed.
Reveal hidden text - This option will reveal text in the output TIFF or hard copy that is not otherwise visible
due to the text matching the background color (i.e., white text on a white background) or text matching the
highlight color in the source document.
Note: This setting is not recommended unless it is an absolute requirement. It may slow the printing of
Word documents dramatically.
Show comments - This option enables the printing of comments included in the Word document if present.
Note: How comments appear in the printed output is dependent on the settings currently set in Microsoft
Word on the processing station. For example, if balloons are desired, the Track Changes Options in
Word should be set to Use Balloons > Always.
Printing of comments on the actual page where they occur is only available in Word XP and higher. In
prior versions, the notes will be printed after the last page of the document.
Show revisions - Some Word documents may also contain tracked changes which can be printed through
LAW by selecting this option. LAW will only print the changes that have been made to the document if Track
Changes has been enabled for the document.
Note: How revisions appear in the printed output is dependent on the settings currently set in Microsoft
Word on the processing station. For example, if balloons are desired, the Track Changes Options in
Word should be set to Use Balloons > Always.
Field Replacements
The Field Replacement options allow users to specify the actions LAW should take when encountering these types of
dynamic fields in a document.
Date/Time Fields - This option allows selection of one of five actions: Do not modify (print as is), Do not
print, Replace with date created, Replace with modified date, and Show field codes.
Filename Fields - This option allows selection of one of four actions: Do not modify (print as is), Do not
print, Replace path from filename, and Show field codes.
Both of these settings are useful for preventing Word documents from printing current date or file path information
which may only apply to the production machine and not to the project being printed.
247
Separator Pages
Separator pages can be optionally inserted before documents or folders during the Print and E-Print batch processes.
Separator pages are useful for keeping documents and folders separate from one another and organized when
dealing with hard copies. While pre-configured separator page and placeholder templates exist for the E-Print and
TIFF Conversion processes, LAW also allows the customizing of separator pages and placeholders for the E-Print,
Print, and TIFF Conversion batch processes. This topic discusses the creation of custom separator pages; for
information on the templates or other print functions, see the following topics: Print Options or E-Print/TIFF Output
Settings.
Separator pages and placeholders can be configured via the Separator Page Options form. This form is accessible
from three locations as it applies to three different processes. To access these options, first click Tools > Batch
Process to launch the Batch Processing dialog.
To configure separator pages for E-Print, click Options > E-Print Options from this dialog and choose the E-Print
category. Next, enable Print separator pages, choose <Custom> from the Template drop-down list, and then click
the Options button.
Note: After configuring separator pages for the E-Print process, remember to configure the tray settings below the
Print Separator Pages option. See the E-Print/TIFF Output Settings topic for more information.
To configure placeholders for excluded/unsupported documents, or documents that received errors, for the TIFF
Conversion process, click Options > TIFF Options and choose the TIFF Output category. Next, select one or both
248
Batch Processing
of the following options: Print placeholders for excluded/unsupported documents or Print placeholders for
documents that error during TIFF Conversion. Doing so will enable the Placeholder Template drop-down. Next,
choose <Custom> from the drop-down list and then click the Options button.
To configure separator pages for the standard image Print process, click Options > Print Options. Select the
Include separator pages option and then click the Options button.
The Separator Page Options dialog will appear after clicking the Options in any of the aforementioned dialogs. The
remainder of the topic will discuss the specific features available in this form.
Header and Footer

The Header and Footer sections are used to display custom information in the left, center, and/or right sections of the
top (header) or bottom (footer) of the separator page or placeholder. To display text in a particular section, enter the
desired text into the text box below the section in the Header and/or Footer areas. This text will then appear on the
separator page or placeholder during the print or conversion process. To select a font, font style, and font size, click
the button labeled with the letter "A" below the header sections if modifying a header. If modifying a footer, click the
249
button below the footer sections. The selected font and text settings for the header and footer sections are specific to
the currently selected placeholder type. If multiple placeholder types are available in the drop down box (possible with
E-Print and TIFF Conversion), each type of placeholder is allowed to display different text values using different font
settings.
Fields
The Fields section of the Separator Page Options dialog is used to choose which fields should appear on the
separator page or placeholder and also to configure options related to these fields. Most system fields and all user-
defined fields will appear in this list. The fields wrapped in < >'s are fields derived from the standard Default Template
for each placeholder type. Some of these fields will display calculated or formatted values on the separator pages to
match the output displayed on the Default Template.
Select fields by checking the boxes in the Include column beside the field name to be included on the output. The
Display As column can be used to force an alternate field name to be displayed on the separator page or placeholder.
To enter a new display name for a field, double-click in the Display As cell beside the desired field and then key in the
new name. If the Display As cell is blank, then the name in the Field Name column will be used.
Each of the three columns in the Fields grid may be sorted ascending or descending by clicking on the desired
column header.
Click the button labeled with the letter "A" to configure the font, font style, and font size for the field names and field
values.
The Fields section will be disabled when the Folder placeholder type is selected as field information does not exist at
the folder level. See the Options section below for more information on placeholder types.
When enabled (checked), the Do not print field names for blank values option will prevent the names of the
selected fields from appearing on the separator page for any documents that do not contain data in those fields. This
setting applies to E-Print, TIFF Conversion, and the standard Print batch processes.
For E-Print and TIFF Conversion jobs, the Show comments field option can be used to include or hide the
"Comments" system field which appears on placeholder pages that are generated for unsupported file types or files
that error during printing or conversion. By default, for unsupported file types, this field will contain the following
message: UNSUPPORTED OR EXCLUDED FILE TYPE. To customize this message, ensure "Show Comments
field" is enabled and then enter the desired text in the Unsupported file type message text box.
Options
The Options section of the Separator Page Options dialog contains a number of features to allow further customizing
of the separator pages or placeholders.
Placeholder Type - Separator page and placeholder settings can be configured for the types listed in the
drop-down. File separator pages will print in front of e-documents imported via ED Loader or XML load file.
Folder separator pages will be printed each time a new folder is encountered and will apply to the E-Print
and Print processes. The field selection will not apply to folder pages as the fields are only document- or
page-level. The folder path, in addition to the specified header and footer text, will be printed on each folder
separator page. E-Mail separator pages will be printed in front of e-mail records and other store-based items
including calendar items, contacts, tasks, journal entries, and notes. Attachment separator pages will be
printed in front of any attachment records loaded into the case using ED Loader and is based on the
Attachment value found in the _DocCat field. The File, E-Mail, and Attachment types will also be used as
placeholders for excluded/unsupported records or as an error placeholder during the TIFF Conversion
process.
The currently selected placeholder type will also appear in parentheses beside the Fields heading just above
the Selected Fields list. The placeholder type will be grayed out and set to "Raw Images" when viewing this
setting via the Print Options, since the other types will not apply to this process.
Synchronize field settings for all types - When enabled, the fields selected for the active
placeholder type (type selected in Placeholder Type drop-down) will be applied to the File, E-Mail,
and Attachment separator pages and placeholders. (Fields do not apply to Folder separator
250
Batch Processing
pages.) Also applied with this setting are the following: field fonts, Do not print field names for blank
values setting, Show Comments field setting, and the Unsupported file type message text box
value.
Margins - The separator and placeholder margins can be modified by entering the desired values in one or
more of the available text boxes: Top, Bottom, Left, and Right. The values should be entered as twips as
indicated in the interface (1440 twips = 1 inch). The margin settings are unique to each placeholder type.
Vertical field spacing (in twips) - Use this setting to configure the amount of white space between fields on
the separator pages and placeholders. The values should be entered as twips as indicated in the interface
(1440 twips = 1 inch). This setting is unique to each placeholder type.
Print Delays (in ms) - The print delay settings can be configured to cause a delay before (Pre-print delay)
and after (Post-print delay) pages print in an attempt to prevent a separator page from printing before a file
and vice versa (i.e. separator, separator, file, separator). Certain printers rearrange jobs in the spooler
causing the printing of smaller files first while larger files are still spooling. LAW cannot always prevent every
occurrence of this behavior but specifying a print delay can reduce the chances of this occurring. Enter
values in milliseconds (1000ms=1 second) and test various values to determine what works best in your
environment. The print delay values are unique to each placeholder type. The values will be forced to zero
and grayed out when configuring placeholders for TIFF Conversion.
Saving Default Settings

The Save settings as default option located at the bottom of the Separator Page Options dialog is used to save the
current settings as the default selections for new LAW cases. When this option is selected, the current settings will be
saved to a separator.ini file located in the application folder (same folder as law50.exe). The settings in this file will be
applied to all new cases going forward.
If settings are modified in a case and not saved as default, LAW will create a separator.ini in the case folder and
those settings and LAW will now utilize the settings in the case-level INI file for that specific case. LAW will always
look for the case-level separator.ini file before looking in the application path.
Note: This setting and the "Save settings as default" setting in the TIFF Options and E-print Options dialogs are
independent of each other. For example, if "Save settings as default" is enabled in the TIFF Options dialog, the
current separator page settings will not be saved or affected in any way.
251
Distributed Batch Processing

Distributed batch processing was designed to allow multiple LAW stations to process the same batch simultaneously,
while using the same settings that were specified on the machine that initiated the shared job. Only the documents
selected on this initial machine will be processed.
Shared processing is available for the following batch processes:
Image Cleanup
Endorse
OCR
TIFF Conversion
Update Page Data
When a shared batch has been generated, an INI file will be placed in the case folder
(\$UserData\BatchProcessing\All Users) that uniquely identifies the batch. This directory is scanned for INI files when
the Batch Process utility is launched and if any are present, the user will be given the option to "Join" processing.
Initializing a Shared Batch

To initialize a shared batch, first select Tools > Batch Process from the main menu. In the Batch Processing
dialog, select the documents to be processed. Users could also run a query or perform a filter in the grid and then
launch the Batch Process utility from the grid display.
Choose a batch process that is supported for distributed batch processing (see above) and then check the box
beside that process in the Processes section.
In the Sharing section of the Batch Processing dialog, check the box beside the Enable Distributed Batch Processing
option. Enter a Name for the batch.
This name is a reference for users to aid in identifying a batch and will appear on other workstations when prompted
to join. This batch name is also important for managing jobs in the LAW Management Console ("LMC").
The Type field reflects the currently selected invitation type. This value will determine how the job is handled by other
stations when utilizing the LMC. See the LAW Management Console Configuration topic for more information on
managing distributed batches.
Click Begin to start processing.
252
Batch Processing
Joining a Shared Batch

Once a distributed batch has been initialized on one station, other machines can join and assist with the processing.
To join, first open the same LAW case on another workstation. Then, select Tools > Batch Process from the main
menu. The Running Batches dialog will appear in front of the Batch Processing dialog. All active batches created in
this case will be listed.
Note: If the Running Batches dialog does not appear as expected, try clicking the Refresh button in the Sharing
section of the Batch Processing dialog. If a batch becomes available, click the View button to view the running
batch.
Locate the desired batch and highlight the name in the grid. Click Join. LAW will locate the next unprocessed
document in the batch and begin processing it using the same settings that were used when initializing the batch on
the other station.
Note: If "Cancel" is chosen on the Running Batches dialog, the batch will not be cancelled on other stations.
The batch may also be started by clicking View in the Batch Processing dialog in the Sharing section. This will launch
the Running Batches dialog as well and allow users to choose a batch to join.
Deleting Shared Batches

Once a shared batch has completed successfully, it will no longer appear as a "running batch" in LAW. To delete an
incomplete batch that is no longer needed, click the batch to select it in the Running Batches dialog. Next, choose
Edit > Delete. The shared batch will be deleted from the list.
253
LAW Management Console

LMC Overview
The LAW Management Console ("LMC") is a companion utility to LAW PreDiscovery versions 5.3.14 and above. The
purpose of the application is to monitor distributed batch processing jobs initialized in LAW and to eliminate several
steps by automatically joining LAW workstations to existing jobs. This application also displays license information for
workstations visible to the LMC. The information recorded on each workstation is stored in a central location and
shared with other LMC instances.
The LMC will run on each workstation running LAW PreDiscovery. When the LMC instances on individual
workstations are connected to the same SQL Server (the server used to create LAW cases), the machine names of
those workstations will be visible in the Clients node.
Client details can be viewed by clicking on the Clients node or on the client name(s). In addition to displaying clients
and client details, the LMC will also list distributed batch processing jobs in SQL cases.
Licensing details can be viewed by clicking the Licenses node or on an individual key. A tally of all licenses can be
viewed here as well as license details for each individual key.
These features are only applicable to jobs and workstations that have been made visible to the LAW Management
Console by LAW (see Configuration). The benefits of having these jobs and clients visible to the LMC includes the
ability to monitor multiple workstations from a single workstation as they perform batch processes, allow available
LAW workstations to join jobs automatically, and monitor license usage.
Startup
The LMC is included with the full installs of LAW as well as the updates. The application is located in the Console
folder within the LAW installation folder. By default, this location is C:\Program Files\Law50\Console.
The executable file used to run the LMC is LAWConsole.exe. The application can be started on each LAW machine
using one of two methods:
1. Double-click the LAWConsole.exe in the Console folder. The console may be started using the local
instance or using a shared EXE file. Please note, the local instance of the LMC will be used when using the
method listed next.
2. Check the option Start the Management Console on Windows Startup in LAW (Tools > Options >
Preferences). When the box is checked, and the LMC is not running, a message will appear prompting to
launch the LMC. Click Yes. The local instance of LMC will be launched at this time and will be executed
each time Windows is started.
255
Once the LMC is running, an icon will appear in the system tray. The icon will be green when the application
successfully connects ( ) and red if the application fails to initialize ( ). After the LMC is added to the system tray,
the application can be restored by single-clicking the icon in the tray or right-clicking and choosing Restore. Once
restored, the minimize and close buttons in the upper right-corner will both minimize the application to the system
tray, but not close the application. To completely exit the LMC, right-click the icon in the system tray and choose Quit
or press Alt+F4 on the keyboard while the application is in focus.
An LMC instance is referred to as a "client" throughout the related Help topics. A client represents a workstation
running an LMC instance; each LMC instance is represented by that workstation’s computer name.
See the Configuration topic for information on the initial configuration of the LMC and creating batches in LAW.
256
Configuration
The LAW Management Console ("LMC") can be used to view a list of active distributed batch processing jobs (also
referred to as shared jobs or batches in the Help topics), the progress of the jobs, information about connected clients
(workstations running the LMC and connected to the same SQL Server), and also has the ability to automatically join
LAW to an existing shared job. The LMC also provides a list of license keys located on workstations that are visible to
the application. With minimal initial configuration, the LMC can begin providing these services and eliminate multiple
steps involved with distributed batch processing and license tracking.
Initial Configuration of the LMC

The LMC requires a connection to SQL Server in order to run and only supports SQL-based LAW cases for the
management of distributed jobs. The SQL Server used when connecting the LMC should be the same instance used
to create the cases in LAW. When the LMC is launched for the first time on a machine (see LMC Overview), it will
attempt to pull SQL information from the law50.ini file in the application path ([SQL Server] section). If this information
is not available, or the LMC is unable to connect to the server at that time, an introduction screen will appear.
Three options are presented:
1. I have a SQL Server and would like to configure the LMC client to remotely manage shared batch
processing jobs. - When this option is chosen, the Server Connection Information dialog will appear. Enter
the SQL login information (see Configuring LAW and SQL Server) and then click Accept. If able to connect
successfully, the LMC icon will turn green, the LMC main interface will appear, and the current workstation's
machine name will be listed in the Clients node in the left panel. If unable to connect successfully, the icon
will remain red, an error will appear in the right panel of the main interface, and the SQL Connection
Information dialog will reappear also displaying the error message.
257
2. I do not want to configure the client right now, but would like it to remain running in the system tray
for future configuration. - When this option is chosen, the LMC icon will remain red and it will be minimized
to the system tray. The introduction screen will appear once again if the application is restored at a later
time. To remove the application from the system tray, right-click the icon and choose Quit.
3. I do not have a SQL Server or do not plan to use the client. Close the client and remove it from
system startup. - When this option is selected, the LMC will be completely closed and removed from
startup. To launch the LMC at a later time, use one of the methods discussed in the LMC Overview. The
introduction screen will appear once again and the three options listed here will be presented.
If the LMC was able to locate SQL information from the law50.ini and was able to connect successfully, the LMC will
bypass the introduction screen and the main interface will appear, displaying the machine name of the current
workstation below the Clients node. The first panel in the task bar in the main interface will also display a status of
"Connected to" followed by the server name.
258
Configure the LMC clients on other workstations when running the LMC client locally rather than using a shared EXE.
Remember, in order to view information about other workstations running the LMC client, the clients must be
connected to the same SQL Server.
To change the SQL Server used with the LMC, click Server > Connect from the main menu, and then enter the SQL
Server name and credentials. To disconnect from the current SQL Server, click Server > Disconnect.
Creating a Shared Batch in LAW

In order to utilize the batch processing management features provided by the LAW Management Console, the
distributed batch process must be created in a SQL case. When the Batch Processing dialog is launched, the LMC
will pull SQL Server information from a local configuration file (%AppData\LawConsole\LAWConsoleSettings.ini). If
this file is not present or does not have valid SQL information, then the LMC will use the SQL information stored in
the application path (LAW50 folder) in the law50.ini file. When a job is visible to the LMC, that job’s progress will be
visible to the LMC.
Create or open a SQL LAW case to create the shared batch. Click Tools > Batch Process. Select one or more of
the six processes supported for job sharing:
Image Cleanup
Endorse
OCR
TIFF Conversion
Update Page Data
Enter a name for the batch in the Name text box. Next, view the invitation “Type” listed below the Name field.
259
All shared jobs are created with an invitation. The invitation controls whether LMC instances that can see the job
(connected to the same SQL server) will instruct LAW to join the shared job. The invitation can also be edited at any
time from an LMC instance by selecting the corresponding job node and clicking the ellipses button to the right of the
invitation description in the right hand panel.
260
Note: Changing an invitation only affects the behavior of LMC instances that have yet to auto-join the job. If the
invitation is changed after five stations have joined, those five stations will be unaffected by the change in the
invitation and will continue processing. If one of those five stations was restarted, then it would be subject to the
change in the invitation.
There are currently three types of invitations:
1. Closed: (Default) None of the LMC instances will be able to auto-join LAW to the shared batch. LAW
workstations can still be joined to the job manually by clicking Tools > Batch Process and then Join from
the Running Batches dialog.
2. Open: All LMC instances will auto-join LAW to the shared batch. Provided the criteria in the "Auto-joining
Jobs" section (below) have been met, instances of LAW on other workstations will be joined to the job
automatically.
3. Restricted: Only LMC instances specified in the Create/Modify Job Invitation dialog will auto-join LAW to
the shared batch. Check the boxes beside the desired clients. Clients not selected in this dialog will not
attempt to join the batch.
In addition to the type of invitation, the invitation may contain a timestamp restriction.
If the invitation specifies that the job cannot be joined until after a certain time, then this will take precedence over the
invitation type. For example, if a shared batch is created named TIFF01 and the invitation type is set to Open, but the
user specified that the job cannot be joined until 1 am, then the job will be ignored until after 1am.
Once the shared batch has been initialized on a machine, the job will appear below the Jobs node in the LMC.
Other LAW workstations can now join the job automatically provided certain criteria are met. The next section
discusses these criteria in more detail.
Automatically Joining Shared Jobs

The LMC's ability to join LAW workstations to a shared job in an unattended manner relies on certain conditions. If
these conditions are met, LAW will launch, open the SQL case, and begin processing the job without user interaction.
Jobs will be joined in the order in which they were created, but are sorted visibly by name under the Jobs node.
1. The LMC client must be running on the machine.
a. The LMC client must be connected to the same SQL server in which the case database is stored in
order to see the job. Similarly, LMC clients must be connected to the same SQL server in order to
“see” each other in the console.
2. LAW is not running.
3. Invitation must be set to Open or Restricted; if Restricted is selected, the applicable machine name(s) must
be selected in the invitation editor when creating the batch or at any time via the LMC.
4. The station is in a "system idle" state (see Operation).
261
a. The system idle timeout value for each client station must be greater than 0. This value is set within
the LMC in Tools > Options > General > System Idle Timeout. When the workstation is idle (no
keyboard or mouse movement) for the specified number of seconds, the second panel in the status
bar will change to "System Idle: YES" on the LMC will attempt to join a job provided all other criteria
have been met.
5. The client is not Excluded (see Operation).
6. The job’s status must be Active (see the Operation topic for possible job status values).
As discussed in the Distributed Batch Processing topic, jobs can also be started manually by opening LAW, opening
the case, and joining the batch process (Tools > Batch Process). If a companion LMC instance is running, it will
report the station’s progress in the same fashion as if the LMC asked LAW to join the job. Invitations and Exclusions
(see Operation) do not restrict a manual join. Currently, LMC does not indicate if a job was joined manually vs.
automatically.
The Operation topic will discuss the components of the LMC interface and application usage.
262
Operation
Once the LMC has been configured and one or more shared batches are visible within the LMC (see Configuration),
the LAW Management Console can be used to manage and monitor processing as well as join available LAW
workstations to existing processes for faster completion. Multiple views are available in the LMC to monitor these
clients and workstations. The LMC can also report license usage for these LMC-visible workstations.
Client Overview
Selecting the main Clients node will display an overview of information about these workstations in the right panel.
The number in parentheses beside the term "Clients" is the number of clients (workstations running the LMC)
connected to the same SQL Server and visible to the current instance of the LMC.
The clients overview panel displays the following information about each client:
Computer - Machine name of the connected client.
Running - Indicates if LAW is running on the workstation.
User - Displays the user currently logged in on the workstation.
LAW Version - Displays the name of the LAW case currently open on the workstation.
Case - Displays the name of the LAW case currently open on the workstation. If LAW is not running, this
field will be blank.
Status - Displays the status of the workstation. Possible values are:
263
Online - Connected to SQL, visible to other LMC clients, and not working on a job.
Starting - Preparing to begin batch processing.
Working - Working on a shared batch process.
Cancelling - In the process of cancelling a batch.
Job Name - Corresponds to the value entered in the Name field when creating the batch in LAW (Tools-
>Batch Process dialog).
Last Updated (Server time) - Stores the server date and time the workstation's information was last
updated.
In addition to the information provided in the grid, the clients overview screen also contains two buttons:
Screenshot - Produces a screenshot of the workstation currently selected in the grid in the right panel. This
tool is useful for monitoring the state of the workstations when processing jobs or preparing to process jobs.
Leave Job - Forces the currently selected workstation to silently leave the job being processed. Once a
workstation is forced to leave a job in this manner, it will automatically join the Excluded Clients list for the
job it was working on (see the Excluded Clients explanation in the Job Details section within this topic).
Client Details
Each individual online client will be listed below the Clients node in the left panel of the LMC. The client name
preceded by an asterisk is the workstation currently being used. A client name in bold indicates that client is currently
working on a shared job. When an individual client is selected, the right panel provides additional information specific
to that client.
264
Three sections exist in this panel, each including a number of fields with information about the currently selected
client: Client Details, LAW Details, and Job Details.
The Client Details section contains five fields and one button:
Status - Displays the status of the current workstation (Online, Starting, Working, or Cancelling). See the
above Client Overview section for descriptions of these status values.
User - Displays the user currently logged in on the workstation.
Workstation - Displays the machine name of the selected workstation.
IP Address - Displays the IP address of the workstation.
Console Version - Displays the version of the LAW Management Console. Typically, this version should
match the LAW version shown in the LAW Details section.
Screenshot - Produces a screenshot of the currently selected workstation currently selected in the grid in
the right panel.
The LAW Details section also contains five fields:
Running - Displays a "True" value if LAW is running and a "False" value if LAW is not running. If LAW is
running, the other fields in this section will also be populated with data. If the value is "False", only the LAW
version will appear and the remaining fields will be populated with "N/A."
Case Name - Displays the name of the LAW case currently open on the workstation.
LAW Version - Displays the name of the LAW case currently open on the workstation.
Profile - Displays the name of the system or user-defined license profile currently in use.
Detail - Lists the name of all license modules currently checked out on the workstation.
The Job Details section also contains five fields and one button:
Progress - Displays the total number of records in the batch and the document currently being processed
(i.e., 4 of 154).
Document - Displays the document number (i.e., Doc #5 which means the fifth document in the current
folder) and the path relative to the root case folder.
Doc Name - Refers to the document number listed above and is combined with the file extension of the file
being processed.
Filename - Displays the original filename of the document for EDD records and is blank for non-EDD or
records without native files.
Leave Job - Forces the currently selected workstation to silently leave the job being processed. Once a
workstation is forced to leave a job in this manner, it will automatically join the Excluded Clients list for the
job it was working on (see the Excluded Clients description in the Job Details section in this topic).
Job Overview
Selecting the Jobs node will display an overview of information about active shared batch processing jobs in the right
panel. The number in parentheses beside the term "Jobs" is the number of jobs currently visible to the LMC.
265
The jobs overview panel displays the following information about each client:
Name - Corresponds to the value entered in the Name field when creating the batch in LAW (Tools > Batch
Process dialog).
Case - Displays the name of the LAW case currently open on the workstation. If LAW is not running, this
field will be blank.
Status - Displays the status of the job. The possible status values are:
ACTIVE - Jobs that can be joined by clients and are visible to the LMC. If a user manually joins a
batch in LAW, then the corresponding job’s status is always set to ACTIVE regardless of its
previous status. For example, if a global cancellation was issued for a job, and a user manually
joins the batch, the corresponding job’s status is set to ACTIVE.
CANCELLED - Jobs that have been suspended, are visible to the LMC, and can be restarted via
the Start Job command.
INACTIVE - Jobs that had their corresponding batch deleted in LAW (via the Running Batches
dialog) or were removed from the LMC by right-clicking the job node and selecting “Remove Job.”
These jobs are not visible to the LMC.
#Clients - Displays the number of clients currently processing the job.
%Comp - Displays the percentage of completed documents in the batch.
Errors - Displays the number of errors that have occurred during the batch processing.
Invite - Displays the type of invitation selected when the batch was created (see Configuration) or the type it
was changed to if this field was modified within in the LMC.
Processes - Lists the processes selected when the batch was created, such as TIFF, OCR, or Endorse.
266
In addition to the information provided in the grid, the clients overview screen also contains two buttons:
Cancel Job - Cancels the batch for all clients but does not delete the job from LAW. See the Cancelling
Batches section in this topic.
View Errors - Launches a viewer displaying errors that have occurred during a batch. Errors from every
LMC-visible machine processing the job will be displayed here; the machine the error occurred on is listed in
the grid. Error logs can be saved to .csv or .txt files from this viewer, shown below:
Job Details
Each individual job will be listed below the Jobs node and job-specific information will be displayed when selected.
267
The Job Details section contains six information fields, a Cancel Job button, and the invitation editor:
Case Name - Displays the name of the LAW case currently open on the workstation.
Processes - Lists the processes selected when the batch was created, such as TIFF, OCR, or Endorse.
Req. Lic - Lists the license modules required in order to work on the batch.
Job Status - Displays the status of the job. See the Jobs Overview section for the possible values for this
field.
Created - Displays the date and time the batch was created and the user who created the share batch.
Invitation - Displays the invitation type for the current job. This invitation can be edited by clicking the
ellipsis button beside this field.
Cancel Job - Cancels the batch for all clients but does not delete the job from LAW. See the Cancelling
Batches section in this topic.
The Job Progress section contains four fields and the View Errors button:
Complete - Displays the total number of documents completed thus far in the batch.
Remaining - Displays the estimated amount of time remaining in the batch.
Total - Displays the total number of documents included in the batch.
Errors - Displays the number of errors that have occurred thus far in the batch.
268
View Errors - Launches a viewer displaying errors that have occurred during a batch. (A screenshot of the
error viewer is in the above Job Overview section.)
Three tabs also exist in this Job Details panel:
Clients - This tab displays each client working on the job, the process currently taking place on the machine
(i.e., OCR), and the document currently being processed.
Client Activity - Use this tab to view client activity specific to the selected job. Entries will appear when a
client attempts to join a job, successfully joins a job, fails to join a job, is excluded from a job, etc.
Excluded Clients - When a client is excluded from a job, the machine name and reason for the exclusion
will appear here. A client can be excluded from a job two ways. The first is if the LMC requests LAW to join a
job and LAW fails three times (maximum retry attempts). The second way is if a client requests that another
client ”leave” a job. Excluded clients can be viewed on the job details panel->Excluded Clients tab. Clients
can be removed from this list by selecting the client in the list and selecting Remove.
The Save button can be used to save the log to a .txt file. Use the check boxes to filter the type of activity shown in
the log.
Logs
All exception types have their messages logged into a main application log. The last 500 entries that were logged
during the application session are made visible on the Logs tab. The current session log can be saved to disk by
selecting the “Save” button. The entire log is stored in %APPDATA\LAWConsole\LAWConsole.log. This log contains
data from multiple application sessions and has a maximum size of 5MB.
269
Application Settings
Settings specific to the LAW Management Console are accessible by clicking Tools > Options with the main LMC
interface. Three categories exist in Options dialog:
General
System Idle Timeout - When the number of seconds specified in this field has been reached
without any movement on the workstation (no interaction with machine such as mouse movement),
the LMC will change the second panel in the task bar to "System Idle: YES." This idle state is a
requirement that must be met in order for the LMC to automatically join LAW to a shared batch
process (see Configuration). Setting this value at "0" (zero) will disable idle mode and LAW will
never be automatically joined to jobs. The second panel in the task bar will indicate the idle timer
has been deactivated at this point.
Polling Interval - The LMC updates its status to the database at the specified polling interval and
retrieves data about other online clients; the interface is then updated with this new data. It is
important to note that the LMC is a single threaded application and therefore user-interaction with
the interface incurs a small delay while it is updating the interface. Under normal conditions this is
extremely negligible and almost cannot be noticed. This delay can be mitigated somewhat by
reducing the polling interval. The lower the value, the less latency experienced in the interface, but
the trade-off is network and database traffic. The default value is 10 seconds.
LAW
Law50.exe - When the LMC automatically joins LAW to a shared batch process, the instance of
LAW to be launched is determined by this setting. Typically, if the environment is using a shared
Law50.exe mapped from a server instance of LAW, then it is recommended this Law50.exe is used
for processing.
Network
Enable Remote Refresh Requests - This option is used to decrease latency in client to client
operations, such as screenshots and Leave Job requests. The console communicates actions
between clients by utilizing a centralized message store. When a client requests an action from
another client, the message is placed into the store, and the recipient client retrieves the message
the next time it refreshes. Since clients refresh at an unsynchronized interval, there could be a
delay in retrieving the message by the recipient client. This option sends a UDP packet to the
recipient client requesting that it refresh immediately, thereby reducing the time it takes to retrieve
and process the message. The Port setting refers to the active port for the current client instance.
The LMC is aware what ports other clients are connected to, so it is not necessary that this value
be the same for all clients, but for ease of configuration it is recommended. When the application
initializes, or changes are made this setting, an entry is placed into the application log indicating the
state of the UDP Listener.
Cancelling Batches
In addition to manually cancelling batches in LAW via traditional means, the LMC offers two mechanisms for issuing
cancellations. An entire job can be cancelled (global job cancellation) or a specific client can be asked to leave a job
(client-level Leave Job request). Global job cancellations are issued via the Cancel Job command found on the job
overview and individual job detail panels. When a global cancellation is issued, the job’s status is set to
CANCELLED. Any instances of LAW currently working on the batch will see the job’s status has changed and will
cancel out of the batch. Conversely, if the job’s status is CANCELLED, the same command “Cancel Job” will now
read "Start Job." This command will change the job’s status to ACTIVE, thus making it available for clients to join.
Client-level cancellations are issued via the Leave Job command found on the client overview and individual client
detail panels. This command will only be enabled for clients that are currently working on an LMC-visible job. When a
Leave Job request is made, a message is sent to the LMC client who in turn passes the cancellation request to its
companion LAW instance. When this message is sent, that target client is then excluded from the job so it will not
attempt to re-join that job. To allow the client to re-join the job, remove it from the excluded clients list. Excluded
Clients are explained in the above Job Details section within this topic.
270
LAW's action after the cancellation may differ depending on how LAW was started. If LAW was started manually, and
was joined to the batch via traditional means, then LAW will behave in the same manner as if the Cancel button was
clicked. If LAW was started in an automated fashion via the LMC, then LAW will silently cancel and then shut down.
License Overview
Selecting the main Licenses node will display a summary of license information pulled from LMC clients in the right
panel. The number in parentheses beside the term "Licenses" is the total number of keys on workstations running the
LMC, connected to the same SQL Server, and visible to the current instance of the LMC.
Note: If a workstation is accessing licenses, but not running the LAW Management Console, not connected to SQL,
or is connected to a different instance of SQL than other workstations, that workstation's license usage will not be
reported in the LMC interface.
The licenses overview panel displays the following information:
License - Lists all license modules found on the keys listed below the Licenses node.
Total - Displays a total count of each license module found on the collection of keys listed below the
Licenses node.
In Use - Displays a total count of license modules in use on workstations running the LMC and connected to
the same SQL Server (for all keys listed below the License node).
Available - Displays a total count of available licenses for each module for all keys listed below the Licenses
node.
271
Clients using '<license module>' - Displays a list of clients using the module selected in the license
module list. The machine names and user names will be displayed.
License Details
Each individual license key will be listed below the Licenses node in the left panel of the LMC. As mentioned, only
clients connected to the same SQL Server instance and running the LMC will report their key usage to the LMC. The
details panel will look very similar to the overview panel with some exceptions. The license key number will appear in
the blue banner above the list of modules and the license modules and counts will be specific to that key only. The
location of the key (machine name and IP address) and expiration date (if applicable) will appear in a banner at the
bottom of the panel.
272
Deduplication Utility
Deduplication Utility
The Deduplication Utility will attempt to deduplicate records in the LAW case against each other and flag the
necessary fields to indicate the status for each record. This utility may be used if deduplication was not performed
when importing via the Electronic Discovery Loader or using the Inter-Case Deduplication utility. See the
Deduplication Information topic for more information.
The Deduplication Utility can be launched by clicking Tools > Deduplication Utility from within LAW. The utility
contains three tabs, discussed below: Info, Tools, and Settings.
Info Tab
If the current case has already been deduplicated externally using the Inter-Case Deduplication utility, a warning
message will appear when the utility is first launched:
Warning: As indicated in the warning message above, use of the internal Deduplication Utility after the case has
already been deduplicated against other cases using the Inter-Case Deduplication utility is not recommended.
Doing so will present a mixture of internal and external duplicates and could cause problems when purging, filtering,
or reviewing duplicate records. Click the X in the upper right corner to close the dialog.
Proceeding with the internal deduplication after clicking the "Yes I understand and wish to continue" button will
result in the external deduplication database being placed in Rebuild/Flush mode. At this point, the current case
should be removed from the external database. Also, before running the internal deduplication, it is recommended
that the Deduplication Status Reset command (see "Tools Tab" section below) is executed to clear the values
assigned by the Inter-Case Deduplication utility to prevent the mixture of internal and external duplicates. For more
information, see the Inter-Case Deduplication topic.
If the case has not been already deduplicated using the Inter-Case Deduplication utility, the Info tab will appear
displaying a Load button.
273
Click the Load button to retrieve the current deduplication statistics for the LAW case, such as number of duplicates
(global or custodian level) and number of root duplicate records.
274
Deduplication
If deduplication has not yet been performed on the records, the values for each displayed item will be zero. If records
had been deduplicated externally (see above), two additional rows would be included here to show the "Records
deduplicated externally" count as well as the "External deduplication database" path. Click on each item in the Info
tab to view its description as shown in the above image.
Tools Tab
The Tools tab currently contains two utilities related to the deduplication process.
The Deduplication Status Reset tool will flush all items from the current deduplication log and reset the
deduplication-related fields for all records in the case. In other words, the entire case will be in a state as if
deduplication has never been performed. This command does not flush items from external deduplication databases
but will reset the LAW deduplication fields that were updated as a result of inter-case deduplication (see Inter-Case
Deduplication for more information). As mentioned above, it is recommended to run this command on a case before
running the deduplication process via the Deduplication Utility if a case has already been deduplicated using the
Inter-Case Deduplication utility.
The Verify Deduplication Log tool will verify that all entries in the log exist in the LAW case. This tool is included for
troubleshooting purposes and does not check external deduplication databases.
Settings Tab
The Settings tab contains processing and processing range options.
275
Working digest - This setting is used to select the hash key to be used for determining duplicates. The
hash values are obtained through metadata fields (e-mail) or by hashing the entire file (e-docs). LAW
provides two hash keys to choose from: MD5 (128-bit output) and SHA-1 (160-bit output).
Test for duplicate against (Scope) - This setting pertains to the scope in which duplicates are tested.
Deduplication can be performed at one of two levels: Case Level (globally deduplicates against all records in
the database) or Custodian Level (deduplicates against records with the same custodian value).
Only test untested records - When enabled, this option will force LAW to only process records that have
not been tested previously in the deduplication process. This feature may be useful when a case has been
deduplicated previously and then new records are added (and deduplication was not enabled during the
import). If the "Only test records with selected custodians" option is also enabled, only untested records with
the specified custodian values will be tested.
Only test records with selected custodians - When enabled, this option allows the specification of one or
more custodians and forces LAW to process only records with those custodians during deduplication. Click
the Select button to launch the Custom Value Selection [Custodian] dialog.
276
Deduplication
Check the boxes beside the custodians to include them in the deduplication process. Click Accept to save the
changes and close this dialog. The number of selected custodians will appear beside the Select button in the
Settings tab.
The Reset button can be used to reset any options that were modified in the current session. Click Start to initialize
the deduplication process.
277
Inter-Case Deduplication
Records can be deduplicated against other records in a LAW case and against incoming records during the electronic
discovery import process (see Deduplication), after the import against other records in the case (Deduplication Utility
in LAW), or after the import against other records in the case and other LAW cases (covered in this topic). Once a
case is deduplicated externally using the Inter-Case Deduplication utility, the case should not be deduplicated using
the internal Deduplication Utility, and incoming documents should not be deduplicated using ED loader. Doing so can
lead to issues with purging, reviewing, and filtering duplicate records caused by a mixture of internal and external
duplicates existing in the case. See the Deduplication and/or Deduplication Utility topics for more information about
these risks and associated warnings.
Unlike other methods, the Inter-Case Deduplication utility enables deduplication across LAW cases. A master
database (separate from the LAW database) is created to house the deduplication information for the cases. These
cases are ready for inter-case deduplication once they have been populated with records via the ED Loader import.
Records added to these cases during subsequent imports can also be deduplicated.
To start, open the utility by clicking Start > All Programs > LAW PreDiscovery > Inter-Case Deduplication Utility
or double-click the InterCaseDedup.exe file in the \Law50 folder (same folder as Law50.exe file). The Inter-Case
Deduplication dialog will appear.
278
Deduplication
External Deduplication Database

The first step when using this utility is to create a new database (or open an existing database). The external
deduplication database is a "master" Access database (*.MDB file) that will contain deduplication information for each
LAW case added to it during an inter-case deduplication session. This database is completely separate from the LAW
case database; however, the utility will obtain information from the LAW case databases during the deduplication
process.
To create the external deduplication database, click the New button or choose File > New. It is recommended that
this database be placed in a shared location accessible to all member cases (see "Member Cases"). Browse to the
desired location in the Create Deduplication Database dialog, change the file name or use the default (DuplicateLog),
and then click the Save button. The path to the database will now be displayed. The "Mode" value will change from
"No Database Selected" to "New" at this time. As noted in the description in the interface, this mode indicates that all
documents in the member cases will be deduplicated against each other. The next step is to set the deduplication
options (see the "Options" section below).
To open an existing database from a previous deduplication session, click the ellipsis button to the left of the New
button or choose File > Open, browse to the external deduplication database, and then click Open. If the database
has already been used in the inter-case deduplication process, the Mode will change to Resume/Append. See the
"Deduplication Mode" section in this topic for more information.
Options
Two deduplication options are available for the inter-case deduplication process:
1. Digest - The digest refers to the type of hash that will be used to determine duplicates. The hash values
are obtained through metadata fields (e-mail) or by hashing the entire file (e-docs) during the ED Loader
import process. Two options are available:
a. MD5 (128-bit output digest) - This hash value is stored in the MD5Hash field in LAW for each
document.
b. SHA-1 (160-bit output digest) - This hash value is stored in the Sha1Hash field in LAW for each
document.
2. Scope - This option refers to the scope in which duplicates are tested. Two options are available:
a. Global - Records will be deduplicated against all records in all member cases.
b. Custodian Level - Records will only be deduplicated against others records with the same
custodian assigned. Records with no custodian value set will be evaluated globally.
Once the desired options have been set, move to the Member Cases area to add LAW cases. These cases will be
deduplicated against each other in the inter-case deduplication process. See the "Member Cases" section for details.
Member Cases
The member cases are LAW cases that are added to the external deduplication database with the intention of
deduplicating them against each other. These cases must be ED-enabled, and both SQL and Access cases are
supported. This type of deduplication is intended for cases that are already populated with documents imported via
the ED Loader. If documents are added to the cases after the inter-case deduplication process, they can be
deduplicated against the other records as well. See the "Resume/Append Mode" section below for details.
279
To begin adding cases, click the Add button or choose Case > Add. Browse to the project.ini file for the case
(contained in the root LAW case folder) and then click Open. Cases can also be added to the list by dragging and
dropping one or more root case folders (folder containing the project.ini) or the project.ini file itself into the Member
Cases grid. Once added, the case names and paths will be listed in the grid and the number in parentheses beside
Member Cases will increment by one for each added case. Since the cases are validated at the time they are added
to the grid, an error will occur at this time if the case does not meet the requirements for inter-case deduplication,
such as the case not being ED-enabled.
Once the member cases have been added, the Up and Dn keys (or Case > Move Up | Move Down) may be used to
specify the order in which records are deduplicated. The first case shown in the grid will be processed first, the
second case is next, and so on. These buttons can only be used in New or Rebuild/Flush mode.
The Remove button (or Case > Remove) can be used to remove the selected LAW case from the Member Cases
grid. The Clear button (or Case > Clear) will remove all cases from the grid. These buttons can only be used in New
or Rebuild/Flush mode.
Deduplication Process
Once the external database has been specified, the options have been set, and the member cases have been added,
click Begin to start the inter-case deduplication process. The Inter-Case Deduplication Progress screen will appear.
This screen will display, via the Operation field, the series of steps (five total) that take place during the deduplication
process. The Progress area provides both visual (progress bar) and textual indicators of how much work is
remaining and what has been done thus far. The Errors value is a count of all errors that occurred during processing.
The total error count will be displayed in a summary screen once processing has been completed. See the
"Summary" section below for more information regarding errors and logging.
Process Summary
The Summary screen will appear once the deduplication process has been completed, canceled, or aborted due to
some sort of error condition. For a successful process, the summary will show the Digest and Scope options that
were selected and the total number of member cases included in the process. The summary will also list total counts
for documents loaded, duplicate records, and errors at a case level. The "Documents Loaded In This Session" value
is the total number documents, not including any attachment records, that were loaded in the current deduplication
session. The "Duplicates" value will show the total number of duplicates in each listed case and also does not include
any attachment records in the count.
280
Deduplication
If errors occurred during processing, a View Errors button will be included at the bottom of the Summary screen.
Click this button to view the error details. The log file that appears is stored in <drive>\Documents and
Settings\<user>\Application Data\Law50\LawInterCaseDedup\LawInterCaseDedup.ErrorLog.txt. The Elapsed field
displays the amount of time that has passed during the process.
If an error occurs during processing that aborts the deduplication process completely, the Summary screen will
appear with a message stating the process was aborted. Similar behavior will occur if the process is cancelled by the
user. The Summary screen will appear with a message stating the process was cancelled.
Note: Errors that halt processing or cancelling the deduplication process will both result in the database entering
Rebuild/Flush mode. See the "Deduplication Mode" section for details.
The contents of the summary can be saved to a text file by clicking File > Save As from the Summary screen.
Browse to the desired location, enter a file name, and then click Save.
LAW Deduplication Fields

LAW contains a number of system fields to store deduplication-related information about each document in a case.
The Inter-Case Deduplication utility writes to two of those fields (_DupID and _DupMethod) differently than the ED
Loader deduplication and Deduplication Utility in LAW. Please see the Deduplication Information topic for a list of
these fields, their descriptions, and possible values. Field information for all LAW fields can also be found in the Field
Descriptions topic.
Deduplication Mode
The Mode indicator shown below the External Deduplication Database path will display one of four possible mode
values:
281
1. No Database Selected - This mode will be set when no external deduplication database is selected. See
the "External Deduplication Database" section above for information on creating and opening existing
databases.
2. New - This mode will be set when the selected external deduplication database has not yet been involved in
the inter-case deduplication process. The New mode will occur when a new database is created or when an
existing database is selected but has not yet been through the deduplication process.
3. Resume/Append - This mode will be set when the selected external deduplication database has already
been through the deduplication process. When the external database is in this mode, only documents added
to member cases since the database's previous deduplication session will be added and deduplicated
against each other and the existing documents in the database. When the process is run again on this
existing database, the Summary screen will show the total number of documents added in the session
(documents loaded in member cases after previous deduplication session) and the total number of
duplicates in the cases.
4. Rebuild/Flush - This mode indicates that the external database was previously in Resume/Append mode,
but a change was made to one of the member cases that requires that the external database be rebuilt.
Functionally, this mode is the same as the New mode, as the cases will need to be re-deduplicated once this
mode has been assigned. A "Click here for 'Rebuild/Flush' details" link will become available beside the
mode value. Clicking this link will launch a message box that lists the reasons why the deduplication
database was placed in Rebuild/Flush mode. The following actions are possible reasons for this mode or
occur:
a. Cancelling the inter-case deduplication process
b. Deleting a document from a member case
c. Renaming, removing, or adding a custodian in a member case when the Custodian Level scope
was used
d. Deduplicating a member case using ED Loader's Deduplication or the internal Deduplication Utility
The Refresh button can be used to inspect member cases for changes that may the mode. If changes are detected,
the mode will be updated to the correct state.
Reviewing Duplicates
The Duplicate Viewer is a tool that can be used to review records in a case or multiple cases that have been flagged
as duplicates by one of LAW's deduplication methods (ED Loader Deduplication, Deduplication Utility, or Inter-Case
Deduplication). Please see the Duplicate Viewer topic for details.
282
Deduplication
Duplicate Viewer
The Duplicate Viewer is a tool that can be used when reviewing records in an ED-enabled case that have been
flagged as duplicates by one of LAW's deduplication methods (ED Loader Deduplication, Deduplication Utility, or
Inter-Case Deduplication). This viewer presents a tree view of these duplicate documents and makes it possible to
click on a record, immediately see whether or not the record is a duplicate or has duplicates, and quickly navigate to
any duplicates that exist in the current case or other LAW case.
The Duplicate Viewer will always display on top of the main LAW form. Navigating documents via the main document
list or one of the grid displays will also update the viewer, ensuring the duplicate information matches the current
record. Please note, attachment records are not listed in the Duplicate Viewer.
To launch this viewer from the main interface in LAW, click Tools > Duplicate Viewer. The appearance of the dialog
upon launching will depend on whether or not a document is selected, and if a document is selected, whether or not
that document is a duplicate.
If a document is not selected when the viewer is launched, the viewer will look similar to the below image.
Figure 1
If a document is selected that is not a "parent" duplicate (DupStatus=P) or not a duplicate record (DupStatus=G or C),
the viewer will look similar to the below image. The DocID in the viewer matches the LAW DocID field value for the
selected record. If the DocID field is not populated, LAW's "ID" field will be used instead.
283
Figure 2
Records Deduplicated Internally

The examples in this section include records that were deduplicated internally via ED Loader deduplication or LAW's
Deduplication Utility.
If a parent duplicate is selected in a case, the viewer will look similar to Figure 3. Parent documents are shown as the
parent node in the tree view within the Duplicate Viewer. In this example, the parent record is DocID ID00001 and
has a _DupID (and ID) value of 4. The parent document has one duplicate which exists in the same case. The
duplicate record's DocID is ID00004 and has a DupStatus of G, which indicates it is a global duplicate (of ID00001).
Clicking the DocID of the duplicate in the viewer will force LAW to automatically navigate to the duplicate record
within the case.
Figure 3
If a record has multiple duplicates, the duplicate records will be represented in the same manner - as entries below
the parent node (see Figure 4).
284
Deduplication
Figure 4
Records Deduplicated Externally

The examples in this section involve records that were deduplicated externally via the Inter-Case Deduplication
Utility.
Warning: When cases are deduplicated using the Inter-Case Deduplication Utility, the Duplicate Viewer relies on
the external deduplication database to retrieve deduplication information. If the database is moved, renamed, or
deleted, the Duplicate Viewer will display an error (see image below). This error will also be displayed if the viewer
is launched while the associated external deduplication database is being accessed during a deduplication process.
In Figure 5, a parent record is selected (ID00008, _DupId=6) and the duplicate record (ID00018) is located in the
same LAW case, CaseA01. The Duplicate Viewer will include a case name in the parent entry and a case name node
(CaseA01 in Figure 5) above duplicate records when the records were deduplicated externally.
Clicking the DocID of the duplicate in the viewer will force LAW to automatically navigate to the duplicate record
within the case.
285
Figure 5
In the next example (Figure 6), a parent duplicate is selected and the duplicate document is located in a different
LAW case. The parent, DocID ID00002, exists in case CaseA01 and has a _DupID of 2. The duplicate record is
located in case CaseA02 and has a DocID of ID00020.
Clicking the case node (CaseA02 in Figure 6) will force LAW to switch to that case. To navigate to the actual
duplicate record in the other case, click the DocID of the duplicate in the viewer.
Figure 6
Figure 7 shows a parent with a duplicate in the same case, and also a duplicate in a separate case. The parent
record, ID00016, has two duplicate records: ID00032 in CaseA02 and ID00019 in CaseA01.
286
Deduplication
Figure 7
Deleted Records
If a record is a parent or duplicate record, and it is deleted from the LAW case, a warning will appear in the Duplicate
Viewer in place of the typical entry. Figure 8 shows the resulting viewer after a parent's duplicate document is
deleted.
Figure 8
Retrieving the Case Deduplication Status

The Click here to retrieve the deduplication status of the case link located at the bottom of the Duplicate Viewer
can be used to ensure the case is fully deduplicated. If the number of deduplicated records in the case matches the
number of records in the case, then the status will be displayed as "Case is 100% deduplicated." If the number of
deduplicated records in the case is less than the number of documents in the case, the viewer will display a status
similar to what is shown in Figure 9.
287
Figure 9
288
Export Utility Overview
Export Utility Overview

LAW's Export Utility allows users to export one or a combination of the following items to the desired litigation support
software: native files, images, metadata/index field data, and full text. Because the supported export formats are quite
different from each other, LAW provides users with target application-specific settings to better suit the selected
format(s).
Many of the supported formats are strictly viewers and do not support index or OCR information. Consult the
documentation for the intended target applications before doing any coding or OCR to avoid wasting time performing
unnecessary steps in LAW. LAW supports all of the popular litigation support packages and several others. To launch
the Export Utility, select Tools > Export Utility from the main form or standalone grid, or click the button on the
main form, standalone, or embedded grid toolbar.
The LAW Export Utility also includes the ability to set up export profiles to save export settings as explained in the
Export Profiles section.
289
Image Format
The image format required is a result of the target application and its image viewer. Some applications use one multi-
page image file to represent a multi-page document while others use a series of single-page image files (logically
grouped) to represent a multi-page document. If images created via TIFF Conversion in LAW were stored in multi-
page format and a single-page export format was chosen, the images would need to be split upon exporting, which
can significantly slow the process. Therefore, conversion to single-page tiffs is recommended whenever possible.
Load File Extensions

The load file extensions indicate the extensions of the load files that are created for each of the supported formats.
With the exception of Doculex (which use a FoxPro database) and the Concordance DCB export, all of the load files
created are text files that conform to the specifications defined by the target application. In the case of Concordance
and JFS, the export actually produces two export files, one with index data and one with image information. The load
files can be found in the export path after the export is complete. The load files are named (with the appropriate
290
Exporting
extensions) according to the last folder in the export path (e.g., "Vol001.dat", "Vol001.dii", etc. for an export path of
"D:\Exports\Case1\Vol001"), as LAW assumes this is the volume label for the export.
Supported Formats
Below is a quick reference to all supported export formats, image file formats (single or multi-page images), load file
extensions, formats that support importing of index information, native file support, and support for (single- or multi-
page) OCR.
16-Bit Naming
Meta Data Full Text
Format Output Files Single / Multi Page Required (8.3
Support Support
Characters)
[VolName].dat
BlueTrace [VolName].opt Single / Multi Page PreDefined No Yes
ImportText.cpt
CaseLogistix [VolName].xml Single / Multi Page Yes No Yes
CaseMap [VolName].csv Single / Multi Page Yes Yes Yes
[VolName].dat No, unless using older

Concordance [VolName].opt Single / Multi Page Yes version than 2.0 of Yes
ImportText.cpt Opticon
[VolName].dcb
[VolName].ini
[VolName].key
Concordance Direct (DCB) [VolName].ndx Single / Multi Page Yes No Yes
[VolName].opt
[VolName].tex
ImportText.cpt
Delimited Text [VolName].csv Single / Multi Page Yes No Yes
Doculex Viewer 4.x Doculex3.dbf Single No Yes No
Doculex Viewer 5/6 Doculex5.dbf Single No No No
DocuMatrix 1.5 [VolName].xml Single / Multi Page Yes No Yes
dtSearch N/A Multi Yes No Yes
EDRM XML 1.0 [VolName].xml Single / Multi Page Yes No Yes
iCONECT [VolName].xml Single / Multi Page Yes No Yes
inData's TrialDirector [VolName].oll Single / Multi Page Yes No No
291
Inmagic's DB/TextWorks [VolName].add Single / Multi Page Yes No Yes (embedd
Introspect eCM [VolName].idx Multi Yes No Yes
IPRO IntelliVIEW [VolName].lfp Single / Multi Page Yes No Yes (embedd
[VolName].jfs
JFS Litigator's Notebook [VolName].log Single Yes Yes Yes
jfs.col
LaserFiche [VolName].lst Single Yes No No
OmniDox (Custom) [VolName].ID Single Yes No Yes
PDF Conversion Straight PDFs Single / Multi Page No No No
PDF Hidden Text Searchable PDFs Multi Yes (embedded) No Yes (embedd
Ringtail.mdb (Access
Ringtail CaseBook Single / Multi Page Yes No Yes (embedd
DB)
Sanction [VolName].oll Single Yes No Yes \ No (ex
ImageBase.add +
Storm Viewer Single / Multi Page Yes No Yes (externa
Supporter Tables
[VolName].dii
[VolName].txt
Summation Blaze (Metadata if exported Single / Multi Page Yes No Yes (externa
field count is 6 or
more)
TotalVzn [VolName].opt Single / Multi Page No No No
292
Exporting
Export Profiles
Export profiles are used to save settings used in a particular export such as index field selection and format-specific
settings, allowing users to re-open the profile and apply or review those settings at a later time. Profiles will be
created, saved, modified, and opened from the Export Utility and are saved as a *.pfl file in a user-specified location.
No profile is loaded by default when the Export Utility is launched in a new case. The profile can be created and
saved to a file at any time when working in the Export Utility; otherwise, the user will be prompted to save the settings
after clicking Finish to initialize the export.
Creating Profiles
To create a profile, first launch the Export Utility by clicking Tools > Export Utility from the main menu or standalone
grid, or click the button from the main or embedded grid toolbar. The Export Utility dialog will appear.
Click File from the menu bar and choose Save As.... The Save As dialog will appear. Choose a location and enter a
name for the profile. Users may choose to create an 'ExportProfiles' folder in a directory (i.e. LAW50 folder) or may
choose to keep the profiles with the associated LAW case. At any rate, the location and name of the profile is
determined by the user. Click Save to save and apply the profile. Once created, the profile name will appear in the
title bar of the Export Utility dialog as shown.
The profile can also be created after clicking Finish from the Options tab of the Export Utility. A prompt will appear
prior to the export process initializing, asking if the user wishes to save the current settings. If Yes is chosen, the user
can enter a file name for the profile and a location in which to save the file. If a profile is already applied as in the
above example, clicking Yes will force the settings to be saved to the currently active profile.
Opening Saved Profiles

Saved profiles can be applied to additional exports for any LAW case provided they match, or closely match, the
settings needed for a particular export. If the profile does not meet the requirements, it may be edited within the
Export Utility by simply opening the profile, changing the desired settings, and then saving the changes.
To open and apply an existing profile, click File > Open from within the Export Utility. The Open dialog will appear.
Browse to the desired *.pfl file and click Open. All settings saved to this profile will be applied to the current export
session. Note: When a profile is used and an export is executed, that same profile will be automatically selected
when the Export Utility is launched in that LAW case.
Profiles may also be opened and applied using the "recent profiles" menu. The last four profiles opened in a case will
be listed in the File menu within the Export Utility. Simply click the desired profile to apply it.
293
Formats/Documents Tab
The Formats/Documents tab will be used to specify the export type, the files to be included for exporting, the type of
files (e.g., native files), the target application and its configuration settings (if any), and image format.
File Types
Because LAW is both a scanning and an electronic discovery application, the Export Utility allows users to choose
which type of data should be included in the export.
The Selected Types drop-down contains three options:
294
Exporting
All Records - This option may be used when a LAW case contains both scanned (or imported) images and
native files, and the user wishes to include both types in the export. This option may also be used if the case is
all e-discovery or all scanned data.
Scanned Data - Use this option when exporting only scanned images or images imported using a feature
other than the ED Loader (such as Import Raw Images).
Electronic Discovery - This option will be used to export files that were imported as e-discovery only. This
may include native files and/or the tiff images for each ED record (if files were converted to tiff).
Note: Keep in mind, not all target applications support native file review. Currently, native file exports apply only to
Blue Trace, CaseLogistix, Concordance, Concordance Direct (DCB), Delimited Text, EDRM XML 1.0, iCONECT,
Introspect eCM, Ringtail, and Summation.
The next section is used to choose which document "states" to include in the export. Four options are available:
Include Images - Includes scanned images, images imported via Import Raw Images or Import Load File,
and images created during the Tiff Conversion batch process or single document tiffing.
Include Full Text - Includes text files for any documents that contain text. This text may have been
extracted during the pre-save or created during the OCR process. The type of text included in the export will
depend on the option selected in the Text Options dialog (see below).
Options - The Text Options dialog allows users to choose the type of text to take precedence when
exporting.
The options are: OCR Text, Extracted Text, and Printed Text. If OCR is chosen as Option 1, LAW will export
the OCR text for any documents that have associated OCR. If no OCR text is found, LAW will move to Option 2
295
and export either the Extracted Text or no text at all if set to 'None'. LAW will then move to Option 3 and export
Printed Text if it has been created from the native documents during the TIFF conversion process.
Allow UNICODE in text - When enabled, LAW will include any UNICODE characters in the exported
text if present. This feature should be used with caution as many export formats do not support
UNICODE.
Decode UTF-8 to ANSI - When enabled, LAW will convert the default UTF-8 extracted text files to
ANSI upon exporting.
Export as single page text - Single-page text files for each document will be exported if this option
is enabled.
Note: Only two formats, Summation and Sanction, support single-page text.
Omit text for tagged documents - This option can be used to omit the OCR, printed, or extracted
text from the export for certain records. This feature may be used to avoid potential problems caused
by extremely large text files associated with LAW records. A tag field must be created and records
tagged prior to launching the Export Utility. The tag field will appear in the drop-down list below this
option.
Tip: A run command is available via Tools > Run Command > Capture Text File Sizes that will
store the file size of the extracted text associated with a document in an index field. This provides
an easier method of locating large text files and tagging them for use with the "Omit text for
tagged documents" feature. Please note, this run command has not been fully tested and cannot
be supported in the event of a problem.
Include Native - Includes the native files imported during the e-discovery import process. Again, not all
export formats support native file review. If Include Native is the only option selected, only Blue Trace,
CaseLogistix, iCONECT, Concordance, Concordance Direct (DCB), Ringtail, and Summation will be displayed
in the Formats section.
Note: This option will be disabled if the Scanned Data export type is selected.
Include records without files - When enabled, LAW will include a record in the export load file or database
for all LAW records that do not have a native file associated with them. For example, if a duplicate file was
detected during an ED Loader import, and the action was set to log a record but exclude the native file, then the
record in LAW would not have a native file. If this export setting is disabled, this record would not be included in
the export output and a warning would be logged.
Documents
The Documents section will allow users to choose which documents to include in the export.
All Documents - Includes all documents in the case, depending on the selected Export Type. For example,
if this option is selected, and Electronic Discovery is chosen in the File Types section, LAW will only export
records imported as e-discovery; non-ED data will not be included in the export.
296
Exporting
Search Results - Includes all records currently displayed in the grid. This option will only be enabled if the
Export Utility is launched while a grid display is active or if it is launched directly from a grid.
Select Documents - Allows users to choose certain folders and/or ranges of documents within folders for
processing. Click Select to launch the Select Folders dialog and check the boxes next to any folders that need
to be included for export. To select a range of documents, click the folder containing the desired records and
click the Set Range button. Check the boxes next to the starting and ending documents. The Calculate total
documents option may be selected to include document counts (and possibly page counts - see next section)
in addition to the number of folders selected. Enabling this option could cause a delay when returning to the
main Export Utility screen in large cases.
Document and Page Counts

In cases with a large number of documents and/or pages, a delay may be experienced when launching the Batch
Process or Export Utility dialogs while LAW calculates the total number of pages to display. To avoid the potential
delay, the page count can be disabled by navigating to Tools > Options > Preferences tab and then deselecting the
Calculate total pages in batch/export dialogs setting prior to launching the Export Utility dialog. The number of
pages will no longer appear beside the number of documents.
Formats
This section is used to specify the target application(s) as well as the load file/image format. Note: Many applications
may be chosen but not all support the same options or image formats. Also, certain applications will have special
configuration settings available in the Export Utility.
To select a format, single-click the desired application title in the Available Formats list. Directly below this list, two
image format options exist: Single-Page and Multi-Page. Choose a format by clicking the appropriate radio button.
Note: The image format MUST be selected BEFORE moving the application format to the Selected Formats list.
To move the format to the Selected Formats list, simply double-click the application title or ensure the format is
highlighted and click the Select button. Once the format has been moved, the user can confirm the proper image
format was selected by highlighting the application title in Selected Formats and viewing the selected image format
directly below the Selected Formats list.
As mentioned, certain formats will have additional configuration settings specific to that application. To determine if a
format has additional configuration options, single-click the application title in the Selected Formats list. If the
Configure button becomes enabled, this indicates additional settings exist and can be viewed by clicking Configure.
The formats below support additional configuration settings:
CaseLogistix
CaseMap
Concordance
Concordance Direct (DCB)
Delimited Text
DocuMatrix 1.5
EDRM XML 1.0
iCONECT
inData's TrialDirector
Introspect eCM
IPRO IntelliVIEW
297
JFS Litigator's Notebook
PDF Conversion
Ringtail CaseBook
Sanction
Storm Viewer
298
Exporting
Format-Specific Settings
CaseMap
To view CaseMap configuration settings, move the format from the Available Formats list to the Selected Formats list
(Export Utility > Formats/Documents tab), highlight the application title and click Configure. The CaseMap Settings
dialog will appear.
Data Delimiters
Choose the desired delimiters to surround each field and/or field value in the load file. To specify a delimiter not in the
Field drop-down list, choose <other> and key the delimiter into the "Other" text box.
Path Notation
The path notation allows users to specify how image paths are written to the load files during the export process. With
Hard Path selected, the load file will display a full path to each output file, such as
C:\Exports\TestCase\Vol001\image.tif. The Relative Path setting uses a relative path to the images from the export
path instead of the entire path (minus the drive letter). If the UNC Path option is selected, and the export path is a
mapped network drive, the image paths are written using an UNC notation (\\computername\sharename\...).
Other
When enabled, the Include field names as first record setting will force LAW to place the names of any included
index fields in the first row of the load file.
299
CaseLogistix
To view CaseLogistix configuration settings, move the format from the Available Formats list to the Selected Formats
list (Export Utility > Formats/Documents tab), highlight the application title and click Configure. The CaseLogistix
Settings dialog will appear.
Path Notation
path instead of the entire path (minus the drive letter). If the UNC Path option is selected, and the export path is a
mapped network drive, the image paths are written using an UNC notation ( \\computername\sharename\ ...).
Other
When enabled, the Include document/OCR text as a field in load file setting includes the text for each document (if
available) as a field in the CaseLogistix XML file. The Field Name text box is used to specify the name of the field to
which the text will be exported.
Note: In LAW 5.2 and higher, any Unicode data included in exported fields is automatically included in CaseLogistix
load files.
300
Exporting
Concordance
To view Concordance configuration settings, move the format from the Available Formats list to the Selected Formats
list (Export Utility > Formats/Documents tab), highlight the application title and click Configure. The Concordance
Settings
Data Delimiters - These options allow users to specify which data delimiters to use in the Concordance .dat
file. The data delimiters used when exporting will also need to be used when importing the .dat file into
Concordance. The default values Concordance uses by default can be applied by clicking the Restore
Defaults button.
Path Notation - The path notation allows users to specify how image paths are written to the load files
during the export process. With Hard Path selected, the load file will display a full path to each output file,
such as C:\Exports\TestCase\Vol001\image.tif. The Relative Path setting uses a relative path to the images
from the export path instead of the entire path (minus the drive letter). If the UNC Path option is selected
and the export path is a mapped network drive, the image paths are written using an UNC notation
(\\computername\sharename\...).
Include field names as first record - Inserts the field names for each field as the first record in the .dat file.
This is useful when viewing the data manually or importing into other applications.
Include document/OCR text as a field in load file - The text for the selected documents will be included in
the .dat file if this option is enabled. This setting also overwrites the Include Full Text setting on the
Formats/Documents tab of the Export Utility. The Field Name is the name of the field in the .dat file which
will contain the text. If the selected field contains more than ~8MB of text, LAW will automatically create
sequential fields to adhere to Concordance's field size limitations.
301
Link to images and native files in their current location - Leaves any images and native files included in
the export in their location (LAW case directory). This feature greatly improves the speed of the export
because no files are being copied and LAW must only generate the load files. Paths in the load file will
reflect the current location of the files.
Create Opticon load file only - With this option selected, LAW will only create an Opticon load file (.OPT)
and not the .DAT file.
Allow Unicode data (UCS-2 format) - Allows Unicode field data to be included in the load file if any exists
in the records selected for export. Prior to exporting, please ensure the version of Concordance being used
will support the Unicode data.
Note: The "Allow Unicode data" setting only applies to Concordance database versions 10 and above.
302
Exporting
Concordance Direct (DCB)

To view Concordance Direct (DCB) configuration settings, move the format from the Available Formats list to the
Selected Formats list (Export Utility > Formats/Documents tab), highlight the application title and click Configure. The
Concordance Direct Settings dialog will appear.
Settings
Use specific database (*.dcb) override path - Allows users to append to the desired database.
Security - The Security feature applies login information when appending to existing Concordance DCB
databases. Click the button to enter a user name and password for the database.
303
If the version of Concordance installed on the current workstation does not support this feature, the Security
button will be grayed out.
Database path - This option is used in conjunction with the "Use specific database (*.dcb) override path"
option. Click Browse to locate a Concordance database; exported records will be appended to the selected
*.dcb file.
Path Notation - The path notation is used to specify how image paths are written to the Opticon load
file during the export process. With Hard Path selected, the load file will display a full path to each output
file, such as C:\Exports\TestCase\Vol001\image.tif. The Relative Path setting uses a relative path to the
images from the export path, instead of the entire path (minus the drive letter). If the UNC Path option is
selected, and the export path is a mapped network drive, the image paths are written using an UNC notation
( \\computername\sharename\ ...).
Note: Hard paths will always be used if the "Automatically load Opticon imagebase files" option is enabled.
 If Record Match is Found - The selected option will determine the action LAW will take if a
matching record is found in the Concordance database when utilizing the append feature. The
three options are:
Skip Record - Record will be omitted if it already exists.
Update Existing Record - Any new information will be applied to the existing record, if
one is located.
Append All Records - All records will be appended to existing database.

Field Indexing - Click this button to open the Concordance Field Settings dialog box, listing the fields in the
current LAW case. The fields can be selected as "Key" or "Indexed" fields before exporting the database to
Concordance. When the Concordance database is opened, the selected key and indexed fields are listed in
File > Modify.
Note: These field settings only apply to Concordance 8 databases (or higher). To modify fields for earlier
database versions, edit the "E-Discovery.dcb" database template located in the Template folder in the LAW
installation directory.
304
Exporting
Concatenate DCB's across separate partitions - Select this option to concatenate the databases into one
database and then export it into partitions. For example, a partition size of 650 MB creates partitions of the
concatenated database that can be copied to CDs. All of the database partitions are treated as one
database. The partition size is set in the Options tab of the Export Utility.
Automatically load Opticon imagebase files - When enabled, LAW will automatically load any exported
images into Opticon, eliminating the need for the user to do so once the Concordance database is created.
Include document/OCR text as a field in database file - When enabled, this feature includes exported
text to a field in the database. Enter the desired Field name below this option in the text box provided.
Link to images and native files in their current location - Leaves any images and/or native files included
in the export in their current location (LAW case directory). This feature greatly improves the speed of the
export because no files are being copied and LAW must only generate the load files. Paths in the load file
will reflect the current location of the files.
Truncate text values that exceed their field size - If this setting is enabled, records with text values that
exceed their field size in the target DCB will still be added to the database. The offending text values will be
truncated and a warning will be logged. When disabled, these records will not be added to the DCB and
errors will be logged. The warning and error messages will include the field name, field size, and the
offending data size.
305
Delimited Text
To view Delimited Text configuration settings, move the format from the Available Formats list to the Selected
Formats list (Export Utility > Formats/Documents tab), highlight the application title and click Configure. The
Delimited Text Settings dialog will appear.
Data Delimiters
Choose the desired delimiters to surround each field and/or field value in the delimited text file. The Delimited Text
export generates a *.csv file named for the last folder in the export path (i.e., Vol001.csv).
Path Notation
path instead of the entire path (minus the drive letter). If the UNC Path option is selected and the export path is a
mapped network drive, the image paths are written using an UNC notation ( \\computername\sharename\ ...).
Allow Unicode data (UCS-2 format)

Select this option to view any Unicode data existing in the selected export fields in the delimited text (CSV) file
created during export.
Note: Excel will not parse a Unicode file correctly by default unless a tab [009] is used for the field delimiter.
306
Exporting
DocuMatrix 1.5
To view DocuMatrix configuration settings, move the format from the Available Formats list to the Selected Formats
list (Export Utility > Formats/Documents tab), highlight the application title and click Configure. The DocuMatrix
Case Name and Database Name - These are both optional settings and are not required to create the export from
LAW. These values may be entered if requested.
Include attachments by parent - Forces LAW to include attachments with any selected parent.
Include page offset data with OCR - This setting uses the OCR information created from the ExperVision or ABBYY
OCR engine to create information in the load file for producing hit highlighting in DocuMatrix. Without this setting
enabled, OCR text will be included in the load file, but the location of each word will not be included. ("Include Full
Text" must also be checked on the Formats/Documents tab of the Export Utility.)
Create XML for fixing existing documents - Use this setting to create an XML file specifically used for updating
existing records in an existing DocuMatrix case.
Renumber documents sequentially - When enabled, LAW will renumber the documents in the .xml load file,
starting with the specified value in the Starting # field.
Note: DocuMatrix requires attachment (child) documents to have a parent in the load file. If an attachment is
included to be exported but the parent is not (using the manual document range selection), this may cause
problems when loading the file into DocuMatrix.
307
EDRM XML 1.0

To view EDRM XML 1.0 configuration settings, move the format from the Available Formats list to the Selected
Formats list (Export Utility > Formats/Documents tab), highlight the application title and click Configure. The EDRM
Batch Name
The Batch Name setting is used to associate a specific name with the exported set of files and metadata. The value
entered in the text box will be stored in the XML load file in the Batch Name tag.
Path Notation
mapped network drive, the image paths are written using a UNC notation ( \\computername\sharename\ ...).
When enabled, the Include document/OCR text as content in load file setting includes the text for each document
(if available) within the EDRM XML file. Specifically, the text will appear between the starting and ending
InlineContent tags.
308
Exporting
iCONECT
To view iCONECT configuration settings, move the format from the Available Formats list to the Selected Formats list
(Export Utility > Formats/Documents tab), highlight the application title and click Configure. The iCONECT Settings
dialog will appear.
Path Notation
mapped network drive, the image paths are written using a UNC notation (\\computername\sharename\ ...).
Other
The Date Format feature is used to choose the date format for any exported date fields. Choose the desired format
from the drop-down list.
When enabled, the Include document/OCR text as a field in load file setting includes the text for each document (if
available) as a field in the CaseLogistix XML file. The Field Name text box is used to specify the name of the field to
which the text will be exported.
309
Introspect eCM
To view Introspect eCM configuration settings, move the format from the Available Formats list to the Selected
Formats list (Export Utility > Formats/Documents tab), highlight the application title and click Configure. The
Introspect Settings dialog will appear.
General
In the General section, enter values for the Batch Name, Index ID, and Folder ID text boxes. If the Batch Name is left
blank, the volume name of the exported load file will be used by default. The Index ID and Folder ID values will
appear as repeating values in the load file. Each of these three values is usually provided if this format has been
requested.
Include all Bates numbers - Creates a text file called "<image>_uid.txt" for each multi-page document and contains
a list of PageIDs contained in the multi-page document.
Link to images and files in current location - When enabled, the export process will generate the load file(s) and
link them to the images and/or native files in their current location; the files are not copied.
Note: When using this setting, images MUST be in multi-page format in the LAW case in order for Introspect to
view all pages of the images. Also, the IDX load file will always be written to the image path of the case so relative
paths to the documents can be used (required by Introspect) and named according to the batch name as configured
in the Introspect settings. A shortcut to the load file will be created in the export path referencing the load file in the
image directory of the case.
Use IDX Version 5 format - Forces LAW to configure the load file to match the specifications for Introspect 5.
<Field IDs..> - Click this button to display the field configuration dialog shown below:
310
Exporting
The Introspect Field Information dialog may be used to define specific Field ID values for any of the fields. The fields
shown in this list are all of the index fields which exist in the current LAW case. These fields will exist in the Header
section of the .idx load file.
311
IPRO IntelliVIEW
To view IPRO configuration settings, move the format from the Available Formats list to the Selected Formats list
(Export Utility > Formats/Documents tab), highlight the application title and click Configure. The IPRO Settings dialog
will appear.
Include index fields in load file - Use this setting to include index information in the .lfp file. Click the Edit button to
display the IPRO Field Information dialog.
This dialog allows the selection of up to 10 Information (IO) fields and as many Tag/Issue (IS) fields as the user
needs. When specifying the IO tags, an index value (1-10) must be assigned to the selected field and will match the
312
Exporting
corresponding field in IPRO. No two selected IO fields may have the same index value. Selection of index fields in
this window is independent of the fields selected under the Fields tab in the Export Utility. Once the desired selections
have been made, click OK to save the changes and return to the IPRO Settings dialog.
Include OCR Word Information - OCR produced using the ExperVision or ABBYY OCR engine may be included in
the IPRO load file using the full text (FT) tag, which allows full text searching in IPRO. To separate the OCR text from
the image information, select the option to Write to separate LFP file. This option will generate two IPRO files
displayed as [Volume].lfp and [Volume](ocr).lfp.
Number pages (w/IPRO annotations) - This feature allows LAW to create special tags in the exported LFP file that
apply the current PageID of the document as an "IPRO Annotation." This allows IPRO users to view/hide the PageID
annotation just as if the annotation were created in IPRO itself. The Alignment setting is used to determine the
horizontal location of the annotation: Left, Centered, or Right. The Vertical Position setting is for placing the
annotation relative to the height of the document. Selecting 0% will create an annotation at the top of the page and
selecting 100% will create the annotation at the bottom of the page.
Note: This annotation is applied directly on top of the existing image; therefore, it could potentially cover existing
image data. The IPRO annotation does not modify the image itself.
Use new folder flags (DocBreak = F) - Use this setting to include an (F) flag in the IPRO .lfp file as the document
break at the beginning of each new folder. The default value for this feature uses the document (D) flag.
Use volume path notation - If this option is checked, a volume path notation will be used; otherwise, a full path (with
drive letter) will be used and no volume will be specified.
313
JFS Litigator's Notebook

To view JFS configuration settings, move the format from the Available Formats list to the Selected Formats list
(Export Utility > Formats/Documents tab), highlight the application title and click Configure. The JFS Litigator's
Notebook Settings dialog will appear.
The JFS settings allow users to map LAW fields to default JFS fields. To link a field, choose a field in the Available
Fields list and then choose a field in the JFS Fields list. Click the Link Fields button to add to the Mapped Fields list.
The Use alternate format setting allows LAW to list only the exported field names (per line) with the corresponding
field value.
314
Exporting
PDF Conversion
To view PDF Conversion configuration settings, move the format from the Available Formats list to the Selected
Formats list (Export Utility > Formats/Documents tab), highlight the application title and click Configure. The PDF
Create bookmarks for grouped documents - Use this setting in conjunction with the Combine
Parents/Attachments option, found in the Export Utility under the Options tab, to create bookmarks in exported PDF
files. If a document is not a parent or contains no attachments, no bookmarks will be created in the PDF file for that
document.
Bookmark Caption - The Parent and Attachments drop-down lists will contain the index fields that exist in the
current case. The fields will be used as the bookmark titles in the exported PDF.
Populate PDF metadata - This setting may be used to populate the metadata of a PDF file with index field values
stored in the LAW case. This feature must be used in conjunction with the "Combine Parents/Attachments" setting
located in the Options tab of the Export Utility.
315
Ringtail Casebook
To view Ringtail configuration settings, move the format from the Available Formats list to the Selected Formats list
(Export Utility > Formats/Documents tab), highlight the application title and click Configure. The Ringtail Settings
dialog will appear.
Allow long folder names (over 20 chars) - This option allows LAW to ignore Ringtail's recommended folder name
length limit of 20 characters.
Caution: This setting is not recommended as Ringtail does not officially support long folder names. This option is
available due to special LAW user requests.
Include document/OCR text as a field in load file - Use this option to place the document text into a memo field
inside the Ringtail load file. This was the default method for handling Ringtail OCR with LAW versions 4.02.41 and
below. Ringtail does not directly support this method and it should be used with caution.
Insert special page markers in OCR text - This option inserts a special page marker onto the OCR text of each
page in the following format: "###{Page}|||Page {PageID}^^^". This tag is used by Ringtail for linking the OCR text to
the actual images. The Replace existing page markers option will remove any existing page markers currently on
the OCR and replace them with the new value. This feature is useful if the OCR in LAW already contains these
markers but document boundaries have since changed. Instead of re-OCRing the documents, this feature replaces
the old tag with the new.
Include reference to native file in Pages table - When enabled, and native files are included for export, LAW will
write a record for each native file to the Pages table in the Ringtail load file (export.mdb). Records referenced in the
pages table will be available for viewing in the Image frame in Ringtail. If images and native files are included for
export, and the native records are not referenced in the Pages table, Ringtail will locate the native files and allow
viewing of them in the Content frame, provided the native files are named the same as the associated image and are
located in the same folder.
316
Exporting
Ringtail Format Notes

The requirements for the Ringtail format should be followed closely to avoid possible problems importing this load file
into Ringtail.
Folder character length not to exceed 20 characters - If LAW's folder name length exceeds the 20
character maximum length, LAW will automatically truncate the folder path to 20 characters (unless the "Allow
long folder names" option is selected).
Folder names may not contain spaces - Spaces in folder names will automatically be converted to
underscores ("_") during the export process.
Exported text filenames - The filenames for the exported text files are unlike other formats; Ringtail
requires a filename format named the same as the image tag with a .txt extension.
Supports Single-Page or Multi-Page Tiffs (single-page most common) - Ringtail supports either single-
page or multi-page tiffs; however, the most commonly used image format is single-page tiff.
BegDoc#, EndDoc#, and PgCount - These three fields (if included in the Fields tab and selected for
export) will be automatically placed in the 'Export_Extras' table of the Ringtail load file.
317
Storm Viewer
Storm Viewer is a freely distributable viewer available to the public. The viewer runs as a front-end to the Storm
imagebase. The Storm imagebase can be built and distributed freely by users of LAW and Storm-X. Storm Versions
1.2 and above now offer the DB-Builder License which allows users to import industry standard loads files and raw
image files to build their own Storm ImageBases.
Storm utilizes the powerful Advantage Local Server for accessing image data and metadata. The local server has a
5-user concurrent connection limit, so no more than 5 users may have a single database open at one time.
For users who wish to scale Storm for use as a document retrieval tool, and have more clients, the Advantage
Database Server is a lightweight and powerful RDBMS solution that will add stability, speed, and more connections to
existing imagebases.
Note: Storm Viewer exports will also work for the Stormi software, a free CD-runtime viewer.
318
Exporting
Summation
To view Summation configuration settings, move the format from the Available Formats list to the Selected Formats
list (Export Utility > Formats/Documents tab), highlight the application title and click Configure. The Summation
Settings
Allow advanced (iBlaze) dii features - Enables features not compatible with versions 5.21 and below of
Summation.
Write all fields to dii file - Allows the writing of seven or more index fields to be written to the dii file. The
default export method is to write the index fields to a .txt file if the number of index fields is greater
than seven.
Include document/OCR text directly in dii file - Allows the text for the exported documents to be included
in the dii load file. If this setting is enabled, it will overwrite the 'Include Full Text' option on the Fields tab of
the Export Utility for the Summation format.
Warning: This feature appears to have bugs in Summation. Form feed characters to delimit text pages are not
supported and errors about unsupported operations may occur, although all the data does appear to get imported.
Include PST tokens directly in dii file - Forces LAW to include an extra 'tag' in the edii file. The @PSTFile
token allows Summation users to identify the source PST file where the e-mails originated. This can be
helpful if there are many individual PST files being processed for a job. If this option is not checked, the
319
@PSTFile token will be omitted from the edii file. This setting is disabled in LAW cases that are have not
been enabled for electronic discovery.
Always write index fields to separate file - Forces LAW to place all index field information into a delimited
text file regardless of the number of index fields selected for export.
Include field names as first record of delimited text file - Places the index field names in the first line of
the delimited text file. This is useful for determining the field order of the data in the load file or for importing
into other applications.
Data Delimiters - The data delimiters for the delimited text file may be defined in this section. The default
values for this feature can be reset by clicking the Restore Defaults button.
Dii Path Notation - This setting is used to specify the type of volume notation to use in the dii file. The CD
Volume (@V Vol:) option will return a tag in the dii similar to: "@D @VVol001:\Vol001\001\" where "Vol001"
is the volume name. Hard Path creates a tag similar to: "@D C:\Exports\Vol001\001\". The Image
Directory (@I) option will return a tag in the dii similar to: "@D @I\Vol001\001\" where "Vol001" is the
volume name. The two options (@V and @I) are the most commonly used with @I being the recommended
(most versatile) method. Most users of Summation have a preferred way of importing the dii files so it is
important to check on the preferred method.
eDii Tokens - This feature allows users to choose which tokens are placed in the Summation load file. All
available tokens are selected by default.
Note: An INI setting is available to modify the @MEDIA value used for e-mail attachments that are e-mail files (i.e.
MSG attached to an MSG). By default, LAW will populate the @MEDIA token for these attachments as
"Attachment" per the Summation documentation. However, the value can be changed to "eMail" for e-mails
attached to e-mails by adding the following setting in the Law50.ini file in the application path (same folder as
Law50.exe):
[Summation]
EmailAttachEmailMedia=eMail
If the [Summation] section already exists, add the key below it; otherwise, add the entire setting as shown.
To switch back to the default of "Attachment", either remove (or comment out) the setting above or replace the
eMail value with Attachment.
320
Exporting
TrialDirector and Sanction

The TrialDirector and Sanction formats utilize the same configuration settings. To view these settings, move the
format(s) from the Available Formats list to the Selected Formats list (Export Utility > Formats/Documents tab),
highlight the application title, then click Configure. The TrialDirector Settings or Sanction Settings dialog will appear,
depending on the selected format.
Document ID - Uniquely identifies each document within the collection. Users may choose BegDoc# or any other
index field in the LAW case, such as DocID or Exhibit Number (for example).
Object ID - References each page within the document. This field may either be Page ID (used when BegDoc# is
selected as the Document ID field) or Auto-Generate, which assigns a .001 extension (and so on) after the Document
ID to each page within the document (i.e., EX001.001, EX001.002, EX001.003). The Auto-Generate feature is most
commonly used when a field other than BegDoc# is selected as the Document ID.
Description (Optional) - Optional setting allowing users to populate the Description field in TrialDirector or Sanction
with values from a user-defined field in the LAW database.
321
Fields Tab
The Fields tab in the Export Utility will be used to select the index fields to be included in the load files and to select
the Image Tag, or document identifier, which will be used to link the index field data to the associated image or native
document.
Selected Format
The Selected Format drop-down will contain up to five items, depending on the formats selected in the
Formats/Documents tab: Default (always present in list), Summation, Concordance, Concordance Direct (DCB), and
Ringtail.
In certain situations, users may need to include certain fields in a Summation load file and a different set of fields in a
Concordance load file, for example, but would like to perform both exports at one time. LAW allows customization
of the field selection and field names for each of the four aforementioned formats while still maintaining a "default"
field selection for any other selected formats. This option eliminates creation of multiple exports solely to change
index field information for one or more of the formats.
For example, a user needs to export to Summation, Concordance, and Storm Viewer, and the specifications call for
different index fields to be included in each type of load file. The user would first choose the Storm Viewer fields with
<Default> as the Selected Format in the Fields tab. Next, the user would select Summation from the Selected
Formats list, check the "Use format specific fields over default selections" option, and then choose the desired fields
for the Summation load file. The final step would be to choose Concordance from the Selected Formats drop-down,
check the "Use format specific..." option, and then choose the desired fields for the Concordance load file. In another
example, a user must export to Summation and Storm Viewer and needs to include the same fields for both formats.
In this scenario, the user would simply need to choose <Default> in the Selected Format drop-down and then select
322
Exporting
the desired fields. These fields would then be included in both the Storm Viewer database and the Summation load
file.
The "Use format specific fields over default selections" option enables the Available and Selected Fields lists when a
format other than <Default> is chosen, allowing users to choose fields to be included in that format's load file.
Selecting Fields
The Available Fields area displays a list of both user-defined and system fields that are available for export. To
include a field in the export, highlight the index field in the Available Fields list and then click Select or simply double-
click the field name. The field will then be moved to the Selected Fields list. To remove a field, double-click the
desired field from the Selected Fields list or select it first and press the Remove button. Fields may also be selected
or deselected by clicking the Select All or Remove All buttons.
The Selected Fields list is divided into two columns:
Field Name - Displays the name of the selected index field.

Export As - Allows users to rename the field upon export. This does not rename the field in the LAW case
itself, just in the load file. This is useful for applications that require fields to be named a certain way, such as
Summation. Note: Field names displayed in red once moved to the Selected Fields list indicates the field name
is not compatible with one or more of the selected export formats (i.e., field name is too long or contains
unsupported characters). The field will need to be renamed in the 'Export As' column prior to export. The field
name will no longer appear in red once the name has been properly changed.
The Promote and Demote buttons may be used to change the order of the fields in the Selected Fields list and
ultimately, in the load file. The Promote button will move the selected field further up in the list, while the Demote
button will move the selected field down the list.
Image Tag Field

The Image Tag, or document identifier, field is used to link images or native documents to the matching index field
data. The BegDoc# and DocID fields are commonly used for this purpose, but other user-defined fields may be used
provided they contain a unique value and do not contain blank values for any record.
323
Options Tab
The Options tab contains settings for the output path (for images, native, text, and load files), folder and file naming
schemes, export logging, and various other output settings, such as file format.
Output Path
This section contains settings related to the location in which the files will be exported.
Export Path - This value will be the location to which the exported files will be saved. These files may
include one or a combination of images, native files, full text, and load files, depending on the selected options.
Partition Size - This setting is used to determine how much data is written to each volume. The last folder
listed in the output path is considered to be the volume name. For example, if the export path listed is
C:\Exports\EDD_001\Vol001, then the first volume will be Vol001. When the partition size has been reached, a
Vol002 folder will be created, etc. The default of 650 MB should be used if planning on burning the exported
324
Exporting
data to CDs but may be increased or decreased as needed (0=unlimited, all records will be written to one
volume).
Prompt to continue export when volume is full - When this option is enabled, a prompt will appear on the
screen each time a volume becomes full and a new volume must be created. The user must click Yes each
time in order for LAW to create the new volume and continue with the export.
File Naming Scheme

The file naming grid is used to specify the type of file name to be used for images, native files, and full text. The items
below will briefly describe each column in the grid and its purpose:
File Type - Lists each file type included in the export as well as a Default option, which will apply to all types
unless the Override option is used. Only file types that are selected on the Formats/Documents tab will be
displayed; the Default option will always be displayed and represents all three file types. Having each type
listed separately allows users to apply different options to each (native, images, full text) if desired.
Override - Used to override the Default settings for the desired file type. For example, if BegDoc# is needed
as the filename for images and the original filename is needed for native files, simply check the Override option
in the Native row and choose <Original Filename> in the File Naming column, leaving BegDoc# as the Default.
File Naming - Used to specify a file naming scheme for the exported files. User-defined and system fields
will be listed in the drop-down for use as the file naming convention, including DocID and BegDoc#.
Exts - This option will ensure the file extension is included in the exported filename. This will be useful for
single-page imports when a document-level file naming scheme is used (otherwise resulting in .001, .002, etc.
extensions).
Starting Num - This option will only be available when the 'Auto Number' file naming scheme is selected.
Enter a starting number for the exported files; the value will increment by one for each exported record.
Reset Num - This option will only be available when the 'Auto Number' file naming scheme is selected.
Enabling this option will force the auto-numbering to restart to the specified starting number for each new
folder.
The Create control list file for extracted full text option, when enabled, will provide users with a control list (*.lst
file) that consists of a unique document identifier for each record with full text as well as a path to the text file.
This option is commonly used to import text into a Summation case with existing records but may be used for other
purposes if needed. The .lst file will be created in the currently specified Export Path, also found in the Options tab.
Folder Naming Scheme

The folder naming grid is used to specify the folder structure to be used for the exported images, native files, and full
text.
325
File Type - Lists each type of file (images, native, text) included in the export as well as a '<Default>' option,
which will apply to all types unless the Override option is used.
Override - Used to override the Default settings for the desired file type. For example, if <Default> is set to
Mirror Original, but the job specifications call for Incremental folders for native files only (and mirrored for
images and text), the user could select 'Override' beside the Native file type and then choose Incremental in the
Folder Naming column.
Root Folder - If a root folder value is specified here, the file type(s) (images, native, and/or full text) will be
placed in the mirrored or incremental folders, following this folder structure: <Export Path>\<Root Folder>. For
example, if a ”r;Text” root folder is specified for the Full Text file type, and the specified export path is
C:\Exports\EDD_001\vol001, then the full text will be placed in C:\Exports\EDD_001\vol001\Text. The Folder
Naming scheme (see next option) will be applied following the Root Folder.
Folder Naming - Three options exist for folder naming: Custom, Mirror Original, and Incremental. One
option may be applied to all by selecting the desired option as the <Default>. Or, use the Override setting and
choose different options for each.
o Custom - Uses 1-3 of the specified index fields to create a folder structure when exporting (see
Files/Folder option below).
o Mirror Original - Mirrors the current structure as shown in the folder tree in LAW’s main interface.
o Incremental - Places the specified number of files in a "001" folder, creates a "002" folder, etc.
(see Files/Folder option below).
Files/Folder - This option only applies to the Incremental and Custom folder naming schemes. If
Incremental was chosen, enter the desired number of files to be placed in each folder or use the default of 250.
If Custom was chosen, use this field to launch the Custom Folder Structure dialog and choose the field or fields
containing the folder structure.
Note: If a folder or file name length exceeds 250 characters for any records, the export path for those records will
be changed to <Export Path>\$Invalid_Paths.
Output Settings
The Output Settings section contains options related to output image files, annotations, and other miscellaneous
settings.
326
Exporting
Output Format - The Output Format setting allows users to convert images to an alternate format during the
export process. Output format settings are: Default, JPEG, PCX, PDF, PDF (Image Only), PNG, TIFF, and
TIFF (Binary). The JPEG, PCX, and PNG formats only support single-page image files and should NOT be
used with exports that produce multi-page images. The PDF setting can be used to convert images to PDF
and may be used with single- or multi-page image formats. This setting has the same effect as choosing the
'PDF Conversion' export format. The PDF Conversion format provides a means to export images as PDF
with no load files, whereas the PDF output format setting produces PDF images with all specified load files.
Choosing PDF (Image Only) forces LAW to create an image-only type PDF file. The TIFF (Binary) format
forces the export of black and white tiff images.
Note: If exporting multi-page color or grayscale tiff images to a single page format with the Output Format set to
Default, and the “Use Pegasus Image Library” is disabled, LAW will automatically export these files as JPEG
images. This is done for better compatibility with older image viewers that may not support TIFF w/JPEG
compression and to minimize the file sizes of the color images. B&W TIFF images will not be affected by this
process.
Output Scale - The Output Scale setting allows users to reduce the size (AND quality) of the images during
the export process. This setting is typically used to create a set of images to be viewed over the Internet or
an intranet where bandwidth is limited. This feature may be used to create a second set of images to be
viewed as thumbnails for browsing and allow the entire original image to be loaded upon request from a
separate location. Output Scale is not available for use if the "Use Pegasus Image Library" setting is
enabled.
Image Drive - The Image Drive setting allows users to specify an alternate drive letter for hard image paths
written to load files. If using hard paths for images (not recommended, but necessary with some formats),
this setting will replace the drive letter (with the designated letter) written to the load files, so they can be
imported without modification from another system. The <Default> setting uses the drive letter of the export
path. This setting should only be used if importing the data from another system and the drive letter from
which it will be read is known.
Merge Annotations - Merging annotations will "burn" all annotations onto the exported images. See
Annotations for more information on merging.
Retain Color - This setting allows color annotations to be preserved when merging annotations. It
is ONLY applied when an output format of TIFF or PDF is selected for a multi-page export. The
Retain Color setting for annotations currently only exists in the Export Utility.
Note: This requires changing the color format of the page and may significantly increase the size of the
images. Also, if using the PDF setting users should first ensure that the target application supports PDF images.
327
Combine parents/attachments - This feature merges attached documents to their respective parents
during the export process, creating a single document.
Use Pegasus Image Library - When enabled, LAW uses the Pegasus Image Library to manipulate images
during export. When this option is not selected, LAW uses the Pixel Image Library. However, common
"assertion failure" errors may occur when using the Pixel Image Library.
JPEG subsampling - Enabled only when the Pegasus Image Library is selected, JPEG
subsampling is used to adjust the color quality of a JPEG-compressed color image exported out of
LAW. Subsampling is used to calculate the color values of pixels that have been removed from the
image to reduce the size of the file. By averaging the known colors of nearby pixels, the missing
pixels can be determined. There are four possible selections for this setting ranked by displayed
image quality starting with the highest: 1:1:1, 2:1:1 (horizontal), 2:1:1 (vertical), and 4:1:1.
The default subsampling value of 4:1:1 is sufficient in most situations because it results in a good
quality image with the smallest file size out of the four possible settings. If the highest quality
display image is desired, the 1:1:1 subsampling option should be used instead. It will produce a
very high quality JPEG-compressed image because all of the color information for each pixel is
stored in the image file; however, the existence of this data results in a larger file size. The 2:1:1
(vertical) and 2:1:1 (horizontal) settings will produce a medium image quality between 4:1:1 and
1:1:1. These two options differ by the direction in which they average nearby pixels in the image.
Depending on the content of the image, the difference in image quality between the four possible
subsampling formats may not be noticeable. Some users of Summation iBlaze have reported a
noticeable improvement in displayed image quality when using the 1:1:1 subsampling format.
Note: Summation iBlaze defines these subsampling options differently than LAW.
LAW's Value Summation's Value

1:1:1 4:4:4
2:1:1 (horz) 4:2:2
4:1:1 4:1:1
2:1:1 (vert) 4:4:4
Export Status
This feature allows users to track whether or not a file has been exported.
A user-defined field must be selected to store the export status from the drop-down. Exported files will receive a value
of Y; records that did not export will receive a value of N. If an index field was created for this purpose, enable this
setting and choose the field from the list. If the "Reset export status" option is enabled, LAW will update the export
status for all documents in the case (regardless of the documents selected for export).
328
Exporting
Advanced Tab
The Advanced tab contains settings to control the blank value and duplicate checking for the selected image tag and
file naming fields. All of these settings are enabled by default (and always have been in previous versions of LAW).
Please use caution if disabling these settings as it could result in files being overwritten in the export path or problems
with loading into the target application. If these checks are not needed, a speed increase in export initialization is a
potential benefit of disabling the settings in larger cases.
Perform Blank Value Checks

These options determine whether LAW performs a check for blank values prior to exporting.
On file naming scheme - When enabled, LAW will check the selected field(s) used as the file naming
scheme (Options tab) for blank values and notify the user if any are found.
On image tag(s) - When enabled, LAW will check the selected image tag field (Fields tab) for blank values
and notify the user if any are found.
Perform Duplicate Checks

These options determine whether LAW performs a check for duplicate values prior to exporting.
On file naming scheme - When enabled, LAW will check the selected field(s) used as the file naming
scheme (Options tab) for duplicate values and notify the user if any are found.
On image tag(s) - When enabled, LAW will check the selected image tag field (Fields tab) for duplicate
values and notify the user if any are found.
329
Creating CD Volumes
LAW can export a case into volumes during the export process. The Options tab in the Export Utility contains an
Output Path section. Inside this section are options to determine the export path and to set the partition size of the
volumes created. If creating standard CD’s, using the default value of 650MB is recommended. Most CD’s today can
hold 700MB, but LAW needs some extra room for "buffer" space. Since LAW must prevent documents from spanning
across CD’s, this extra space is used for fitting the last document on the CD. The resulting volume size could result
anywhere from ~630MB to ~670MB depending on the documents in the case.
The last folder of the export path is used as the volume label for the export, so it needs to be named accordingly. For
example, an export path of "D:\Exports\Cases\John Doe\Vol001" will use "Vol001" as the volume label. All load files
created (with the exception of Doculex) are named after the volume label (e.g., Vol001.dii, Vol001.dat, Vol001.oll,
etc.) and all load files that reference a volume label will use this as the CD volume name. This is critical when
performing exports that read image information from a CD with a reference to the CD via the volume name. If the
volume of the CD is not specified as the last folder name, those applications will not be able to find the images
located on the CD.
Once the export has been created, depending on the size of the case, multiple volume folders may have been
created. For example, this sample case created three volumes:
Next, begin burning the volume folders onto the CD. It is VERY important this step is followed exactly or the load files
may not load properly into the destination application. Open the desired CD burning software and create the CD so
that the entire Vol001 folder is on the root of the CD and name the CD "Vol001". Repeat this step for each volume.
The load files should appear inside the Vol001 folder on the final CD, along with the images/native/text files for the
case.
330
Administration
Administration
Case Summary
The Case Summary function allows users to obtain a quick report on the size of a case and the status of the
OCR. The summary reports the number of documents, the total number of pages, the number of pages flagged for
OCR, and the number of pages completed. (See Flagging Documents/Pages for OCR section for details.) To
generate the case summary, select File > Administration > Case Summary from the main form. LAW will prompt
the user to enter a date range for narrowing summary information (optional).
If opting to do so, users can specify a date range and only documents that were created during that date range will be
included.
The case summary is a quick and easy-to-use report for general billing and progress reports. If more detailed
information is needed such as number of fields coded or a summary on a specific set of documents (that can be
identified by a query), the Summary function in the standalone grid display (Tools > Summary) may be used. For
electronic discovery reports based on data loaded via ED Loader, click Tools > ED Reports in the standalone grid.
331
Note: This summary can be incorrect if invalid records or page counts exist in the database, both of which can be
detected and/or corrected with the Scan for Errors functions.
332
Administration
Compacting the Database

Compacting databases is an essential part of database maintenance. Compacting removes unused space and
rebuilds indexes which can decrease the size of the database significantly and increase performance. This can also
help prevent corrupted databases that occur as the result of failed database operations or network
problems frequently encountered with very large databases. Database "bloating" occurs naturally as information is
added and removed. The space used by records is not reclaimed when records are deleted, causing the size of the
database to grow over time. This unused space is removed during the compact operation, reducing the size of the
database. The size of the database before and after the compact operation will be reported, so users can see how
much spaced was recovered (Access only).
Compacting should be done on a weekly basis at a minimum. However, if multiple users are performing extensive
coding and scanning in a case, consider compacting on a daily basis. To compact the current database, select File >
Administration > Compact Database.
Note: The Compact Database feature is not supported for SQL/SQL Express cases.
333
Log Viewer
Reviewing Errors
When certain processes in LAW have completed such as an export or batch process and errors have occurred, LAW
will generate an error log and prompt the user to view the contents. If Yes is selected (to view errors), the error log
will be displayed in the Log Viewer dialog.
If the user chooses not to view the errors and selects No, the error logs may be viewed at a later time using the Log
Viewer. This viewer may be launched by clicking Tools > Log Viewer from the main form. The Open Error Log dialog
will appear.
This dialog will contain seven tabs: All Logs, Export Logs, Batch Logs, Reorg Logs, Scan Logs, Deduplication Logs,
and Page Count Extraction Logs. The All Logs tab will contain all error logs associated with the current case. To
launch the Log Viewer, select a log from the list and click Open. The Log Viewer dialog will appear displaying the
filename of the error log in the title bar. Error logs for most processes are stored in <case root>\$Logs in *.csv format.
334
Administration
Sort columns (ascending or descending) by clicking on a column header. The columns can also be moved within the
Log Viewer by dragging, and dropping the column in the desired location.
Records shown in the Log Viewer can be tagged for future review, processing, etc. A tag field must be created prior
to launching the Log Viewer in order for the field to appear in the Tag Field drop-down list. (See the Creating Tag
Fields topic to learn how to create tag fields.) Once the tag field has been created and is selected from the Tag Field
list in the Log Viewer, determine which records need to be tagged. To tag all the records currently listed in the Log
Viewer, click the Tag All Records button. To tag only certain records, first use the Ctrl or Shift keys and left mouse
button to 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 Index display. Tag values cannot be toggled using this feature.
To view additional error logs once the Log Viewer has been launched (if any exist), click the Open Log button and
choose a different log from the Open Error Log dialog.
To save the contents of the Log Viewer to a new *.csv file, click the Save As button, browse to the desired location,
enter a file name, and then click Save.
The Log Viewer may be synchronized with the main form in LAW, allowing users to view the documents that received
errors when reviewing the error details. Click the Synchronize button to synchronize with the document list.
335
Reorganize Documents
The Reorganize Documents function will automatically reorganize documents based on the ranges specified in the
selected range file. To reorganize documents, select File > Administration > Reorganize Documents.
After selecting the range file, LAW will begin rebuilding documents based on the specified ranges. The reorganize
function should be performed prior to the OCR process to avoid complications, although it will reorganize text-based
OCR during the reorganize process. Any non-text OCR not associated with the leading document for a range will be
discarded. If an error occurs stating the image and OCR text are not synchronized, the reorganize process will be
aborted and the OCR will have to be either removed or corrected for the image that caused the problem. This issue
can occur for several reasons including: aborting the OCR process by canceling or an OCR engine crash, inserting
new pages into a document after the OCR process, or merging of documents with incomplete OCR.
336
Administration
Scanning for Errors

As cases increase in size, users will need a way to detect and/or eliminate certain types of problems. The Scan For
Errors feature provides a means to automatically search the database for some common problems. This function can
be run by selecting File > Administration > Scan For Errors... from the main menu.
Any errors detected are reported in a log file named "scandb.log" and is located in the "Log" folder in the user's temp
folder (%temp%\Law50\Log). If errors are detected, LAW will present the option to view this file when the scan is
complete.
Documents
This section allows the selection of either All Documents or the Current Folder to be scanned for errors. The Include
subfolders option will allow LAW to also scan the folders below the currently selected folder. The Ignore Native
Documents option prevents native documents (records without images) from being repeatedly scanned and logged
as errors.
Options
Find invalid records (missing images)
This option verifies each record in the database has a corresponding image. Users often delete or move files through
Windows causing LAW to contain records that do not point to valid images. These extra records can affect
processing and summary functions, so users should remove them. To remove any such records, select the Remove
if found option.
Find blank/missing Page IDs
337
This option is used to find documents with pages that have blank or empty Page ID entries. Whether intentional or
simply operator errors, certain export formats require non-blank Page ID entries for renaming or linking purposes.
This option provides a way to find the documents with blank entries so users can take the appropriate measures to
correct them. To modify the pages after they are found, use the Query->Blank Page IDs function in the standalone
grid display; once returned to the grid, the records can be easily modified or processed.
A 'missing' Page ID is defined as being a document record with an incorrect number of page-level records. Since
each document should have the same number of page-level records as the document's page count, this check
ensures (for example) that a 5-page document has exactly 5 records in LAW's page table. If any missing page
records are found, LAW will automatically sequentially number the PageID values of the missing page level records if
Auto-number missing pages is selected.
Find gaps in Page IDs

This option is used to find gaps or breaks in the numbering sequence. Pages in a case are typically numbered
sequentially. Sometimes, however, there may be breaks in the numbering sequence. This option allows users to find
these breaks to ensure that all pages are accounted for and to confirm these breaks, if any, are intentional and
correspond to the original documents.
Remove duplicate/orphan page records

This setting allows LAW to scan for duplicate page records where a document contains two "page 3's" for example.
Since there can only be one 'page 3', this record is safe to remove. The existence of this problem is often detected
while numbering a range of documents as it causes a duplicate PageID to be detected during this process.
An orphan page record is a page level record that no longer belongs to an existing document. This may have
occurred after a document was deleted, but a failure occurred deleting the page records for the deleted document.
These records are also safe to remove from the database.
Verify Page Counts

This option validates the page count of every image in the case (with a record). It does so by opening every image
and comparing the actual page count with the page count stored in the database. If the page count in the database is
incorrect, it will be updated, provided the Correct invalid database page counts option is selected. Because every
image has to be opened, this option can be very time consuming when cases become large. However, this option has
several benefits. First of all, it ensures that the total page count displayed in the Case Summary is accurate for billing
purposes. Second, by opening every image file, it ensures that none of the images have become corrupted (if they
are, it will be logged). Third, it ensures that there are no excess Page ID entries (entries for pages greater than the
actual page count) that can affect the export process.
338
Administration
Validating Document Ranges

When scanning documents at the production level, document breaks can often be incorrectly determined at scan
time. Document breaks can be manually corrected with a combination of the Merge Documents and Split Documents
functions, but users may not know what the actual document breaks should be unless pre-determined by a separate
process. If the document breaks have been pre-determined and recorded in a range file (comma-delimited text file
consisting of two fields: BegDoc# and EndDoc#), they can be validated after the scan process using the Validate
Ranges function and optionally reorganized using the Reorganize Documents function.
Validating Ranges
To run this function, select File > Administration > Validate Ranges . LAW will prompt the user for a range file.
Once specified, the documents will be compared against the range file in two passes. The first pass checks to ensure
all pages fall within the specified ranges. This pass is only useful 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
fall within one of the specified ranges will be reported in the error log.
If Yes is selected, the error log will be displayed.
The second pass actually validates all of the specified ranges against the documents in the case. Any ranges that are
not found will be reported.
339
Extracting Subsets
Located under Folder > Extract as Subset in the main menu, this feature dumps data and images of the current
folder to a selected output folder. Not all indexes and field properties are retained, so the output is not suitable for a
standalone working case. This feature has been designed for quick partial backups or re-importing purposes.
Note: This function works with either ADS or Access databases and always produces a project.mdb file. This
feature is not currently supported with SQL Server cases.
340
Administration
Run Commands
The following information is for advanced users of LAW and requires previous programming experience to utilize this
functionality.
LAW has the ability to run custom commands created by end users and run custom defined functions on a LAW case
(Tools > Run Command). The connection string to the current database will be passed to the executable so that it
may open and manipulate the current database. All command executables must be located in the
<AppPath>\Commands directory in order to be detected. The file description of the exe will be used as the menu item
name or the filename without extension if no description exists.
This feature also allows the running of scripts (i.e., VBScript, Javascript) in addition to actual executables.
Below is a sample Visual Basic connection string. The (VBA.Command) property will return the connection strings for
both an Access database and an ADS database.
Dim cnn as New ADODB.Connection
Dim rs1 as New ADODB.Recordset
Dim rs2 as New ADODB.Recordset
cnn.Open VBA.Command
rs1.Open "tblDoc", cnn, adOpenKeyset
rs2.Open "tblPage", cnn, adOpenKeyset
Note: Custom commands may be created by customers, but LexisNexis assumes NO responsibility for any
damage done by a user-defined command.
For a listing of index fields existing in LAW for both ED and non-ED-enabled cases, please see the Field Descriptions
topic.
Below is a run command provided by LexisNexis that can be used to populate RecordType values in the LAW case.
Populate RecordType Values

<RecordType> is a "virtual" field available only in the Export Utility and is used to classify exported records as e-docs,
e-mail, etc. The "Populate RecordType Values" run command can be used to populate this field within the LAW case
database thereby providing access to this data without having to export first. This command is intended for ED-
enabled LAW cases only.
An index field to store the values must be created prior to accessing the run command. The name of the field does
not matter; it does not need to be named RecordType. However, the field must be document-level and the type is
restricted to Text or Memo.
Once the field is created, click Tools > Run Command > Populate RecordType Values. Enter the name of the target
field and then click Begin. The possible values are:
LOOSE E-MAIL ATTACHMENT
E-MAIL ATTACHMENT
E-DOC ATTACHMENT
LOOSE E-MAIL
E-MAIL
341
E-DOC
IMAGE ATTACHMENT
IMAGE
When the process has completed, a "Success" message box will appear indicating the number of records
successfully updated.
342
Administration
Full Text Indexing

LAW supports the searching of full text for image or native records with associated text in SQL and SQL Express
cases. In order to perform full text searches in LAW, the text for the records must be indexed.
Records in LAW can have up to three types of text:
1. OCR
2. Printed
3. Extracted
Only one type of text for each record can be included in the index at any given time. For example, if a document
contains all three types and an indexing process is executed, then by default, only the OCR text will be indexed. If
OCR is not found for a particular document, LAW will look for Printed text, and then Extracted if Printed text is not
found. However, the order in which LAW looks for text to index can be modified - see the below "Indexing Options"
section.
Indexing Options
Options specific to the full text indexing process are located in the Indexing tab in Tools > Options. These options
can control how certain words, punctuation, etc. are handled during indexing. Auto-indexing can also be enabled from
this form.
343
Indexing options include:
Accent-sensitive - The indexer will take accents into account in indexing words with this option enabled.
For most users this is not recommended because this option increases the chance of missing the retrieval of
a document if an accent was omitted in one letter.
Automatically recognize dates, e-mail addresses, and credit card numbers - Enable this option to have
the indexer scan for anything that looks like a date, e-mail address, or credit card number during indexing.
Case-sensitive - The indexer will take capitalization into account in indexing words when this option is
enabled. In a case-sensitive index, "APPLE", "Apple", and "apple" would be three different words. This
option is not recommended because most users would like to retrieve a document containing Apple in a
search for apple.
Ignore duplicate documents during indexing - When enabled prior to indexing, LAW will not index any
duplicate records in the case. Duplicate records will have a DupStatus of either G or C. The "parent"
duplicate, DupStatus=P, will be included. Enabling this option could increase indexing, searching, and
review speed and efficiency by only including unique files in the index.
Insert word breaks between Chinese, Japanese, and Korean characters - Check this box if planning to
search Chinese, Japanese, or Korean documents that do not contain word 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 sees each line of text as a single long word. To make this type of text searchable, enable automatic
344
Administration
insertion of word breaks around Chinese, Japanese, and Korean characters so each character will be
treated as single word.
Run index process in background until cancelled (auto-index mode) - When enabled, the indexing
process will run in the background, referred to as auto-indexing. When running the indexer in this mode, the
indexer will continue to poll the database for new documents to index until it is cancelled. This allows the
indexing of documents during the import process, so that when an ED loader session is complete, the
documents are indexed and ready to be searched. Clicking the Hide button will minimize the Auto-Indexer
Status dialog to the system tray. To restore, right-click the icon in the system tray and choose Restore. A
count of total documents indexed will appear when resting the mouse pointer over the icon.
Note: The auto-indexer cannot be restored from the system tray when certain forms are displayed, such as
Batch Processing and the Query Builder.
Auto-start indexing prior to electronic discovery imports - Enable this option to ensure auto-indexing is
enabled prior to ED Loader imports. The option is useful in the event the auto-indexing option is
inadvertently left disabled.
Use local folder for temporary files during indexing - During indexing, the dtSearch Engine may need to
create temporary files to store word lists that are too large to fit into memory. By default, these files will be
placed in the index folder. Use this setting to instruct the indexer to use the local user’s temporary folder for
these files. The indexer 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.
Options specific to the handling of hyphens are also available.
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" would be indexed as
"firstclass."
All three - Applies all of the above options to allow multiple ways of finding text.
The Text Priority section displays the current order in which LAW looks for text when indexing document text. As
mentioned above, only one type of text (of the three possible types) can be indexed for a document at any given time.
The default order is OCR, Printed, and then Extracted. To change this order, click the Configure button. The
Configure Text Priority dialog will appear.
345
Choose the desired text types for options 1, 2, and 3. To only include a particular type in the index, such as
Extracted, choose Extracted for Option 1, and then choose <None> for options 2 and 3.
Note: If the above index options are changed after the case has already been indexed, the case will need to be re-
indexed in order for the changes to be applied.
Flagging Documents for Indexing

Documents must be in a "flagged" state in order to be included in the indexing process. LAW will do this automatically
when creating new records via electronic discovery, LAW case, and raw image imports when the new record has
associated text. Images created via scanning that are later run through the OCR process will be flagged as well.
Records with text imported via load file will need to be manually flagged (see remainder of section).
By default, LAW will also flag documents for indexing automatically when a new type of text is associated with a
record. For example, if text is extracted from a document during the ED Loader import, and that document is later
converted to TIFF and printed text is added, the new printed text will need to be indexed in order to become
searchable in LAW. This behavior can be modified using the following options:
1. [OCR] Reset text index status - This option is located in the OCR tab under Tools > Options and applies
only to the individual and batch OCR processes. De-selecting this option will prevent LAW from re-flagging
the document for indexing after the OCR process is performed. This means the OCR text for affected
records will not be searchable in LAW.
2. [TIFF Conversion] Reset text index status - This option is located in Tools > Batch Process > Options >
TIFF Options in the TIFF Output category and applies only to single document and batch TIFF conversions
when Save text with images is enabled. De-selecting this option will prevent LAW from re-flagging the
document for indexing after the TIFF conversion and printed text is created. This means the printed text for
affected records will not be searchable in LAW.
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, the document could be manually re-flagged
for indexing so the printed text for that document would be indexed instead. To flag a single document for indexing,
highlight a record in the document list on the main form and choose Edit > Reset Fulltext Flags > ON. To remove
the flag, choose OFF instead.
346
Administration
Resetting the text index flags for multiple documents can be done in one of two places. If all of the documents are in
one folder, select the documents in the document list (Ctrl+A to select all or use the Ctrl or Shift key to select specific
documents) and select Edit > Reset Fulltext Flags > ON|OFF from the main form. If the documents span multiple
folders and can be logically grouped in a query, or to reset all documents in a case, utilize the grid display. From the
standalone grid, select Tools > Reset Fulltext Flags > ON|OFF to reset the full text index flags for all documents in
the current record set. See the "_FTIndex Field" section below to learn more about the text flag values stored in this
field.
Once the desired documents have been flagged, they can be indexed by clicking Tools > Fulltext Index > Index
New Documents (see next section for more information).
Indexing Documents
After loading records via the Electronic Discovery Loader ("ED Loader"), LAW will prompt to index the new
documents' text if the Perform full-text indexing option in the ED Loader's Post Import Actions is disabled. Click
Yes to begin. If the option was enabled prior to import, LAW will begin indexing automatically after the import process
has been completed. An auto-indexing feature is also available for indexing text as a background process, allowing
text to be indexed as records are being imported rather than waiting for an EDD import to complete. This feature is
located in the Indexing options in Tools > Options and is explained in the above "Indexing Options" section. When
records with associated text are imported via the LAW case import, LAW will prompt to index once the import has
been completed.
If the indexing is not performed immediately after the ED import, it may be performed at any time thereafter using the
Tools > Fulltext Index > Index New Documents option. This feature will index any records that are "flagged" to be
indexed (see above "Flagging Documents for Indexing" section for more information). The entire case can be re-
indexed if needed by clicking Tools > Fulltext Index > Re-Index All Documents. This feature is useful in the event
an indexing option needs to be changed or the index has somehow become corrupt.
_FTIndex Field
The _FTIndex system field is automatically created when a case is ED-enabled and will store numeric status flags for
the indexing process. The possible values for this field are listed below:
0: No text is available for indexing.
1: Record's text is ready for indexing.
2: Record was re-flagged for indexing but has not yet been re-indexed.
3: Record's text has been indexed.
Full Text Index Properties

To view the index properties, launch the Query Builder (Tools > Search All Records), check the box beside Full
text search, click Options, and then click Index Properties. The Full Text Index Properties dialog will appear.
347
This screen provides details about the full text index for the current LAW case, such as size and the number of
indexed documents. Three functions also exist in this screen:
1. Purge Duplicates - This function will remove all records that were flagged as duplicate records in LAW
(DupStatus=G or C) from the full text index. This feature will first scan the case and then return the duplicate
count in a message box. Click Yes to remove the duplicates from the index or click No to cancel. To prevent
these records from being included prior to indexing, use the Ignore duplicate documents during indexing
option.
2. Compress Index - Compressing the index will remove obsolete records from the index. Obsolete records
may include documents that were deleted from the case or records that were removed from the index using
the Purge Duplicates feature. These obsolete documents will NOT be returned in searches. If the
"ObsoleteCount" value in this dialog is greater than zero, use the Compress Index function.
3. Verify Index - This function will check the full text index for problems or corruption. If any issues are
discovered, an error will be returned after running the verify and the case will likely need to be re-indexed.
348
Administration
Configuring LAW and SQL Server

Important: Please contact LexisNexis for instructions on configuring SQL Express.
Enable LAW SQL Server Support

To enable SQL Server support with LAW, choose Tools > Options > Preferences tab and check the box beside
Enable SQL Server/MSDE support. When this option is used, an additional database engine option of MSDE / SQL
Server will be available when creating a new case. With this database engine type selected, enter the name of the
SQL Server located on the network (name of server running SQL Server). This value is saved and must only be re-
entered if the server name changes.
Note: This database type is enabled by default upon installation and may be disabled to remove this choice when
creating a new case. To disable the option, open any case in LAW and choose Tools > Options, click the
Preferences tab, and deselect the "Enable SQL Server/SQL Express Support" option.
Create SQL Server LAW User Account(s)

There are currently two methods of specifying user accounts for use with SQL Server. One of these methods must be
used to allow LAW access to the LAW cases stored on the server.
Global Default User

The following user, with create/modify permissions, must exist on the SQL Server to create a generic global user
account:
User: LAW_User
Pwd: law32sql
LAW will use this account to access and create databases. This allows SQL administrators to prevent LAW from
accessing and modifying any other existing databases.
When using the default user, the security mode for SQL Server must be set to SQL Server and Windows or mixed-
mode authentication. See the SQL Server's instructions on how to do this.
Integrated Security
Windows integrated security may be used when accessing/creating SQL Server cases. This will allow a user to
create SQL Server cases without adding a special user to SQL Server as long as the current user has database
create permissions on the specified SQL Server. To enable this feature, check the Use Windows NT integrated
security option when specifying the database backend for newly created cases.
Note: If using this method, each individual user must be setup on the SQL Server to allow access to the case.
SQL Server Notes

All testing has been performed internally using SQL Server 2000, but SQL Server 7 or higher should be
supported.
349
LexisNexis does not provide any other SQL Server configuration recommendations or hardware
recommendations. All information is publicly available for the customer to locate and determine the best
possible configuration for its intended usage.
350
Administration
Tracking Page Source, Size, and Color

LAW can capture the source, size, and color at a page level for scanned and imported images, as well as images
created via TIFF Conversion within LAW cases. This data is stored in five page-level system fields (PageSource,
PageSize, PageHeight, PageWidth, and PageColor) in the LAW database and can be viewed in the main user
interface Index display and in the two grid displays, and can be queried using the Query Builder.
This page-level data is captured "real-time" for scanned pages; in other words, all five fields are populated as the
pages are scanned into the case. Images acquired via raw image or load file imports will receive only a source value.
Images created in LAW via TIFF Conversion or single document TIFFing will receive a PageSource and PageColor.
Note: Images affected by the "Treat native TIFF images as image for record (bypass TIFF Conversion)" setting will
not receive a PageColor value.
A batch process is available to populate this missing information for TIFFed and imported images. The remainder of
this topic will explain this feature in more detail.
Note: See the Page Properties Report topic to learn how to create a report containing the page-level information
discussed in this topic.
Field Names and Possible Values

The five fields used to store these page-level properties are PageSource, PageSize, PageHeight, PageWidth, and
PageColor. Three of these fields are lookup fields and are listed differently within the actual database. Possible
values contained in these fields are listed below this paragraph. The lookup field names as referenced in the
database are shown in parentheses beside the field name displayed in the LAW interface. Also, the numeric values
used in the database are listed in parentheses beside the textual value users will see in LAW.
PageSource (SourceID)
Feeder (1)
Flatbed (2)
Imported (3)
TIFF Conversion (4)
Manual TIFF Conversion (5)
PageColor (ColorID)
Black & White (1)
Color (2)
Grayscale (3)
PageSize (PageSizeID)
Letter (1) *8.5x11
Legal (2) *8.5x14
Double Letter (3) *11x17
Oversized (4) *Any pages outside the above 3 sizes
351
PageWidth
Varies (Example: 8.5)
PageHeight
Varies (Example: 11)
Note: A page size tolerance ini setting currently exists at the application level. This setting can be used to set a
margin for the page size values. The default value of the tolerance is set to .1; for example, everything up to 8.6 x
11.1 will still be considered a 'Letter' size page. The setting can be modified by editing the Law50.ini file in the
application path (same folder as the Law50.exe file). The section is [Settings] and the key is PageSizeTolerance=
<value>. If the [Settings] section does not already exist, add the section above the key value; if it does exist, add
PageSizeTolerance to the existing section.
Update Page Data Batch Process

The Update Page Data batch process (Tools->Batch Process) can be used to populate the PageColor, PageSize,
PageWidth, and PageHeight fields for any images in the selected record set missing this information. PageSource is
not affected during this process as the source can only be captured at the time the image is acquired. As mentioned,
imported images in LAW will only receive a PageSource value and images created by TIFFing will only receive
PageSource and PageColor values (see first note in this topic); therefore, this process is necessary to populate the
remaining fields if this type of data is needed for a particular project.
352
Administration
Reporting
Viewing Reports
LAW provides several pre-defined reports that can be used to gather specific data related to electronic discovery
imports. A number of options, such as sort order, are available for each report type as well as global settings that
allow the inclusion of a personalized logo.
This reporting feature is available in both SQL and Access LAW cases. If a case is not enabled for electronic
discovery, only the Page Properties and Tally reports will be available in the report selection panel.
The report management screen can be accessed in one of two ways. One method is to click File > Administration >
View Reports from the main user interface. The second method is to launch from within the standalone grid display.
Click Tools > View Reports. The View Reports dialog will appear.
If the View Reports dialog is launched from the grid, or if either grid is active when the tool is launched, certain reports
can be limited to the current record set loaded in the grid. See the individual report topics for more information.
Generating Reports
In ED-enabled cases, the left panel of the View Reports dialog contains two groups. The first group, ED Loader
Sessions, contains reports that show ED Loader session data for the current case. The second group, General,
353
contains the remaining reports that relate to other areas of the application. Click on each report in the list to see a
description in the Report Description section located at the bottom of the form. Select the desired report on the left
before moving to the option selection area.
The second panel contains options for each report. The first column lists the setting name while the second column
allows editing of the setting value. Click the rows to view descriptions of each option directly below the options area in
this panel. To remove the grouping in the options area, click the "Alphabetical" button located above the options. The
group headers, Global Settings and Options, will be removed. These group headers can be returned by clicking the
"Categorized" button.
The Global Settings apply to every type of report and when they are changed, the changes persist to the other
reports as well. The two global settings are:
1. Display Custom Logo - If this setting is set to True, and a path is specified in the Logo Filename setting,
the logo will appear on the first page of the report.
2. Logo Filename - To select a logo, click the ellipsis button in the second column beside this setting, browse
to the desired image file (.bmp, .jpg, or .gif), and then click Open. The path to the image will appear in the
field. In order for the logo to appear, the Display Custom Logo setting must also be set to True.
3. Logo Location - The logo can be placed in one of the following locations on the first page of the report: Top
Left, Top Right, Bottom Left, or Bottom Right.
The Options located below the Global Settings are 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).
Once the report has been selected and the options are set, click the View Report button. The report will be
generated and launched in the Report Preview screen.
354
Administration
From the Report Preview screen, the report can be previewed and then saved to file or printed. The Save File button
in the toolbar will launch the Save As dialog. From here, the file type for the report can be selected from the Save as
type drop-down list, such as Adobe PDF. Once the file type is chosen, browse to the desired location, enter a file
name, and then click Save. A Print button is also available in the toolbar for printing the report directly to paper or to
a file.
Report Types
The following reports are available in the View Reports dialog:
1. ED Loader Session
2. Exception
3. Deduplication or Inter-Case Deduplication*
4. Files By Type
5. Files By Type Summary
355
6. Page Properties
7. Tally
*The type of deduplication used in a case will determine which type of report will appear in the View Reports dialog.
Click the names of the reports above to read more about each individual report.
356
Administration
ED Loader Session Report

The ED Loader Session Report provides an overall summary of all or selected sessions in the current LAW case as
well as a breakdown of each individual session.
Report Options
In addition to the Global Settings, the following options are available for the ED Loader Session report:
1. Included Sessions - By default, this option will be set to All Sessions, meaning all sessions in the current
case will be included in the report. Click the ellipsis button in the second column to launch the Select
Sessions dialog and select specific sessions. Clicking on the Title or Created column header will sort the
session list.
2. Sort Field - Two fields are available for sorting the report:
1. Date Created - This option will sort the sessions based on the date and time the session was
created in the ED Loader.
2. Session Label - The session label is specified in the ED Loader Sources tab prior to the start of
each session. This option will sort the report based on the session label values.
3. Sort Order - Choose Ascending or Descending for the values in the selected sort field.
ED Loader Session Report Contents

This section discusses the contents of the ED Loader Session report.
357
The first section of the report, the session summary, indicates the number of sessions included in the report within the
header (see above image).
Session-level sections will contain the session label, session ID, and start date and time for the session (see above
image).
Below the header in the session summary, the report displays counts of recoverable and non-recoverable items for all
selected sessions, as shown in the above image. The term "recoverable" indicates the session can be restarted in an
attempt to obtain files that had not yet been processed due to the session not completing (i.e. process was cancelled
by user). The above data is a summary of the Status field found in each session-level section of the report.
The session-level section provides the session status and creator (user and machine name extracted when session is
initialized) (see above image).
The above image shows the next area of the report, which displays the number of records written to the LAW case
database (after full expansion), the number of items processed (prior to expansion), the estimated time it took to
process (or import) the data, and the approximate processing speed in records per hour. These four items are
available in both the session summary and session-level sections of the report.
The next three sections of the summary are also included in both the session summary and session-level areas.
The Session Contents section (above) shows counts for all e-docs, embedded files, e-mails, e-mail attachments,
archives, and archive attachments in the selected sessions (including files that received errors or warnings, filtered
files, etc.) and the total file size. The file counts and file sizes (post-process sizes) are also broken down by file type
(i.e. e-docs) in this section.
The Errors/Warnings section (above) displays totals for processing errors, commit errors, warnings, and incomplete
records for all selected sessions.
The Filters section (above) displays a list of all available ED Loader filters and a count of how many files were filtered
by each type for all selected sessions.
358
Administration
Exception Report
The Exception report provides both a summary and a detailed overview of ED Loader session exception data. This
report focuses on records that were filtered or received errors or warnings during the ED Loader import process.
Report Options
In addition to the Global Settings, the following option is available for the Exception report:
1. Included Sessions - By default, this option will be set to All Sessions, meaning all sessions in the current
case will be included in the report. Click the ellipsis button in the second column to launch the Select
Sessions dialog to select specific sessions. Clicking on the Title or Created column header will sort the
session list.
Exception Report Contents

The Summary section of the Exception report provides three sets of information: Item Summary, Filters, and Errors.
The Item Summary displays a count of items processed (prior to expansion), items discovered (after expansion),
records written to the LAW case database (after expansion, filtering, errors, etc.), and records that were not written
due to errors or filtering. Post-process file sizes are also included for the last three items mentioned.
359
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 occurred during processing, but records
were likely still written to the case database), commit errors (errors that occurred during processing and prevented
the record from being written to the case database), warnings, and incomplete records (records that will be listed 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, filter actions, a list of warnings and
error messages, and a list of sessions included in the report.
This portion of the Details section shown in the above image lists all filters that were applied to records during the
selected sessions as well as the count of records filtered and the total file sizes (post-process) for each. All enabled
filters may not be listed here - if no records matched a particular filter, then that filter will not be shown. For the filters
that include scope and action settings (Duplicates and File Types), the file count and file size for each scope and
action setting is included in addition to the totals.
360
Administration
The next portion of the Details section, shown above, will list all warning and error messages that occurred during the
ED Loader session and a record count will be displayed for each type of warning or error. Total error and warnings
counts are also shown.
The last portion of the Details section, shown above, contains a list of sessions included in the report. The sessions
are referenced by their session labels. The total number of included sessions is also displayed here.
361
Files By Type Report

The Files By Type report contains a list of native files associated with electronic discovery records in a LAW case.
The records will be grouped by their file type description, such as Adobe Portable Document Format or HyperText
Markup Language. Non-ED records may optionally be included in the report.
Report Options
In addition to the Global Settings, the following option is available for the Files By Type report:
1. File Type Filter - Three filters for the report are available:
a. All File Types - This option includes both supported and unsupported file types in the report. The
term "supported" refers to files with a valid source application assigned for printing, such as Adobe
Acrobat or Microsoft Word. Non-ED records may be included depending on the state of that setting
(see #2).
b. 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).
c. 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.
2. Include Non-ED Records - When set to True, non-ED records such as scanned documents or images
imported via load file will be included in the report, provided the All File Types or Supported File Types filter
is selected. These records will be grouped under the <Non-ED Records> header.
Files By Type Contents

The contents of this report will vary depending on the selected options. A report generated using the All File Types
and Include Non-ED Records=True options is shown in the below image.
362
Administration
The report groups the entries by their file description or by the <Non-ED Records> header for non-ED records, such
as scanned documents. The group header will also display the total file count for that type, the number of pages (if
available), and the total file size. The page counts and file sizes are also available for each individual file. The Pages
value is pulled from the PgCount field in the LAW case. If the PgCount is not greater than zero, LAW will check the
EDPages field and use that value. The file sizes are post-process file sizes.
363
Files By Type Summary Report

The Files By Type Summary report provides a condensed version of the Files By Type report by providing native file
counts and sizes per source application. This report does not include a listing of every native file path, which is the
key difference between the Files By Type Summary and the Files By Type report.
Report Options
In addition to the Global Settings, the following option is available for the Files By Type report:
1. File Type Filter - Three filters for the report are available:
a. All File Types - This option includes both supported and unsupported file types in the report. The
term "supported" refers to files with a valid source application assigned for printing, such as Adobe
Acrobat or Microsoft Word. Non-ED records may be included depending on the state of that setting
(see #2).
b. Supported File Types - This option includes supported file types only in the report. Non-ED
c. Unsupported File Types - This option includes unsupported file types only in the report. Non-ED
2. Include Non-ED Records - When set to True, non-ED records such as scanned images or images imported
via load file, will be included in the report.
Files By Type Summary Report Contents

The contents of this report will vary depending on the selected options. A report generated using the All File Types
option is shown in the below image.
364
Administration
This report shows a listing of each unique file type included in the case. For each file type, the report provides a total
file count, the total number of pages, and the total file size (post-process). The Pages value is pulled from the
PgCount field in the LAW case. If the PgCount equals zero, LAW will check the EDPages field and use that value.
365
Deduplication Reports
The Deduplication report provides a summary and detailed view of deduplication information for the current case. If
documents in the LAW case were deduplicated using the ED Loader or LAW's internal Deduplication Utility (or 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, then the "Inter-Case
Deduplication Report" will be displayed in the report list. This report includes the same information as the
Deduplication report, but includes data from any cases the current case was deduplicated against. This report does
not list the case name at the top since the information may apply to more than one case.
Report Options
In addition to the Global Settings, the following options are available for the two deduplication reports:
1. 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 be included for each custodian. Set this option to
False to exclude the Custodians section from the report.
2. 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 (minus attachments) in the case(s), followed by
duplicate totals.
3. Group File List By - If the Parent/Duplicate File List is included in the report (see above option), the Group
File List By option can be used to group the file list by parents or duplicate records.
Deduplication Report Contents

Two sections exist below the Summary header in the deduplication report: Process Summary and Duplicates.
366
Administration
In the Process Summary, the Total Records count represents the number of records in the current LAW case (and
member cases if the report spans multiple cases). The Processed count represents the number of records that have
been deduplicated, while the Unprocessed count represents the number of records that have not been deduplicated
(DupStatus = Null or U). Files that are ineligible for deduplication (i.e. images imported via raw image import) will also
be included in the Unprocessed count.
The Duplicates section lists the duplicates and file size totals. The Total Duplicates count is the total number of
records that have been flagged as duplicates (DupStatus=G or C). The "Dup. (non-att.)" count is the number of
records that are duplicates (DupStatus=G or C) and may or may not have attachments. The "Dup. Atts" count is the
number of records that are duplicates (DupStatus=G or C) and are attachments. For example, an e-mail item
containing two attachments would be counted as 1 record for the Dup. (non-att.) section since it is the master
duplicate of the family; then, the two attachments would be counted as 2 records for the Dup. Atts section since those
records have received a duplicate status based on their parent record. The file sizes of the duplicate files in LAW are
provided beside these totals in both MB and GB.
If the Display Custodian Details option was set to True prior to creating the report, the following Custodians section
will appear below the Summary.
The Custodians section contains the same information as the Summary, but is the section is sorted by Custodian
name and the data is broken down for each custodian in the associated LAW case(s). In the above example, nine
total records exist in the case with 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 following Parent/Duplicate
File List section will appear next.
367
This section contains a file listing of duplicates and their associated parent records for the associated LAW case(s).
This file list can be useful for listing and/or locating duplicate records for each original duplicate record in the case.
Attachment records are not included 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 the parent records
(DupStatus=P) and the duplicates are listed below their respective parent 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
will display a total count of global duplicates (DupStatus=G) and a total count of custodian-level duplicates
(DupStatus=C).
368
Administration
Page Properties Report

LAW can capture the source, size, and color information at a page level for images in a case. The reporting tool
utilizes this information to provide tallies of each property for 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 Properties report:
1. Document Range - When the range is set to All Documents, the report will span the entire LAW case. The
Current Record Set option will only be available if one of the grid displays are active when launching from
File > Administration or when launching from the standalone grid display's Tool menu (View Reports).
2. 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.
3. Group By Field (Y-Axis) - Choose from one of the following options: Page Source, Page Size, or Page
Color. The values in the selected field will appear in the Y-axis. The same field cannot be selected for both
the Primary and Y-Axis grouping options.
Page Properties Report Contents

The report layout will vary depending on the fields selected for the primary and Y-axis grouping. In the following
example, Page Color was selected for the primary "group by" field and Page Size is in the Y-axis.
369
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. Within these 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 right side of the report). The Source data (i.e. Feeder) and totals are listed horizontally in each section.
Note: To learn where the Page Properties report data is pulled from, what the fields mean, and how the data is
populated, see the Tracking Page Source, Size, and Color topic.
370
Administration
Tally Report
The Tally report can be used to produce a report listing the unique values present in a system field or in a user-
defined index field followed by the total number of times that unique value exists in the selected index field.
Report Options
In addition to the Global Settings, the following options are available for the Tally report:
1. Display Custodian Details - When set to True, the Tally report will be grouped by any custodians that exist
in the current case.
Note: If the current case is not ED-enabled, this option will not be available.
2. Document Range - When the range is set to All Documents, the report will span the entire LAW case. The
Current Record Set option will only be available if one of the grid displays are active when launching from
File > Administration or when launching from the standalone grid display's Tool menu (View Reports).
3. 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 are excluded from this list: page-level
fields, fields with the Unique property applied, auto-increment fields, and any field starting with the character
"_" (underscore). Field values containing delimited lists such as “A; B; C” will be tallied as a single unique
value rather than individual items.
Warning: While memo fields are included in the Field To Tally list, the data will automatically be
truncated to 255 characters in the report.
4. Number of Columns - The data in the report can be displayed in 1, 2, or 3 columns on each page of the
report.
5. 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 alphabetically based on the values located in the selected
tally field. If Totals is selected, the data will be sorted based on the tally results for each field value.
6. Sort Order - This option is used to sort the data in the "Sort Field" Ascending or Descending in the report.
Choose None to avoid applying a specific sort order.
Tally Report Contents

The following Tally report sample is set to display custodian details and the tally field is set to DocExt, as indicated in
the header below the LAW case name.
371
The number beside the custodian indicates the number of unique field values for that custodian. The number to the
right in the heading indicates the total number of field values in the tally field for each custodian. The count of each
unique value is displayed to the right of the value below the section heading. For example, in the above report, five
records exist with a value of "CustodianA" in the Custodian field and a value of "doc" in the DocExt field. If the tally
field does not contain a value for any of the selected documents, the report will include a <Null> entry.
If the Display Custodian Details option is set to False, the report will appear as shown below:
372
Appendix
Appendix
Deduplication Information
This topic is intended to provide users with an understanding of the current deduplication process implemented in
LAW and the related Inter-Case Deduplication utility. Items discussed include: methods used to deduplicate e-mail
and e-docs, a list of deduplication-related fields and possible values, and brief explanations of deduplication options
and their resulting output.
Key Generation
Key generation refers to the hashing of either the entire input file (e-docs) or a set of metadata values extracted from
the file (e-mail); file hashing and metadata hashing are the two primary methods used by the ED Loader for
generating keys. Currently, the ED Loader generates two output hashes in parallel: MD5 and SHA-1. Users can
choose which of these is used in the deduplication process in the ED Loader options.
E-docs: The key value is generated using the entire file as the input.
E-mail: The key value is generated using an input value of certain metadata after processing of the metadata fields
has been executed. The purpose of using the post-processed metadata is to match the metadata that is stored in
LAW; therefore, if the key is regenerated in the future, the value would match the original. E-mail includes both e-mail
messages contained in mail stores and loose e-mail messages. The term "loose e-mail" refers to a file that is
identified as a mail item and successfully converted to a mail item by Outlook. These include .msg files, .eml files,
and other RFC822-format e-mails. The fields shown below are used to generate the deduplication key for e-mail and
loose e-mail items:
BCC
Body
CC
From
IntMsgID
EMail_Subject
To
Attach (semi-colon delimited string of first level attachments in the e-mail)
- OR - AttachmentContentHash (if the "Include attachment hashes in e-mail metadata hash" option is
enabled in the ED Loader Deduplication setting, the hashes of the attached files will be included in the parent
e-mail's metadata hash as opposed to the above Attach field)
Fields
Five fields in LAW are used to store information regarding deduplication test results and other deduplication-related
data.
DupStatus: Indicates the duplicate state of the document. This is the primary field used for differentiating duplicate
items from non-duplicate items. DupStatus is a single character field and will contain one of the following values:
U - Indicates the record was not tested (not deduplicated).

N - Indicates the record was tested and was not determined to be a duplicate at the selected scope
(Global/Custodian-level).
G - Indicates the record is a global-level duplicate.
C - Indicates the record is a custodian-level duplicate.
373
P - Indicates the "parent" duplicate. This value is set when a duplicate has been identified. The record that
was assigned the "G" or "C" status will have the same _DupID value as this parent record (see _DupID field,
explained below).
_DupID: This field is designed to provide a mechanism for grouping duplicate records with their "parent" duplicates. A
document determined to be a duplicate via ED Loader deduplication or the LAW Deduplication Utility will contain the
same LAW ID field value as any other records that were determined duplicates of that particular document. The
parent duplicate will store its own ID in this field. Drag and drop this field into the grouping area in one of the grid
displays to view the parent and "child" duplicates together.
Records deduplicated via inter-case deduplication are slightly different. Parents and their duplicate records will still
have matching _DupID field values; however, the value will not be pulled from the ID field in LAW. This value will
instead come from an ID assigned to records in the external deduplication database. The ID for each parent and
duplicate will be the ID of the parent, as assigned in the tblDupLog table's DupID field.
_DupMethod: Indicates which hash type was used in testing the duplicate state of the record. Possible values are:
1 - MD5 hash
2 - SHA-1 hash
129 - MD5 hash and record was included in an inter-case deduplication process
130 - SHA-1 hash and record was included in an inter-case deduplication process
MD5Hash: Stores the MD5 hash value of the record. If a file is considered to be a duplicate, this value will be equal
to the deduplication key.
Sha1Hash: Stores the SHA-1 hash value of the record. If a file is considered to be a duplicate, this value will be
equal to the dedup key.
Scopes
Scope refers to the range of deduplication keys that will be tested to determine the record’s duplicate state. The
scope may be specified by the user in the ED Loader’s Deduplication settings, the LAW Deduplication Utility, and
Inter-Case Deduplication utility. Two options are available:
Global: The Global scope will result in the incoming records’ deduplication keys being tested against ALL
other keys, regardless of how the other records’ scopes were logged.
Custodian: The Custodian scope will result in the incoming records’ deduplication keys being tested against
all other keys that have the same CustodianID value.
Actions
The Action options are used to limit or exclude the data stored for a record that is considered to be a duplicate.
Options include:
(Include) Log record: Duplicate records are added to the LAW case normally, including the native file, and
all associated duplicate fields are set.
(Partially Exclude) Log record but do not copy file: Duplicate records are added to the LAW case
normally and all associated duplicate fields are set, but the native file is not copied to the case folder.
(Exclude) Do not log record or copy file: Duplicate records are completely excluded from the case. The
record is not added to LAW and the native file is not copied.
Attachments
Attachments will simply inherit the DupStatus of their parent item. This includes all types of attachments, such as e-
mail attachments, attachments to an archive file (i.e. zip), and loose e-mail message attachments.
374
Appendix
(Partially Exclude) File Type Filter Action and

Deduplicating
When this action is selected, and File Type Filtering is enabled, duplicate checking is executed normally. Records
without native files can still be flagged as duplicate parents or children.
375
Unicode Support
LAW versions 5.2 and higher will support the Unicode standard. Proper language packs must be installed on the
computer in order for the associated Unicode characters to display within LAW’s user interface.
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 and any other applicable folder view in the
application. Unicode existing in the metadata will be retained and can be displayed in the Index display.
The two grid displays in LAW do not support Unicode. However, if Unicode characters exist in a field they
will be displayed in a pop-up text box when resting the pointer over the cell.
Unicode is not supported in LAW case names. While the rest of the case path can contain Unicode, it is
recommended the case paths do not contain Unicode characters to avoid potential issues with 3rd party
applications.
Index field names cannot contain Unicode characters.
The "Text/RTF Printer" does not support Unicode text files. It will support RTF with Unicode. This is a
limitation of the underlying component. To print Unicode text files, use either Microsoft Word or the Shell Printer
as the source application.
Note: If using the Shell Printer, you must ensure that the application registered on the system for text
files supports shell prints For example, Notepad supports shell prints.
Unicode data can be retained when exporting field data from the two grid displays. In order to retain this
data in the output file, you must select "Unicode Text (Tab delimited)(*.csv)" in the "Save as type" drop-down
list in the "Save Results As" dialog box.
Unicode data is supported in the Export Utility in the following export formats:
1. CaseLogistix - Unicode is automatically included if present in the exported data.
2. Delimited Text - Unicode data will be included only if the "Allow Unicode data (UCS-2 format)"
option is enabled in this format's configuration settings.
3. EDRM XML 1.0 - Unicode is automatically included if present in the exported data.
4. Concordance Direct DCB - Unicode data will be included only if Concordance version 10 or above
is installed on the machine and the "Create Concordance 10.0 database (supports Unicode)
setting is enabled in the format's configuration settings. Unicode is only supported in
Concordance versions 10 and above.
5. Concordance - Unicode data will be included only if the "Allow Unicode data (UCS-2 format)"
option is enabled in this format's configuration settings.
In the Export Utility, when exporting to a format that does not support Unicode, do not use the Mirror Original
folder naming scheme if Unicode folders exist in the case. Also ensure the export path does not contain
Unicode. Unicode paths and filenames may prevent the target applications from opening the associated image,
text, and/or native files.
The ExperVision and TextBridge OCR engines do not currently support Unicode. Supported languages can
be found in the Language drop-down list located in the OCR tab in Tools > Options. Printed and extracted text
will contain Unicode data if it exists in the original file and can be displayed, provided the proper language
pack(s) are installed on the system.
376
Appendix
Shortcut Keys
Note: If the shortcut keys are not functioning, and a grid display is currently active, please ensure that Review
Mode is disabled in the grid. See the Tagging Records section for more information.
Function Keys
F1 - Help File
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 &endash; Duplex **
F12 - Scan Mode &endash; Flatbed **
** Scanner must support these modes to have any effect.
Control Keys
<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> - Goto 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
377
<Ctrl+1> - Black and White Scanning
<Ctrl+2> - 8-bit Grayscale Scanning
<Ctrl+3> - 24-bit Color Scanning
<Ctrl+F3> - Scan New Attachment
<Shift+Ins> - Attach to Previous
<Shift+Bksp> - Detach All
<Ctrl+F4> - Enhance Image menu
<Ctrl+F6> - Replace Document
<Ctrl+Ins> - Insert New Pages (from scanner)
<Shift+Del> - Delete Pages
<Ctrl+F12> - Merge Annotations
<ESC> - Clear current region (if main image has focus)
<ESC> - Clear selected pages (if thumbnails display has focus)
<Ctrl+PgDn> - Zoom In
<Ctrl+PgUp> - Zoom Out
<Ctrl+Left> - Pan Left (moves image, if zoomed)
<Ctrl+Right> - Pan Right (moves image, if zoomed)
<Ctrl+Up> - Pan Up (moves image, if zoomed)
<Ctrl+Down> - Pan Down (moves image, if zoomed)
<Alt+UpArw> - Increase scan brightness (32pts)
<Alt+DnArw> - Decrease scan brightness (32pts)
Document List Keys

Note: The focus must be on the document list to use these shortcuts.
<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
378
Appendix
Contacting LexisNexis
About LexisNexis
LexisNexis offers the broadest choice of discovery solutions, giving law firms, corporations and government agencies
the control and confidence they need to litigate successfully in the face of overwhelming data volumes and rapidly
changing technology.
Please visit our web site: http://law.lexisnexis.com/law-prediscovery.
Technical Support
Our #1 priority is our customers. If you are having any technical difficulties with our products, feel free to call or e-mail
us. Our representatives pride themselves on resolving customer issues quickly and effectively.
Technical support for LAW is offered via e-mail or phone and is included for 1 year from the initial date of purchase.
New maintenance agreements (providing support and updates) may be purchased on an annual basis. Free
telephone support is available to LAW demo users. The telephone support center is open 8am to 7pm (CST)
Monday-Friday.
Support requests will typically receive a response the same day, if not within the hour. We will make all possible
attempts to correct any bugs or assist you with system specific problems you may experience.
We welcome your input regarding the product as well as specific feature requests. We value any requests or
recommendations you may have, as LAW has been developed as a result of user demand and feedback. We cannot,
however, make any guarantees that all or any feature requests will be implemented.
Please submit support or enhancement requests using the following information.
E-mail: lawsupport@lexisnexis.com
Phone: 866-831-0497
Training
LexisNexis products are designed to be intuitive and easy to learn. Nevertheless, we find that education is a wise
investment for the successful use of our products. Use the information below to learn what our training department
has to offer.
E-mail: lawtraining@lexisnexis.com
Phone: 425-463-3503
Sales
E-mail: lawsales@lexisnexis.com
Phone: 866-831-0497
379

LAW Pre Discovery User Guide

Caricato da

Informazioni sul documento

Descrizione originale:

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

LAW Pre Discovery User Guide

Caricato da

Copyright:

Formati disponibili

LAW PreDiscovery™ Software

© 2008 LexisNexis, a division of Reed Elsevier Inc. All rights reserved.

▪ General Product Information: www.lexisnexis.com/law-prediscovery

LAW Licensing .................................................................................................................18

Browsing to a Case .......................................................................................................................36

Field Types ...........................................................................................................................................................39

Changing Field Properties.............................................................................................................39

New Case .............................................................................................................................................................41

Existing Case ........................................................................................................................................................42

Populating List Items.......................................................................................................44

Default Custodian ..........................................................................................................................54

Exporting Session Data .................................................................................................................82

Color Format .........................................................................................................................................................94

File Type ...............................................................................................................................................................94

Storage Schema ...................................................................................................................................................95

Barcode Breaks ....................................................................................................................................................95

Scanning in LAW ...........................................................................................................................96

Inserting Documents .............................................................................................................................................97

Modifying Existing Documents ......................................................................................................97

Inserting Pages .....................................................................................................................................................97

Using Barcodes .............................................................................................................................99

Folder Level ..........................................................................................................................................................99

Document Level ..................................................................................................................................................100

Attachment Level ................................................................................................................................................100

Ignore Barcode Value .........................................................................................................................................100

Storing Barcode Break Sheet Values in a Field ..................................................................................................100

Dilate Scan Region .............................................................................................................................................100

Scan Entire Page ................................................................................................................................................100

Use Thorough Scan ............................................................................................................................................100

Extracting Barcode Information...........................................................................................................................101

Troubleshooting Barcode Breaks ................................................................................................101

Z-Print Load File .................................................................................................................................................103

Doculex Imagebase ............................................................................................................................................105

Opticon Load File................................................................................................................................................105

Summation Load File ..........................................................................................................................................105

IPRO Load File ...................................................................................................................................................107

EDRM XML 1.0 ...................................................................................................................................................107

Importing Raw Images.................................................................................................................108

Convert images to binary (B&W).........................................................................................................................109

Determine document breaks ...............................................................................................................................109

Include OCR .......................................................................................................................................................109

Link to images in place .......................................................................................................................................110

Remove originals ................................................................................................................................................110

Use filename as BegDoc#...................................................................................................................................110

Mirror original structure .......................................................................................................................................110

Store original filename ........................................................................................................................................110

Store original location .........................................................................................................................................110

Viewing Images ...........................................................................................................................111

Zoom In/Zoom Out..............................................................................................................................................111

Best Fit/Fit to Width.............................................................................................................................................111

Zoom Lock ..........................................................................................................................................................111

Scrolling the Image......................................................................................................................111

Viewer Options ............................................................................................................................112

Scale to Gray ......................................................................................................................................................112

Rotating Pages ............................................................................................................................112

Replacing a Document ................................................................................................................131

Deleting Records .........................................................................................................................157

Retrieval Thresholds ...........................................................................................................................................174

Performing Full Text Searches....................................................................................................175

Tagging Text Hits................................................................................................................................................176

Term Searching ..................................................................................................................................................177

Noise Words .......................................................................................................................................................177

Combining Database and Full Text Searches.............................................................................178