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

LAW PreDiscovery User Guide

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

LAW PreDiscovery User Guide

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

..............................................................123 Deleting Documents .............................117 Manipulating Documents .....................129 Inserting Pages............................................................................................................................................................................................................................................................................112 Thumbnails Display .................................................................................................................................................................................................................................................................................................................................................................................................................................................121 Deleting Documents/Pages...................................................................................................................................................................................................................................................................................121 Moving Pages...........................................................................................120 Moving Documents/Pages .....................................119 Rotate Pages...........116 Viewing Properties for Image Records..................................................................111 Zoom Lock ...............................................................................................................................116 Viewing File Properties for Native Records.....................123 Splitting Documents.................................................................................125 Split Options .................................................................LAW Licensing Viewing Images .....................................111 Scrolling the Image.........................................................................................................................................................................129 Inserting Existing Pages ...............123 Deleting Records from the Grid Displays ......................................................................................................................................................................................................................................131 7 ..............126 Merging Documents .......................................................................................................................................112 Page Navigation ............................................................................................................................................................................................................................................................................................................................................................................................................................................111 Best Fit/Fit to Width....................................................112 Scale to Gray .........................................................................................................119 Page-Level Cleanup ....................................................................................................116 Image Page Properties...................................................................................................................................119 Enhancing Images.................130 Replacing Document/Pages....................................................................................................................................................111 Viewer Options ......................111 Zoom In/Zoom Out.......................................................................................111 Zoom Features ................................................................................................................119 Deskew................................................129 Inserting Documents.........................................................111 Pan Window...........................................112 Rotating Pages .................................................121 Moving Documents........................................................................................................................................................................................................................................112 Invert ...............................................................................................................................................................................113 Selecting Pages.....................................................................123 Deleting Pages .....................................................................................113 Viewing File Properties ...128 Inserting Document/Pages ..............................................................................................................................................................................................................................................................................................................................................................................................................

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

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

.........................206 Endorse .........................199 Hotkeys .....................................................................................................190 Numbering Documents/Pages........................................................207 OCR.......................................................................197 Tagging Records.........................................................187 Batch Updating .........................................................................................................................................191 Auto-Number Function ...........................195 Manually Numbering Pages ...............................201 Batch Updating .................................................................................................................................186 Default Field....................................................................199 Tagging Individual Records....................................................................................................................................186 Importing Data...........185 Multiple Documents ................................205 Document Numbering............................................................................................................................................................................185 Auto-Advance ..........................................................................................................................................................................................................................................LAW PreDiscovery User Guide Single Document.......................................................................................................................193 Document/Page Level Numbering ...........................191 Auto-Numbering .....................................................................................................................................................................201 Importing Tag Lists......................................................................................................................................................................................................................................................................................................................................................................................196 Finding Specific Page IDs .......................................................................................................................................................................................................................................................................205 Document and Page Counts ....................189 Batch Updating in the Index Display ............................................193 Document Level Attachment Numbering ....................................................................................................................................................193 Rolling Numeric Sections .............................................................................................................................206 Image Cleanup .....................................................................................................................................199 Tagging Multiple Records..191 Numbering during the Scan Process ...........200 Batch Tagging Options ..189 Batch Updating in the Grid Displays....................................................................................................................................................................................................................................................................................................................................................................................................203 Batch Processing Overview.193 Alpha-Numeric Numbering..............................................................................................................................185 Coding Options...................................186 List Field Options.............................................................................................................................................................................................................................................................................................................................................................................................................................207 10 ...............................................................................................................................................................196 Creating Tag Fields................................................................................................................................................................................................................

.............................................219 Checking the OCR Settings ....................................................................................................................................................................................................................................................................................210 Flagging Pages at Scan Time ..........................................................................................................217 Creating Searchable PDFs..................213 Language .....................................208 TIFF Conversion.............214 Auto-Rotate................................................................................................................217 Multiple Documents ........................................................................................................................217 Single Document..........................215 Retain Page Layout .....................208 OCR Overview ...........................................................................................................................................................................219 11 ......................................................................................................................................................................................215 Reset Text Index Status.....207 Scan for Suspect Footers ..............................................................215 Auto Deskew.....................................................................................................................213 Page Markers....................................211 Displaying Flagged Pages................................................................211 OCR Options ....................................213 Output Format......................................................................................................................................................................................................................................................................217 OCRing a Region ................................................................................................215 Create PDF Thumbnails ..........................................................................................................................................................................................LAW Licensing Print (Standard-Image Only) .................................................................................................................................................................................................................................................................................................................................................................................212 OCR Engine........................................................212 Available Options.........................................................................................................................................................................................................................................................210 Manually Flagging Pages .....209 Flagging Documents/Pages for OCR ........................215 Overwrite Existing Files ......207 E-Print (ED-Native Files) .............................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................210 Tracking OCR Status...............................................................................................................................................................................................................................................................................................................................................................................................................216 OCRing Documents..........................................................................................................................................212 Page Layout.........................................................................................208 Update Page Data ............................210 OcrFlag Field .................................................................................................................................................................................................................................................................................................................................215 Retain Pictures............210 OcrStatus Field ........................................................................................................................................................................217 OCRing...................209 OCR Indicator.......................................................................................213 Quality.................

................................226 Rip to PDF Before Printing .......232 Tracking Print Jobs in the Spooler ......................................................................................232 Supported File Types .........................................................................................................................................................................................................................224 Print Options........................................222 Auto-Incrementing Using Index Fields ........................................................................226 Limit Jobs in Print Queue ..........................241 Image Printer ..............................................................................................................................................................................................................................................226 Include Separator Pages....................................240 HTML ..........................................................................................................................................................................221 Setting Fonts..........................................................................239 Scaling.............................................238 Orientation .....................................................................................................................................................................................................................................................................................................227 E-Print/TIFF Output Settings ......................................226 Send Jobs in Batches.....................................223 Special Notes: .................................................................................................225 Auto-Size Paper .....................................................229 TIFF Output Options............................................................................................................................................................243 12 .............219 Exporting the Searchable PDF Files ....221 Setting Text.........................................................................................................................................................................221 Setting Border Size...........................................................................................................................229 Saving Defaults ...................................................226 Staple Documents .......228 Print Jobs ....225 Auto-Rotate Pages ....................................................................................................................................................................................................................................................................................................................................................................................................................................225 Do Not Print Annotations ......................................................................240 Field Replacements............................................................................................................................................................................................................................................240 Page Order .........................................................................................................................................................................................................................................................................................................................................................................................................227 Tracking Print Jobs in the Spooler ............................................................................................................................................................237 Excel ..............................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................239 Print ......................................................................LAW PreDiscovery User Guide Create PDF Thumbnails ......................................................................................223 Creating a Custom Watermark.............................................................................................233 Special File Type Notes.........................................................................................................................................................................................220 Header/Footer Options .......................................................................................................................222 Removing a Header/Footer .............................................222 Watermark ............228 E-Print Options ...............................................................................................................234 Acrobat .............................................................................................................................................................242 Passwords .............................236 E-Mail.................

.................................252 Initializing a Shared Batch...........................................................................................................................................................................................................................................................................252 Joining a Shared Batch ............263 Client Details ...........................................................................................................................................270 Cancelling Batches........................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................269 Application Settings ...............................................................................................................................................................................................................................................................................................................................261 Operation................................................253 LAW Management Console...........248 Header and Footer ............................................................................................................272 Deduplication Utility ..........................250 Options ......................255 Startup .............................................................................................................................................................................................................265 Job Details........................................................................................................278 External Deduplication Database .............................244 Word ....................................................................................279 Options ........................................................................................................275 Inter-Case Deduplication..............................................................................................................................................................................................................................................................................................251 Distributed Batch Processing........................................279 Member Cases ....................................280 Process Summary ....271 License Details .........................................................................................................................247 Separator Pages...................................................................................................................................................................................................................................................................255 LMC Overview ....................................................................................................................253 Deleting Shared Batches.......246 Field Replacements......................257 Initial Configuration of the LMC .............................................................................................................................................................................................250 Saving Default Settings .........................................................................270 License Overview ............246 Settings..............................................255 Configuration ................................................................................................................................267 Logs ................................................................259 Automatically Joining Shared Jobs ...............................................................................................................................................................................................................................................................................................249 Fields ....................................275 Settings Tab ..........................................................................................................................................................................................................................................273 Tools Tab.............................................................................................264 Job Overview....................................................................................273 Info Tab ...........................................................257 Creating a Shared Batch in LAW ..............280 13 .................................263 Client Overview .................................................279 Deduplication Process............................................................................................................................................................................................................LAW Licensing PowerPoint .......................................................................................................................................................................................................................................................................................

.308 14 ....................................................................................................................................................291 Export Profiles ...............................................................................................................................................300 Path Notation ...........................................................................................................................................................................................................................................................................................................................................................................283 Records Deduplicated Internally ...................................................................................................................................297 Format-Specific Settings.........................................................................................................................................................................................................299 Path Notation .306 DocuMatrix 1......................................................................................................................300 Other ........................................................................................................287 Retrieving the Case Deduplication Status...............................................301 Settings............................................................................................................281 Reviewing Duplicates .................................................300 Concordance ............................LAW PreDiscovery User Guide LAW Deduplication Fields .................................................................................................................................................................................................................................................................................................................................307 EDRM XML 1.................................................................................299 Other ...............................................................0.................................303 Delimited Text............................................................................................................................285 Deleted Records...................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................282 Duplicate Viewer ...........................5 .......................................................................281 Deduplication Mode.....303 Settings.............................................................................................................................................................293 Formats/Documents Tab ......................................................................................297 Formats ...................289 Image Format.................................................................................................................................................................................................................287 Export Utility Overview......................................................................................................299 Data Delimiters ........294 File Types .......................................................................................................................................................................299 CaseLogistix ...296 Document and Page Counts ..................................................................290 Supported Formats....................................................................................................................293 Creating Profiles .....................................................................294 Documents ........................................................................................................................................................................................................................................................................................299 CaseMap .............................293 Opening Saved Profiles............................................................................................................................................................301 Concordance Direct (DCB).............................290 Load File Extensions....................................................284 Records Deduplicated Externally .........................................................................................................

.................................................................................323 Image Tag Field..........................................................................................................................................329 Perform Duplicate Checks........................................................328 Advanced Tab ....317 Storm Viewer ............................................................................................................................................331 Case Summary ................................334 Reorganize Documents .............................312 JFS Litigator's Notebook ................................................................................310 IPRO IntelliVIEW ..............................................................................................................................................................................................333 Log Viewer.......................................................................................................................337 Find invalid records (missing images)........................................................................................................319 TrialDirector and Sanction....................................................................323 Options Tab ..........337 Find gaps in Page IDs.............................................................................................314 PDF Conversion ...............................321 Fields Tab ................................................326 Export Status .................................................................................................................................................................................................................................................................................................................................................330 Administration..................................318 Summation ..................................................................................................................................................................324 File Naming Scheme ...............................................................331 Compacting the Database..................................................................................................315 Ringtail Casebook ...........................................................................................................................................................................................................................................................................................336 Scanning for Errors ........................................................................................................................................................................................319 Settings..................................................................................................................................................................................................................................................................322 Selected Format ...............................................................316 Ringtail Format Notes..................................................................................310 General.................325 Folder Naming Scheme...............................................................................329 Creating CD Volumes ..............................................................337 Options ............................324 Output Path ..................................................................................................................................................309 Introspect eCM ..........................329 Perform Blank Value Checks ......................................................................322 Selecting Fields ............................................................................................................................325 Output Settings................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................338 15 .....................................................................................................................................................................337 Documents ..................................................................................................................................................................................................................................334 Reviewing Errors ..................................................................................................LAW Licensing iCONECT.......................................

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

.............................................................................364 Deduplication Reports....................376 Shortcut Keys..................................374 Attachments..369 Report Options ................................................................................................................369 Tally Report ..377 Function Keys............LAW Licensing Files By Type Summary Report Contents .............................................................371 Report Options ...........................................................................................379 About LexisNexis........................................................................................................................................................................................................................................................................................................................374 Actions...........................373 Deduplication Information ....................................................................................................................................................................................................................................................371 Tally Report Contents.....................................................................................................................................................................381 17 ..........379 Sales..........................................................................................................................377 Document List Keys........................366 Report Options ........................378 Contacting LexisNexis ...................................................................................................................................................................................................................................................................375 Unicode Support ....373 Fields ............................................................................374 (Partially Exclude) File Type Filter Action and Deduplicating..................................................................................................................379 Index......................................................................................................................................................................................................................................379 Training...........................................................................................................................................................................366 Page Properties Report .............................................................................................371 Appendix....................................................................................................................................................................................................................................................................................................373 Key Generation...377 Control Keys ...............369 Page Properties Report Contents .....................................................................................................................................................................................................................379 Technical Support.........................................................................................................................373 Scopes...................................................................................................................................................................................................................................................................................................................................................366 Deduplication Report Contents ...........................................................................

enter a password in the first field and then enter it again in the second field to confirm.Administrative Mode. ICESQL was used. click the Advanced button on the LAW Profile Manager dialog. making it easier to track and assign licenses. whether running locally or in a client/server configuration. If LAW is executed locally. The password is stored at a workstation level. start the LAW PreDiscovery Software from the program folder or from the shortcut icon on the desktop. create profiles. The password must be at least six characters in length and is case-sensitive. see "License Profile Manager . To change the password for a particular station. When the LAW Profile Manager (Administrative Mode) dialog appears. In the above example. click Tools > Change Administrative Password. referred to as the "License Server. meaning each computer on which LAW is launched. Note: If LAW is installed on a network and the program file. and identify the licenses currently available. 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. identify the licenses in use. Law50. To initially launch the Profile Manager after the installation of LAW. is shared. 18 . Enter the hostname of the computer to which the LAW dongle is physically attached." Specifying the License Server After starting LAW for the first time on a computer. the hostname needs to be entered for each workstation when the product is launched. For more information. the Change License Server dialog will appear. All licenses are maintained on one or more hardware dongles installed on a host computer. The LAW Profile Manager enables users to select licenses. and click OK. When the Enter Admin Password dialog appears. enter the new password in each field.LAW PreDiscovery User Guide LAW Licensing Profile Manager LAW uses a server-based licensing scheme. Note: A prompt for a password after clicking Advanced indicates that the user is not currently in administrative mode." Each workstation is then able to access the License Server through the network to "check out" available licenses for use on that individual workstation.exe. the hostname only needs to be entered once. a prompt to enter an administrative password will appear. will prompt for a password when executed initially.

Clicking OK opens the list of licenses. <Any Available Licenses> "Checks out" one of each available license.LAW Licensing Note: If a hardware key is not found on the specified server. Click OK after entering the hostname. Select the licenses needed for the session and click OK. If a key had been used successfully on the machine in the past. <Custom> Users can check out specific licenses based on their tasks. a message box will appear stating which licenses could not be acquired. a message will appear stating that the key was not found and will ask to try another server. ) will allow users to change the license server at any 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>. if a user needs to scan documents. The LAW Profile Manager will appear once a valid hostname has been entered. 19 . If one or more license modules cannot be checked out. If Yes is chosen. For example. Only the selected licenses will be checked out and available on that workstation. This message will not appear if the CD Publishing license could not be acquired. The button located to the right of the 'License Server' name ( time. the Profile Manager will still launch and then display the error after attempting to check out licenses. the Change License Server will appear once again and a new hostname will need to be specified. she can choose only the Scan license. Clicking OK starts LAW PreDiscovery Software. however. and was later removed. These licenses will not be available to other workstations using the same license key.

switch to administrative mode to enable it (File > Switch to Administrative Mode and enter the password). Click OK. Enter the administrative password and then click OK. click File > Switch to Administrative Mode. If selected as the default profile. Click OK to the "Success" message box that appears if the correct password was 20 . Enter the name of the profile and. The Add New Profile dialog appears. optionally. Then clear the check box Prompt for profile when starting LAW in the LAW Profile Manager dialog box. If the Add button is grayed out. Select the licenses to include in the profile. These profiles may be hidden to prevent other users from checking out more licenses than needed for the current LAW session. To set this as the default profile for the current user. The section in the INI file containing this setting is in the following format: [<user name>]. select Default Profile. The new license profile is displayed in the LAW Profile Manager dialog box.ini file in <application path>\ProfMan. select the profile as the default profile. Hiding System Profiles Two system profiles are displayed by default in the LAW Profile Manager: <Any Available Licenses> and <Custom>. To hide a system profile.LAW PreDiscovery User Guide Creating Custom Profiles Click Add on the initial LAW Profile Manager dialog to create a custom profile. To re-enable this setting. Tip: To automatically check out licenses and bypass the LAW Profile Manager. set Prompt=1 in the profman. a description. it is automatically highlighted.

such as creating profiles and reclaiming undocked keys (see Undocked Keys section). system or user-defined. This is one method of switching to administrative mode. click the Advanced button. The profile will no longer be visible. Switching to administrative mode allows users to perform the following tasks: Add. At least one profile. right-click anywhere in the profile selection area and choose Restore Hidden Profiles. In addition. Right-click the desired system profile in the LAW Profile Manager dialog box and choose Hide System Profile. Once the password is entered. must be visible at all times. 21 . After launching the Profile Manager. select File > Switch to Administrative Mode and enter the administrator password. any feature requiring an administrator password prompts the user for the password. If this is the first time switching to administrative mode on the current computer. 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. To restore the hidden profiles.Administrative Mode Switching to administrative mode in the Profile Manager will allow users access to a number of features. The LAW Profile Manager (Administrative Mode) dialog appears. please see the "Creating and Changing Passwords" section in this topic.LAW Licensing entered. the Profile Manager is switched to administrative mode. edit. Profile Manager .

and refresh the license counts when new licenses have been purchased and added to the existing server key. they will be displayed below the server key's serial number. 7. Licenses that do not exist on the key will be grayed out. Profiles: Lists all profiles stored on the current machine as well as the two default license selection methods. If any undocked keys currently exist. and concurrent user counts (see next section). 5. License Servers: Lists the current license server. Profile: Allows users to add. In Use: Displays the number of licenses in use for each type of license. host name. 2. the right pane will display the name. If the server key enumeration option is enabled. including its IP address. 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. 4. Menu Bar: Contains the following: File: Provides options to refresh profiles and license servers for viewing the most updated information. 3. and licenses stored in that particular profile. edit. When a profile is selected. and delete profiles as well as the set the desired profile as the default. manage undocked keys. Free: Displays the number of available licenses for each type of license. 6. License: Lists each type of LAW license. Server Key: Allows users to change the license server.LAW PreDiscovery User Guide 1. description. all other server keys on the network will be displayed here as well. Tools: Contains options to change the Admin password as well as enable server key enumeration. Total: Displays the total number of each particular license on the current server key. 22 .

Adding New LAW Licenses to an Existing Server Key When additional licenses are purchased for LAW. if a key contains 10 concurrent user licenses. See the Contacting LexisNexis section to find contact information for the Sales department. Once a LexisNexis representative has updated the license counts to reflect the newly purchased licenses. These two numbers reflect concurrent user license counts. the current license server key's serial number is listed with two numbers in parentheses beside it. they will be added to the user's existing LAW server key. licenses can be checked out and released from within the LAW application. The key will be updated with the new license counts. The first number indicates the number of concurrent licenses in use. with any combination of licenses. at the same time.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. For example. For example. while the second number indicates the total number of concurrent licenses contained on the server key. In the License Servers tree (#3 above). 23 . additional licenses may be purchased individually. and 3 workstations are currently logged into LAW. If more are needed. The amount of concurrent user licenses currently owned by a company will depend on a number of factors. then 7 concurrent user licenses will be available at that time. the user will need to launch the Profile Manager and click File > Refresh License(s) from Internet (must be in administrative mode first). Click Help > About LAW > Licenses to launch the License Information dialog. (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). Acquiring or Releasing Licenses in LAW To avoid closing LAW and launching the Profile Manager in order to change the selection of license modules.

Note: This feature will be disabled when an undocked key or temp license is used or while running LAW in demo mode. At least one license must remain checked out while LAW is running. deselect the box beside the license module name (no message will appear when releasing licenses). if the OCR license is released. the serial number of the key(s). Licenses in use by the current workstation will have check marks in the boxes beside them in the "Licenses" section of this dialog. To release a license. and expiration date(s) (if applicable).LAW PreDiscovery User Guide The "Active Key" section of this dialog will display the license server name. A message box will appear indicating whether or not the license acquisition was successful. check the box beside the license module name in the list. To acquire a license. OCR Add-on (PDF) will be automatically released as well as it is dependent on the OCR license. 24 . Also.

you will not be prompted for a password. click the Advanced button and enter the administrator password. and expiration date.0 and Z-Print keys that have been upgraded to LAW 5. specify the length of time the licenses will be checked out. When one or more undocked keys have been created. the user simply returns the licenses to the server key. If an undocked key with licenses is found. Then click Server Key > Create Undocked Key. Creating Undocked Keys Attach an undocked key to any LAW station that has access to the server key. Undocked keys can also be created from the LAW Profile Manager (Administrative Mode) dialog box. Click this item to view the key's serial number. If this method is used. The Profile Manager searches for a key attached to the local computer. undocked keys can be purchased from LexisNexis. click the LAW server key below "License Servers" in the left pane. The undocked key now contains the selected licenses and is ready for use. select File > Switch to Administrative Mode and enter the administrator password.exe in the Law50\Profman folder). Undocked keys can also be managed from the LAW Profile Manager (Administrative Mode) dialog box. Note: Server keys can not be used as undocked keys. This feature is useful for completing on-site scanning projects. The link in this pane is used to "Reclaim Undocked Key(s)". Note: An Internet connection is required in order to create an undocked key. Launch the LAW Profile Manager. When the LAW Profile Manager dialog appears. To open this dialog box. as explained in the next section. Scan. an "Undocked Keys" entry is listed under the server key. Admin. Select the licenses to be "checked out" from the server key and placed on the undocked key. Please see the Contacting LexisNexis topic for the Sales department contact information. To open this dialog box. Next. If you are already in administrative mode. 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.e. click 25 . Once in administrative mode. The Select License(s) dialog appears. One concurrent user license is taken from the server key for each undocked key created. Obtaining Undocked Keys LAW 4.0 and later can be used as undocked keys. select File > Switch to Administrative Mode and enter the administrator password. first attach the undocked key to a LAW station. LAW attempts to locate any expired undocked keys not attached to the computer and prompts the user to reclaim the licenses. Launch the LAW Profile Manager on that station by double-clicking the LAW shortcut (or by double-clicking the profman. When the licenses are ready to be returned. select File > Undocked Key Admin > Create Undocked Key. for example. LAW reclaims all licenses on the undocked key and returns them to the server key. Follow the steps in the previous paragraph to create the key. Edit\QC) from the dongle on the license server. and pull those licenses to the undocked key or keys. There will be no other use for these keys once the upgrade process has been completed.LAW Licensing Undocked Keys Licenses can be "checked out" from the LAW dongle and placed on other dongles (referred to as "undocked keys"). Next. check-out date. allowing other LAW users to access them once again. A user can choose one or more licenses (i. With the undocked key attached.. Or right-click the server key and select Create Undocked Key. select an expiration date.0/Z-Print hardware keys. click the Advanced button and enter the administrator password. 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. If an undocked key is not attached. With the undocked key attached. Reclaiming Undocked Keys To return the licenses on the undocked key to the server key prior to the expiration date specified during creation. select File > Undocked Key Admin > Reclaim Undocked Key(s). If users do not possess 4.

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. Then click Server Key > Reclaim Undocked Key(s).LAW PreDiscovery User Guide the LAW server key below "License Servers" in the left pane. 26 .

except Scan-related (Replace and Insert New Page) Create/delete folders Code index fields Search. compact database. 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 . validate ranges. view properties of a page. print single documents (image records) to paper. 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. reorganize case. launch both grid displays. view reports. utilize the View and Help menus. rotate pages. navigate pages of documents.LAW Licensing Licenses Defined Each license module will allow LAW users to perform certain functions within the software. filter. All licenses will allow users to open a case. access the Run Command feature. Admin (Import/Export) Create cases Modify/create index fields Import/export (minus ED Loader imports) Perform administrative functions (case summary. scan for errors. 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. and access the Tools->Options dialog. group.

LAW PreDiscovery User Guide 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. 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. 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. including Insert and Replace) Create/delete folders Number documents Clean up images Reset OCR flags 28 . Japanese. extracted.

see the LAWtsi product sheet.LAW Licensing TSI Scan Allows scanning to a LAW case using LAWtsi (touch screen interface). 29 . For more information.

a case must first be created or opened. select New Case from the File menu or press the New Case button on the main form toolbar. This activates the browse dialog. If Yes is selected. Creating Cases To create a new case. allowing the user to select a new case list. LAW stores information about these cases in the case list database (caselist. (SQL Express is a free version of SQL with a limitation of 4 GB total database size. Instructions for installing and configuring ADS cases may be obtained by contacting Technical Support. 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. This allows users to share the same case list among multiple stations. browse to an existing case list. 31 . the user will be prompted to browse to an existing case list file. all other stations will see those changes. By default.Properties dialog will appear. so that when one station adds or removes a case. If the case list file is not found the first time a user attempts to access the case list. the following New Case . Microsoft Access does not need to be installed on a machine in order to create an Access case in LAW. see Configuring LAW and SQL.mdb). Select the desired database type for the new case and click OK.) For instructions on enabling SQL support. Once the desired database type has been selected. ADS (Advantage Database Server). LAW currently supports three possible database types for creating a new case: Microsoft Access.Creating a New Case Creating a New Case Before users can begin working in LAW. To change the case list at a later time after one has already been selected. and SQL Server/SQL Express. The purchase and configuration of ADS and/or SQL Server is required before these two database types may be used with LAW. MS Access is the database type shipped with new LAW installations. The Select Database Engine dialog will appear. the case list is stored in the same directory as the LAW executable. Selecting No will automatically create a new case list. press <CTRL+B> from the case list form.

click the Edit List button to launch the Project Administration dialog. It is acceptable to select a different location for the database versus the images.g. select the Enable Electronic Discovery for this case option. If the case will contain electronic discovery data. client or project names may be associated with LAW cases. leaving the default paths intact for future case creation. LAW will automatically create the system fields and supporting database tables necessary for processing electronic discovery using the Electronic Discovery Loader. change the path information in the Case Paths section on the New Case . The default paths may be modified by clicking the Options button and entering the desired paths. To override the default paths for a particular case. client or project name. The "Client or Project Name" feature is discussed in the next section. From the New Case Properties dialog.. This feature is useful for grouping cases when data for a single project is separated into multiple cases. and the path where the database and images will be stored.Properties dialog allows users to specify the name of the case. See Case Templates for more information. case template.Properties dialog. These paths will be applied automatically when creating a new case.Properties dialog box allows users to modify the default paths for databases and images. The New Case . Creating Projects As mentioned in the previous section. When this feature is enabled. 32 . The Case Name must be unique and must adhere to typical file name restrictions (e. A case template will store user-defined index fields and folder structures (optional). case description. cannot contain ? / \).LAW PreDiscovery User Guide The New Case . The case will be stored in the new location. The Case Template drop-down allows users to select a previously created template.

33 . Enter the client or project name for the case in the Project Name field. click the Edit List button located beside the Client or Project Name option in the New Case . Click OK.Properties dialog. Choose the project from the Client or Project Name drop-down list. The Project Administration dialog will appear. Click the OK button to continue.Working With Cases Click the New Project button to launch the New Project dialog. The Project Description is not required but may be helpful for future identification. Make the desired changes to the Project Name and/or Project Description and click OK. Click the project to be edited and click the Edit button. Editing Projects To edit a project name or description. The new project will be added to the list in the Project Administration dialog. The activation setting will default to Active.

LAW PreDiscovery User Guide Deleting Projects To delete a project. 34 . Click the project to be deleted and click the Delete Project button. click the Edit List button located beside the Client or Project Name option in the New Case Properties dialog. Any LAW cases that were previously associated with this project name will display as <none>.

click the case name in any tab of the Open Case dialog and click Properties.Working With Cases Working with Existing Cases Once cases have been created. and utilize the Project/Client View to group cases that are part of the same project (for example). select File > Open Case or click the open folder icon on the main toolbar. and All Cases. which displays three tabs: Recent Cases. All Cases: This tab will display all cases regardless of their state. As letters or numbers are entered into the adjacent box. allowing users to search for a case by either the case name or by the creation date. Opening Cases To open a case in LAW. Click the 'No' radio button beside the 'Case is Active' option and click OK. A case is set as 'Active' automatically when the case is initially created. To set a case as 'Inactive'. The case will no longer appear in the Active Cases tab but will be accessible from the Recent Cases and/or All Cases tabs. To utilize the Search feature.Properties dialog will appear. view and edit case properties. Recent Cases: This tab displays the last ten cases that were opened in LAW. 35 . the cases that correspond to those beginning characters will appear in the list. the Open Case dialog may be used to launch or search for cases. Active Cases: This tab displays all LAW cases that are in an 'Active' state. Active Cases. This will activate the Open Case dialog. The All Cases tab includes searching capabilities. delete cases from the case list. first select the desired search method: CaseName or DateCreated. The New Case .

Once completed. right-click and select Delete from the pop-up menu (or select the case and click Delete from List). If the case is already in the current case list.LAW PreDiscovery User Guide Cases may also be opened using a command-line parameter with the case name.exe" LAW Demo Case. the case will be opened and added to the case list. client or project name.Properties dialog box can be displayed by pressing the Properties button from the Open Case dialog after highlighting the desired case. Viewing Case Properties The New Case .ini) of the desired case.mdb. select the desired case. If browsing to a case which conflicts with an existing case name. Setting a case to the inactive state will result in that case not appearing in the Active Cases tab in the Open Case dialog. modify the shortcut or call the following command: "C:\Program Files\Law50\Law50. 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. simply browse to it from the case list form. or project. This allows users to view the database and image paths for a case. press the Browse button from the case list form and select the project database or ini file (project. It does not remove any data or image files for that case. the user will be prompted to enter a new case name. 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). If a user needs to work on the case at a later time. Note: The path to the exe will require quotes if it contains spaces and is a Windows shortcut or command prompt launch. Deleting a Case To delete a case from the case list. 36 . To browse to a case.add. For example. to open LAW to a case called LAW Demo Case. and modify them if necessary. Browsing to a Case If a user needs to open a case that already exists but is not in the case list. case description. simply browse to the case database to re-add it to the case list. project. Note: Deleting a case from the case list merely removes the reference to the case in the Open Case dialog. a message will appear stating that the case is already in the list.

See Case Templates. 4. 7. 6. and "Enable Electronic Discovery for this case" is selected from the New Case Properties dialog. To open this form. The index information for each record is displayed on the Index display on the main form to the right of the main image window. 8. 2. 3. Edit List: Launches the List Editor to allow editing of list field values. See Case Templates. Field Profiles: Click the arrow to view a list of active profiles. and save a new profile. Add Field: Launches Add Field dialog. Fields shown in black are user-defined fields. For example. the index fields necessary for processing electronic discovery will be created automatically. Name: Displays names of system and user-defined fields. 5. Save Template: Saves a case template based on the current LAW case. displaying all system and user-defined (if any) index fields. When a new case is created. users can enter folder level index information when scanning images or tag relevant documents when processing EDD. 37 . 1. select Index > Modify Fields from the main form. Save Changes: Saves changes after editing field properties. The Modify Fields form is used to add. The Modify Fields dialog will appear. Users may add as many or few index fields as deemed necessary to produce meaningful search results. This information aids in retrieving records from within LAW and. and update existing fields. once exported.Working With Cases Creating Index Fields Index fields are used to store information about the records in a LAW case. LAW will support nearly an unlimited number of user-defined index fields in each case. delete. launch the Manage Field Profiles dialog. within the litigation support applications. Fields shown in gray are system fields and cannot be deleted or edited. Delete Field: Deletes a user-defined index field. Creating index fields is one of the first things users typically do after creating a new case. Apply Template: Applies an existing case template. See the Index Profiles topic for more information.

Type: Lists the type of field (see Field Types below). 11. 38 . Users can choose to have an index created for the field by checking the Indexed option.** 20. Indexed fields provide much faster sorts and search results from within LAW. Because indexed fields take up more space than non-indexed fields and slow down the insertion of new records. Save: Saves any changes made to the active field profile.LAW PreDiscovery User Guide 9.** **See the Index Profiles topic for more information.** 18. 10. The Default profile cannot be deleted. All system fields will be locked. meaning values in this field must be unique for each record. Unique: Indicates if a field is set to unique. Table: Indicates if a field is contained in the document-level or page-level table of the database. Locked: Indicates if a field is locked. 15. 12. Field Order: Displays the order of fields in the Index display. 17. Save As: Deletes a user-defined Index profile. The Table option allows users to select either Document-Level or Page-Level. Documentlevel field values will be the same for all pages of a document. which are discussed below in the Field Types section. Adding a Field To create a new field. meaning they cannot be edited.** 19. Page-level field values will apply to only the selected page. Unless a field will be queried or sorted frequently or will contain unique values. Select the field type from the list of available types. click the Add Field button. The Add Field dialog will appear. be careful not to overuse indexes within the LAW cases. Indexed: Indicates if a field is indexed. 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. Enter a name for the field. Active Profile: Displays the name of the profile currently applied in the Index display. no reason exists to add indexes for the fields. Row Span: Indicates how many rows of data will be visible in the Index display (Memo fields only). If a field is indexed. Delete: Deletes the profile currently selected in the Active Profile field. 14. the Unique option may also be selected to ensure that the field will contain no duplicate values. although this has no effect on the final retrieval application. Visible: Indicates if the field is visible on the Index display. 16. to be used for storing field order and visibility. 13.

simply click (and hold) the field in the Field Order pane. For example. 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. LAW reserves many field names. click and drag the fields to the new location and release the left mouse button. When viewed in the Index display. mm/dd/yyyy). change the desired properties (i. The list values can be modified by selecting the Edit List button once a list field has been selected from the fields list.) Numeric: Accepts numeric values between the values of -2147483647 and 2147483648. field type.e. the field will be added to the bottom of the list. For a complete list of system fields used by LAW and their descriptions. indexed) and select Save Changes. Right-click anywhere within the Field Order pane to view the three pop-up menu options. which can contain up to 255 text characters. Tag (Boolean): This field will have one of two states (Yes/No). Tag. The fields will be re-ordered on the Index display after closing the Modify Fields dialog.e.Numeric. use the Ctrl or Shift key to select multiple fields. please see the Field Descriptions topic. Certain field type conversions may cause a loss of data. select the field from the field list. Changing Field Properties To change the properties of a field once it has been added. The Span Height setting adjusts the number of rows displayed on the main form. and 'drop' the field (release the left mouse button). "Yes" is represented by a green check mark in the grid displays. a unique index cannot be added to an existing field if that field does not contain all unique values. To move a field to a different location. which appear in a drop-down list for the field on the index tab. select the desired field from the field list and click Delete. 39 . but allows entry of pre-specified values. name. except it will automatically increment from one document to the next if no value is specified. Auto-Increment: Same as text field. List: Same as text field. To move more than one field simultaneously. and Text. Page-level fields are limited to three field types . Deleting a Field To delete an existing field. or any other name that already exists. To add a field to this pane. Deleting a field permanently removes that field and all data in it from the database. drag it to the desired location. The Field Order pane may also be used to hide or show fields. Date: Date field. Also.Working With Cases Field Types The following seven field types are available when creating new fields for document-level fields. simply check the 'Visible' box for the desired field. While holding one of these keys. Memo: Field type used for large text field values that exceed 255 characters. which requires entry of a valid date format with a 4-digit year (i. the user will not be allowed to proceed with creating the new field. (Note: Memo fields cannot be indexed. 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. System fields (displayed in gray in the Modify Fields dialog) cannot be deleted. the field will contain the two values in a drop-down list: Yes and No. See the Tagging Records section for more information. Text: Standard text field. If one of the reserved field names is entered.

this option displays all userdefined fields in the current LAW case. Show All Fields (User-defined): Leaving currently displayed fields intact. 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.LAW PreDiscovery User Guide Hide Selected Fields: Hides any fields selected in the Field Order pane. Show All Fields: Displays all system and user-defined fields existing in the current case. 40 .

Note: The Admin LAW license is required to save a case template. Enable the "Save Folder Structure with Template" option to save the current folder structure and field information of the case. The second method is to apply a template to an existing case via the Modify Fields dialog or File>Administration menu. 41 .Properties form. The templates are stored as <Template Name>. the template will consist of field information and only the folders located one level below the root. Saving a Case Template Two methods exist for accessing the "Save Case Template" feature. Click Index > Modify Fields and click Save Template. a subdirectory of the folder containing the LAW executable. New Case A Case Template field appears on the New Case . any folders within these folders will be ignored. If "Top level folders (ONLY)" is selected. Use the instructions above to save a template.XML. The drop-down will display all templates contained within the Templates folder (see above). The second method of accessing this feature is via the Modify Fields dialog. 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. Applying a Case Template Two methods exist for applying a case template. Case templates are automatically placed in a Templates folder. This feature can be used to reduce the amount of time required to set up the same fields or folder structure multiple times.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. The first method of accessing this feature is to select File > Administration > Save Case Template. The first method is to apply the case template at the time of case creation. The Save Case Template dialog (pictured above) will appear.

The Select Case Template dialog will appear and prompt the user to select a template.LAW PreDiscovery User Guide Existing Case Templates may also be applied to an existing case using the feature under File > Administration > Apply Case Template. Choose the desired XML file and click Open. 42 .

EDFolder. EDSource. An alternate method of applying a case template exists in the Modify Fields dialog.Working With Cases A prompt will appear. Note: The EDD lookup fields (Custodian. 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. Select Yes to proceed. Click Index > Modify Fields and click the Apply Template button. 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. Follow the instructions above to apply the template. 43 . Any field names that are duplicates of existing fields will be ignored. listing the fields that will be added to the case.

If this option is enabled and a value is typed directly into a list field on the Index display. select the desired item from the list. The Add button is disabled if the current item matches the selected item or is blank. To launch the List Editor. Highlight a list field and click the Edit List button. Adding List Items To add an entry. Renaming List Items To rename an existing list item. the value will be added to the list after clicking Update (if it is not already in the list). The Edit List button is only enabled for fields defined as 'List' types. List items may also be added automatically when coding documents from the main form. enable the 'Add all new list field values to list on update' option located on the Preferences tab of the Tools > Options form. select the desired item from the List Items pane and click Delete. To utilize this feature. The item will be added to the list. select Index > Modify Fields from the main form. type the value into the 'Current Item' text box and click Add. Deleting List Items To remove a list item.LAW PreDiscovery User Guide 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. This action updates the name of the current item provided the new name does not already exist in the list. and then click the Update button. enter the new name in the Current Item text box. The name of the field being edited is listed just below the title bar. unless it already exists. The selected item will be removed from the current list. 44 .

These list files can be created by exporting from LAW's List Editor or created manually with any text editor. while the Export function is used to save the current items to a list file for future use.Working With Cases Importing and Exporting List Values List items may be reused by exporting to and importing from list files. The Import function is used to import existing entries from a list file. 45 . A list file is simply a text file (with an "LST" extension) that contains list items (without quotes) separated by hard returns. eliminating the need to re-enter list items for common fields by allowing users to share list items between cases.

Changes may be made to the Default profile in a case. electronic discovery) or the type of process currently being performed or QC'd. In e-discovery-enabled cases. The profiles will store a list of visible fields and the order of those fields in an .. a number of popular EDD-related fields are displayed in the Index view automatically when the Default profile is selected. but the changes will not persist to the Default in other existing or new cases.ifp file. scanned documents vs. make the desired fields visible.LAW PreDiscovery User Guide Index Profiles Depending on the type of project (i. if documents are being scanned and five fields must be coded at scan time. no fields are displayed by default. In non-EDD cases. click Index > Modify Fields. and organize them as needed in the Field Order area. click the Save As button at the bottom of the dialog or click the arrow beside the Field Profiles button and choose Save As. Next. 46 . Creating Index Profiles To save a field profile. A "Default" profile is a user-level profile included by default in each LAW case. 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.e. For example. certain fields may be needed for reviewing or coding more often than others.

Changing this path will affect saved global queries. while global profiles are stored in <application path>\Shared. If a profile is shared.Available to the current user in the current case. LAW will automatically display "(Shared)" after the profile name.08 and below used a different storage scheme for index profiles.ifp profile storage file will be named according to the value entered in this dialog.3.Available to any user in any LAW case.Available to any user in the LAW case in which the profile was created. The default storage location for global profiles can be changed via the Preferences tab in Tools > Options. Global . All profiles were stored in a single INI file. The name must be a valid file name. LAW will automatically display "(Global)" after the profile name. the profiles will be copied from this 47 . When 5. and global grid profiles.3. and filters option to select a new storage location. The user and shared profiles are stored in the case folder structure ($UserData). After the storage level has been selected. Click Accept to save the changes.Working With Cases Three storage levels are available when creating field profiles: User . If a profile is global. Click the Browse button beside the Path for global field profiles. 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. global index field profiles. Shared . enter a name for the profile. Note: Versions 5. grid views.14 or later is installed and a case is opened. as the .

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. Profiles can be created.ini file and updated to match the new storage schema.LAW PreDiscovery User Guide indexprof. and deleted from this dialog. applied. New profiles can also be created by launching the Manage Profiles dialog. Applying and Modifying Index Profiles Once created. 48 . available by clicking the arrow beside the Field Profiles button in the Modify Fields dialog. The previous "Default" profile will be named "Default_Shared" to avoid conflict with the new Default profile in the current case.

click Index > Modify Fields. open the Modify Fields dialog and make the desired changes to the visible fields and/or field order. If the Save button is not clicked. LAW will prompt to save changes prior to closing the dialog. then click the Save button. select the profile to be deleted in the Active Profile drop-down. Deleting Index Profiles To delete a profile.Working With Cases To modify an existing profile. 49 . select the profile to be deleted from the Field Profiles list and choose Edit > Delete or rightclick and choose Delete. Profiles can also be deleted by clicking the arrow beside the Field Profiles button and choosing Manage Profiles. Choose Yes to proceed with the deletion. Once the dialog appears. and then click the Delete button. A confirmation prompt will appear to confirm the user wishes to delete that particular profile.

however. click the minus sign. The folder "Number" and "Type" are combined to form the actual folder name. allowing organization by media type or custodian. the records will appear in the document list when clicking on the original folder structure created by the ED Loader during 50 . click the plus sign to the left of the folder name. LAW provides a set of pre-defined folder suffixes to quickly create a folder structure. choose Folder > Expand. The files referenced in the document list are not necessarily physically stored in the folders shown in the folder tree. simply edit the "Folder Name" text box directly. The folder structure is also useful for EDD projects. Folders cannot be auto-created while the root image folder is selected. LAW creates "C:\Case1\0001Box\0002Fldr" and makes that the current folder. Displaying the records in this manner will allow the desired representation of folders and records to be maintained. To collapse all folders below the selected folder. Note: Selecting a folder type will reset the folder name to the contents of the folder number and type. 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. The Auto-Create feature automatically creates the next logical folder on the same level as the current folder. Auto-Creating Folders LAW also provides a quick and easy method for creating a series of folders. folders created via TIFF conversion in LAW are stored in <case root>\$Image Archive. as this would create a folder outside of the root case folder. To collapse. choose Folder > Collapse. If the next logical folder already exists. 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. The New Folder dialog will appear. but users are free to customize the folder names as needed. i. The new folder will be created as a subfolder of the currently selected folder. The next folder is created on the same level as the current one. select the parent of that folder prior to adding the new folder. To expand a folder containing subfolders by one level. one important item to note is that the folder structure generally determines the order of processing. Creating Folders To create a new folder. Click OK to create the folder. For example. LAW will simply jump to that folder and make it the current folder. To expand a folder and all subfolders below the selected folder. For example.LAW PreDiscovery User Guide 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. if currently in "C:\Case1\0001Box\0001Fldr" and Auto-Create is selected. folders are processed in alphabetical order. select Folder > New from the main menu. If the user wishes to customize the folder name.e. 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). This helps scanner operators find their place in the case more easily and aids in finding and correcting scan errors. for example. When naming folders. To create a new folder on the same level as the current folder.

or right-click the folder and choose Move. If this error occurs (due to excessive file locks). To move a folder. Renaming Folders To rename a folder. Similarly. 002Source. The root case folder cannot be renamed. the user would like to put the 005Source folder at the same level as 001Source. All subfolders and records contained in the folder will be moved to the new location as well. click on the folder to be moved in the main interface folder tree and click Folder > Move. the root case folder cannot be deleted from within LAW. When a folder is renamed. ? / \).000). To prevent accidental deletion of an entire folder tree. all subfolders of that folder must first be deleted. 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.Working With Cases import. This screen will display the same folder structure as the tree in the main interface. a setting in the registry can be adjusted to allow the renaming of the folder to proceed. 003Source. This process can take some time if the folder is near the top of the case. 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. The folder name must not contain any characters that the operating system cannot support (i. In the example above. depending on the number of documents affected by the name change. Deleting Folders To delete a folder. The renaming of a folder may actually cause an error and fail if too many documents are affected (usually over 10. See the topic related to the type of function being performed in order to see how the associated files are stored. select the folder to be renamed and then select Rename from the Folder menu. and 51 . Contact LexisNexis for specific details if this occurs. the path for all documents in and below that folder must be updated to reflect the name change. select the desired folder and select Delete from the Folder menu. The Move Folder dialog will appear.e.

52 . Another option is to utilize the Case Summary feature by clicking File > Administration > Case Summary.LAW PreDiscovery User Guide 004Source. Summarize Images LAW provides a quick summary of the images contained within a folder and subfolders (recursively). which takes an additional amount of time. This process may take longer to complete for folders containing a large number of documents. Once the destination folder has been chosen. in addition the number of scanned images. Note: To calculate the square footage of the documents. To do this. select Tools > Summary to view the document and page totals. As noted in the message box (ED-enabled cases only). The folder will be moved to the designated location. size. and number of files and subfolders within it. electronic files and their printed images are skipped during this image summary process. For a faster document or page count. Then. the user would select 43695_MoveFolders01 as the destination folder. The total area information can be very useful for billing purposes. The image summary displays a report of the number of documents and pages contained within the selected folder. 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). The size and number of files displayed will include all files in and below the current folder. click Accept. LAW must open and read each image individually. LAW also calculates the "Total Area" of the documents contained within the folder. Folder Properties LAW provides a means to get a quick summary of a folder that includes the actual location. To view the folder properties for a specific folder. use the Query Builder or Grid View to create a query on the selected folder. The number of skipped records will be listed in the summary output. click the desired folder and select Properties from the Folder menu.

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

To customize the label. Default Target Folder The location of imported electronic discovery documents will be based on the specified target folder. If typing a target folder value directly into the 'Default target folder' text box. To specify a value in the Default Custodian field. The same custodian may be applied to all sources by entering the custodian value into the 'Default custodian' field. 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. the session label will contain the date and time that the session was initialized. This label may be useful for filtering specific sessions or researching session logs. users may create a new folder or select an existing folder for the imported documents. 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). this field will be populated with the currently selected folder (the root case folder is displayed as "<Case Root>). These options may be set either before or after selecting the sources to be loaded into the LAW case. 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 . click the button beside this option to launch the Session Label Editor. 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. 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). In this dialog. Session Label The Session Label allows users to assign a unique identifier to each ED Loader session for a LAW case. Default Custodian Users may assign custodians to one or more sources prior to importing the electronic documents. and that folder does not currently exist in the case. LAW will create it prior to import. When the ED Loader is launched in a LAW case.LAW PreDiscovery User Guide Session Configuration The Sources tab of the Electronic Discovery Loader includes four settings that should be configured prior to each ED Loader session. By default.

users should force each workstation to use unique numbering schemes (i. Type a value into the Current text box and then click Add to add a custodian.e. A list file is simply a text file (with an "LST" extension) that contains the custodian names (without quotes) separated by hard returns. Enter the starting value in the 'DocID Seed' field. 55 .Acquiring Documents The Custodian Manager dialog allows users to enter one or more custodians. PC1_000001. To ensure the DocID is unique to each record when loading from multiple workstations. the number will increment by one for each record. PC2_000001. similar to adding list items for list type fields in LAW (see Populating List Items). A list of custodians may be imported by clicking the Import button and browsing to a list file.). Repeat these steps to enter multiple custodians. DocID Seed The DocID is a unique identifier assigned to each document imported into LAW via the ED Loader. etc. Click Export from the Custodian Manager to create a list file containing any currently existing custodian values. The DocID value's length must not exceed 50 characters.

The 'Scan selection(s) for mailstores' option. if the file list contains a listing of EDOCS\0001. Check the 'Recurse Subfolders' option to ensure the subfolders of selected folders are processed as well. File List . 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). Outlook folders. Outlook Fldr. 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. folders. File(s) .Click this button to launch the Select File(s) dialog. check the box or boxes next to the folder(s) to be processed.xls.Click this button to launch the Select Folder(s) dialog." The Sources tab of the ED Loader will be used to add these sources to the 'Source Queue'.PST) mail stores as well as Lotus Notes (*. For example. Click Accept to add the selected folder(s) to the queue. These different types of sources may be processed in a single ED Loader session. Mail Store . and/or file lists. 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. they will be listed separately in the queue and processed as mail stores.LAW PreDiscovery User Guide Adding/Removing Sources Folders and files selected for import via the ED Loader are referred to as "sources. then the file list should be placed one level above the EDOCS folder. Documents may be added to the Source Queue by selecting individual files. . will search any selected folders for supported mail stores.Click this button to select one or more Outlook folders for import. The file list should be a text file (file extension does not matter) containing full paths to the files. Folder(s) . The mail store(s) containing the folders to be processed must be opened in Outlook prior to using this option. See the Exclusions topic for more information. when enabled. and without quotes. mail stores.NSF) mail stores. the file list must be placed in a location that will allow the ED Loader to complete the path. The store(s) will be added to the Source Queue. When the Select Outlook Folder(s) dialog appears. 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. Check the box or boxes next to the folder(s) to be processed. If any stores are found. When the Select Mail Store dialog appears. Buttons are available for choosing any of the five different types of sources. which is located just below the session configuration options. and mail stores are contained in the selected folders. Browse to the file containing the file paths and click Open to add the source to the queue. LAW currently supports Outlook (*.Click this button to launch the Select File List dialog. If this option is disabled.Click this button to add mail store sources. If the file contains relative paths. Check the "Recurse Subfolders" option to ensure the subfolders of selected folders are processed. separated by hard returns. 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. 56 . simply browse to the mail store(s) and click <Open>.

This option has two sub-options. then clicking and dragging the items into the queue.Used to remove one source at a time. ensure the "Automatically set E-Doc folder sources to Recurse when I add them via drag and drop" option is enabled. 'Scan supported archives' will result in archives (i. the files will be processed as mail stores rather than e-docs. '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. A warning will be logged in the Session Viewer logs when this occurs. both located in the General category on the Settings tab (see the General section). all filenames will be displayed. 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. Click the source in the queue that needs to be removed and click Remove Item to remove it.. 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. Viewing Sources To review information about each source selected for processing. Remove Item . to ensure subfolders of the selected folders are processed. if a folder is selected that contains 5 XLS files and 1 PST mail store.e. and mail stores may all be added using this method by simply browsing to the sources through the operating system (i. First. 57 .Used to remove all sources from the queue.Acquiring Documents Drag and Drop Method Another method of adding sources is to drag and drop items directly into the Source Queue. If the source consists of a file set or file list. click the View Details button located between the Add and Remove sections on the Sources tab. Folders. You can also select Source Details from the View menu. using Windows Explorer). Clear All . Long Paths When sources are selected with paths greater than 260 characters in length (the Windows limit).. If found. highlighting the desired folders and/or files. zip or rar) being scanned for mail stores as well. There are two options that apply to drag and drop that should be considered prior to adding the sources. individual files.e. the ED Loader will first copy the files to a temporary location to allow successful processing of the files. For example.

and so on. Sources are grouped by type for organizational purposes.When the option to 'Use source name as top level folder' is enabled in the Output settings (see Output section). The Source Queue may also be used to edit information at a source level. the new value will appear in green. The source name may be edited by simply typing the desired name directly into the text box. Outlook mail stores will be grouped together.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. To change the target folder for a particular source. 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. Target Folder . and the documents will be imported into a structure below it. This dialog may be used to choose an existing folder for the target location or to create a new folder. If all sources should be imported below the same target folder. The duplicate source name will be appended with a '-001'. certain items may be edited at the source level versus using the default session configuration settings. simply enter or select a custodian in the 'Default custodian' field which is located above the Source Queue in the session configuration settings. Three settings are listed below: Source Name .LAW PreDiscovery User Guide 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. When a custodian value is changed at a source level. simply select the folder in the 'Default target folder' text box located above the Source Queue in the session configuration settings. Custodian . 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. If the custodian should be the same for all sources. the new name will appear in green. Lotus Notes mail stores will be grouped together. 58 . allowing users to easily locate an item to be removed from the queue (for example). When a source name is changed. the name listed in this field will be used as the top level folder name.The selected sources will be imported into the designated LAW folder. Editing Source-level Settings Once sources have been added to the queue.

Reset All . Source Name. You can also enable this option from the View menu.Resets the Custodian. For Folders. You can also select these options from the Edit menu. the path (including filename) of the file list will be displayed.Acquiring Documents Resetting Source-level Settings The Reset buttons. 59 . if "Recurse Subfolders" is selected to include subfolders. the total file count is displayed after the path in the Source Path column.Resets the Source Name field back to the default. are used to undo changes made to the source-level settings. Reset Folders . Viewing Source Paths Select Show source paths to display the path to each source in the queue.Resets the Target Folder field back to the default. Reset Cstdns. located below the Source Queue. This is displayed next to the Target Folder column. For File Sets. . For File Lists.Resets the Custodian field back to the default. a plus sign <+> is displayed at the end of the source path. Reset Names . and Target Folder fields back to the defaults.

It does not expand loose e-mails or compound documents. as well as both source-level counts and total counts of items inventoried. and e-mail attachments. Microsoft Word documents). total size. archive contents. 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. and items that received warnings. The summary will process and log e-docs. counts based on file type (i. To perform a preprocess summary. 60 . and size of files per file type. The summary will include items such as total file counts. discovered.LAW PreDiscovery User Guide 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. This dialog will display the name of the source being processed.e. the File Type Summary dialog will appear displaying the results. This feature may also be used to generate a report containing the aforementioned information. Next.

allowing users to view the true file types of the items contained in the queue. Viewing File Groups Files listed for each extension group may be viewed by clicking the Files button or View > Files. E-Docs .e. This view will list each file in the group. Loose e-mail and compound documents are not expanded in the summary. Note: This process is only available for items listed in the E-Docs tab. E-mail messages from mail stores are also not included in the summary. E-mail Att. Compound documents are not expanded so files embedded within the parent documents will not be included in the summary or reports. Loose e-mail items are not expanded so their attachments will not appear in the summary or reports. If a file is an e-doc.Acquiring Documents Four tabs exist in the File Type Summary: All . loose e-mail messages. but the number of e-mails can be viewed using the reporting feature (explained below). archives. and archive contents.Displays a listing of files found in the queue. E-docs. .This tab will only be populated once the optional identification process has been executed. the total size of the group. This tab will include loose e-docs. organized by file extension.Displays a listing of e-mail attachments found in mail stores. 61 . archive contents. so the attachments/embedded files from these types of files will not be included.Displays a listing of e-docs only. it may be launched using the Open button. archives (i. and any warnings that may have occurred during the summary or file identification process. zip files). and e-mail attachments from mail stores will be included in the summary. The Prev Set and Next Set buttons may be used to navigate through the groups. each individual file size. Identified .

select File > Open Summary and browse to the saved . File identification automatically takes place when sources are loaded into LAW via ED Loader. Click the Identify Files button or Tools > Identify Files to initialize this process. click Tools > Enqueue from the File Type Summary dialog. To add the sources to the ED Loader Source Queue. The sources will be loaded into the Source Queue and are ready for import into LAW. Click the View Report button to generate the report. which allows users to set the Include/Exclude flags directly from this view.EDSD file. 62 . The Identified tab will display the results of this process and is linked to the file type manager database. 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. Once generated. the report may be printed or saved in a number of available file formats using the File > Save As menu item. Saved summary databases will be saved as . To reload the summary. launch the ED Loader. The View Report dialog will appear. so running this process prior to loading will provide users with a preview of the file types as they will be displayed in LAW. click Tools > Reports from the File Type Summary dialog once a summary has been performed.EDSD files in the location selected by the user. Generating Reports To generate a report based on the contents of the summary. A logo may be applied to the report by enabling the Apply logo to report option and then browsing to the desired image file. The file engine will determine the true file type based on the header of each file.LAW PreDiscovery User Guide Identifying File Types The file identification process may be optionally used to validate the files included in the summary. The File Type Summary dialog will appear displaying the results of the saved summary.

Click the Settings tab and click Archives to reach the list of available options.When selected. GZIP. provided the 'Use nested filename for items extracted from archives' option is selected (see below). JAR. Treat archive items as attachments . Include archive source file (copy full archive into LAW) .The archive filename will precede the filename of each extracted item in the Filename field.Acquiring Documents Archives To access the LAW Electronic Discovery Loader. Users may choose not to copy the file to save space and the file is often not needed once the contents are extracted. The Archive settings apply to these types of files. Enable Archive Extraction . The Filename field will reference the archive filename for the attachments that were contained within the archive. 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).Imports the archive file as a parent document and the contents are grouped as attachments to the parent document. LAW will extract contents of the supported archive file types (see above list). and TAR. LAW currently supports the extraction from the following types: ZIP.zip?filename. select File > Import > Electronic Discovery from the main menu. Use nested filename for items extracted from archives . When an archive file is an attachment to an e-mail. RAR.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.doc 63 . Z. as follows: archive.

Original file Y is preserved. Supported compound document containers: Description Non-MS Office Formats Adobe Acrobat (pdf) Y Y Y Detection Extraction Rich text format (rtf) *Converted to Word format for extraction. the spreadsheet will be embedded as Package.LAW PreDiscovery User Guide Compound Documents To access the LAW Electronic Discovery Loader. but could not be opened. for example. generally stored in RTF) Project Package* *A Package is a general type of embed. Office 2007 64 . if a user were to embed an Excel spreadsheet into a Word document. and Excel is not installed. If the "Enable Compound Document Extraction" box is checked. If an embedded file is suspected. 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. select File > Import > Electronic Discovery from the main menu.FileAttach (Word-authored e-mail with inline attachments. Types currently supported for extraction from compound documents: Word/RTF Excel PowerPoint PDF SnapShot Visio Outlook. Note: Not all embedded files are supported. Click the Settings tab and click Compound Documents to reach the list of available options. 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. a warning will be generated and logged in the Session Viewer and ErrorMsg field.

Acquiring Documents Excel Spreadsheet (OpenXml) MS Office Data File (OpenXml) PowerPoint Presentation (OpenXml) Word (OpenXml) Office 2003 Word Word (xml) Excel Excel (xml) *Compound documents not supported in this format PowerPoint Publisher Project Project (xml) *Compound documents not supported in this format Visio Visio (xml) *Currently not recognized by file engine OneNote Office 2002/XP. Office 2000 Word Excel PowerPoint Publisher Project Visio Office 97. Office 95 Word Excel PowerPoint Project Y Y Y Y Y Y Y Y Y Y Y *N Y **Y Y *N N *Y N Y N Y *N Y Y Y *N N N N Y Y **Y Y Y N Y Y N Y Y N Y Y Y Y Y Y Y Y **Detection of embeds in these types is limited only to the types of files supported for extraction (see above list). 65 .

after the import against other records in the case (Deduplication Utility in LAW). deduplication can be performed at one of two levels: 66 . The scope of the project will determine whether or not deduplication will be performed and which methods will be used. or after the import against other records in the case and other LAW cases (external Inter-Case Deduplication utility). Working digest: The working digest is the method of hashing that will be conducted to determine duplicates. records can be deduplicated against other records in the case and incoming records during the electronic discovery import process (covered in this topic). Enable Duplicate Detection: Enables duplicate checking for the current session. In LAW. The hash values are obtained through metadata fields (e-mail) or by hashing the entire file (e-docs).LAW PreDiscovery User Guide Deduplication A duplicate file is an exact replica of another file. Click the Settings tab and then click Deduplication to reach the list of available deduplication options. During the import process. Duplicate files are determined by hashing either the entire file (e-docs) or key metadata fields (emails). 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. select File > Import > Electronic Discovery from the main menu. To access the LAW Electronic Discovery Loader. 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. A hash value can be thought of as the DNA of a file.

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. Additional information regarding deduplication can be found in the Deduplication Information topic in the Appendix.Acquiring Documents Case Level (Globally): Deduplicates documents against the entire incoming collection and against existing records in the LAW case. Also. 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. The desired state of this setting should be determined prior to the first import into new cases and should not be changed. Doing so will present a mixture of internal and external duplicates and could cause problems when purging. and the native file is not copied to the case folder. Three options are available: Include: Creates a record for the duplicate in the database and copies the native file into the case folder. the current case should be removed from the external database. filtering. For more information. 67 .5. 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. If record is considered a duplicate then (Action): This setting determines the action to take once a duplicate is located. as noted in the interface. Custodian Level: Deduplicates documents against records with identical custodian values. Deduplication may also be performed after the ED Loader import using the Deduplication Utility in LAW or the external 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. or reviewing duplicate records. see the Inter-Case Deduplication topic. the ED Loader will include the hashes of attached files in the parent e-mail's metadata hash. At this point.07. Exclude: Does not create a record. before running the internal deduplication. Warning: While enabling this setting is recommended. Partially exclude: Creates a record in the database but does not copy the native file. the Attach field is incorporated in with the metadata hash which only contains the file names of attached files. When disabled. Include attachment hashes in e-mail metadata hash: When enabled. it is not advisable to change this setting during the course of a case as it will alter the e-mail hashing schema. This setting was not available in versions prior to 5. Click the Cancel button to close this warning and return to the ED Loader settings. If the current case has already been deduplicated via the Inter-Case Deduplication utility. no text is extracted.

Messages formatted as RTF.LAW PreDiscovery User Guide E-Mail To access the LAW Electronic Discovery Loader. Click the Settings tab and click E-Mail to reach the list of available options. e-mails are imported by the date the e-mail was received. including HTML with linked images. These embedded images and non-mail items such as calendars. Received. the format in which they are saved. Save Outlook messages as . non-mail items. Sort Key . During Export. For example. All other messages are saved as HTML. The E-Mail settings identify how e-mails are sorted when loaded into LAW. The four options are: HTML .msg). Embedded images in HTML messages are saved in the same folder as the converted message. 68 . and Subject.Select the output format of Outlook messages as they are imported with the ED Loader. contacts. and tasks. such as an Excel worksheet.The format of the output file is determined based on the format of the email message. or HTML messages. are saved as native Outlook files (*. They are listed in a dependency file (*.The direction of the sort may be Ascending (oldest to newest) or Descending (newest to oldest). These images are not LAW records. are saved as MHTML. Instead they are linked to the HTML file for proper rendering. linked images are exported along with the native file so the HTML file can be properly rendered with associated images.When loading e-mails from mail stores. Four fields can be used to sort the e-mails during extraction: From. and the format of the date field values.dep) with the same root name as the native file. Sort Direction . Sent On. select File > Import > Electronic Discovery from the main menu.Messages are saved to HTML files with the exception of messages containing embedded OLE items that cannot be rendered in HTML. HTML/MHTML (based on format) . it is important to identify how the files are imported into LAW and later produced. if Received is chosen.

e-mails are converted to HTML or RTF based on their original format. MHTML files are web archives that allow the embedding of images directly in an HTML file.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. This eliminates the need for any linked images or dependent files. this setting instructs the ED Loader to maintain the X. Outlook Folder Types . Messages formatted as RTF and non-mail items are saved as RTF. Greenwich Mean Time (GMT). Preserve X. Use this setting only if it is absolutely necessary. MHTML .When opening a mail store. Translate date fields to universal time (GMT) .400 addresses .000). RTF messages are saved directly from Outlook. Note: RTF messages and items use Microsoft Word to convert RTF to MHTML. CC.400 e-mail address (if available) in the To. Due to the secondary conversion from RTF to MHTML using Word.Allows the loading of non-mail folder types such as calendar items and contacts when processing Outlook folders or mail stores. Warning: Messages saved as RTF will not contain the BCC information in the RTF output.mht). 69 . Selecting the "Translate date fields to universal time (GMT)" is a decision to be made based on project specifications. Messages that cannot be saved as MSG files are saved as HTML files.Messages are saved as native Outlook files (*. The BCC field. and BCC fields and not convert it to the SMTP address. any RTF output remains as RTF during the import. This is a function of Outlook and how it renders messages to RTF. Print speeds are also significantly slower with MHTML files. If Word is not installed.All items are saved as MHTML files (*.msg) with the exception of e-mails that contain extremely large recipient lists (typically over 5. will however still be captured in the database and in the extracted text. However. If e-mails were generated in Eastern Standard Time but processed in the Pacific time zone.Acquiring Documents HTML/RTF (based on format) . the date and time stamps take on local properties. Similar to the HTML/RTF setting. so the GMT date option is not applied to the display of the converted file. Text or HTML messages are saved as HTML.The format of the output file is determined based on the format of the e-mail message. the time stamp will be the Pacific time zone's date and time. Log warning messages for e-mails containing RTF body content . 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. and then converted to MHTML files. processing speed is significantly slower when using this setting.When enabled. For this reason. Note: Subtle formatting differences may exist between HTML and RTF messages. MSG . if present. users have the option to translate all date/time fields to the universal time zone. These messages can cause Outlook and the ED Loader to hang.

For example.Any native files that are empty (0 byte file size) will not be copied or written to the database. 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. if a PST is contained in a folder selected for processing. Exclude mail stores from e-doc processing (Mail store as e-doc) . The Exclusions settings are conditional settings that can be used to prevent certain types of records from being loaded to LAW. 70 . the mail store would be recorded as a single e-doc record when this option is disabled. select File > Import > Electronic Discovery from the main menu.This option prevents mail stores from being processed as e-docs. Click the Settings tab and click Exclusions to reach the list of available options. Exclude empty files (0 bytes) from processing (0 byte file) .LAW PreDiscovery User Guide Exclusions To access the LAW Electronic Discovery Loader.

Users may choose from two lists: Include and Exclude. Click the Settings tab and click File Types to reach the list of available options. then it can be opened and processed to tiff or paper (if applicable) individually or in a batch. Provided the reviewer has the native file application. select File > Import > Electronic Discovery from the main menu. File type manager . If enabled. it is understandable that users may not wish to import certain file types. Essentially. If filetype is not included then (Action) . files that are not marked as Exclude in the Exclude list will be imported. The File Types settings allow users to identify specific files for processing. Options are: Include . file types marked as Include in the File Type Manager's Include list will be imported into LAW. Active List (Scope) .Identifies which list will be used to determine the files that will be imported into LAW. Exclude . files that are not checked in the Include list will be excluded. Even if a file type is not supported for printing or conversion. For this reason. LAW supports the import of all file types. metadata and text may still be extracted. loading all file types into LAW is recommended. the file can be opened and reviewed. the Exclude list is not considered during the import and vice versa. Enable File Filtering . If the Exclude list is selected.The File Type Manager displays the Include and Exclude lists and offers several options for managing file types. all files will be imported into LAW. Files that could not be converted to tiff can still be exported and delivered in native file format.If this option is disabled.Acquiring Documents File Types To access the LAW Electronic Discovery Loader. or scope. However. If the Include list is selected as the active list. such as common system files. Once a file is imported in LAW.This option will copy the native file and log a record in the database. files marked as Exclude in the Exclude list will be excluded and not imported into LAW.This option will not copy the native file or log a record in the database.Determines which action is taken for excluded file types. and the native file application exists on the machine.This option will not copy the native file but will log a record in the database. The lists are independent of each other. 71 . If the Include list is chosen. Partially Exclude . Click Edit to open the file type manager. the files imported will depend on the selected scope.

then anything not marked as "Exclude" will be imported. the OrigExt field will not be populated and the DocExt field will contain the original extension.LAW PreDiscovery User Guide Files marked as "Include" will be imported if the active list is set to the Include list.LAW automatically validates files to ensure the extension assigned to the file properly reflects the actual file type. The File menu in the File Type Manager is used to create new file type databases. 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. Multiple file type databases can be created. 72 . If this feature is disabled. open existing databases." field in File Type Manager) to the DocExt field and place the original extension in the OrigExt field. Auto Assign Suspect Extensions . This feature can be useful when establishing procedures on specific files to exclude from processing. 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. With "Auto Assign Suspect Extensions" enabled. if a suspect file is found. If Exclude is set as the active list. it will be reflected in the SuspectExt field ("Y"). Also. LAW will automatically assign the a new extension (from the "Active Ext. and save changes to the current database.

This feature is particularly useful when dealing with multiple mail stores with a source name of "Personal Folders. 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. 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." In this example. The General category identifies settings that relate to source selection and the file type management database. Once extracted. the first occurrence of the mail store will be named Personal Folders. Source Selection Ensure source names are unique when they are added to the queue .If using the drag and drop method to select sources for processing.This option will force the selected folders to be added to the queue as e-doc folders following the scan for mail stores. If this option is not enabled. The user must select a location to which the ED Loader can extract the mail store(s) prior to processing.Acquiring Documents General To access the LAW Electronic Discovery Loader. Click the Settings tab and click General to reach the list of available options. this option will force the ED Loader to search supported archive files for supported mail stores. For example. Scan folder selections for supported mail stores when added to the queue . and so on. the Extract Stores dialog will appear.This option is also located in the Select Folders dialog when selecting sources. Add selected folder to queue when mailstore scan is active . the mail store will be added to the queue. Two sub-options are available below this option: Scan supported archives .When enabled. If a mail store is found. this option will add the selected folder and all subfolders to the Source Queue. while any subsequent mail stores will be added as Personal Folders-001. Automatically set E-Doc folder sources to 'Recurse' when I add them via drag and drop . 73 . only the selected folder will be added to the queue. only the mail store would be added to the queue and the folder of XLS files would not be processed. select File > Import > Electronic Discovery from the main menu. and this option is enabled.Enabling this item will ensure there are no duplicate source names in the Source Queue. Personal Folders002. if a folder is selected that contains 5 XLS files and 1 PST mail store.

LAW PreDiscovery User Guide File Type Management Database Active database .If file type filtering will be used. 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 . this option will identify which database is referenced during the import.

Acquiring Documents NIST(NSRL) Filter To access the LAW Electronic Discovery Loader. The NSRL RDS is publicly available as four ISO files containing hashes within specified ranges. then its contents are evaluated on a file-by-file basis. All three of these files must reside in the same directory in order for the hash lookup to work.Contains hashes from the *NSRL RDS_<NsrlVersion>_C and D ISO's. The two partition databases only contain unique instances of each hash present in the ISO. then it is automatically filtered out and its contents are not evaluated or logged to LAW.part) .mdb) .nsrl.part) . Note: If an archive's hash is present in the NSRL database. 3. It is a collection of known.Contains version information and verification counts. This also applies to embedded/attached archives. ED Loader will raise an initialization error and block processing until this configuration is corrected or until the NIST(NSRL) Filter option is disabled. Enabling this option will exclude any files present in the configured hash database using the documents' SHA-1 hash values. 2. in addition to a hash partition table pointing to one of the two partition databases. traceable software applications. Hash Database The NSRL hash database is a collection of SHA-1 hashes for known. The NSRL RDS is a collection of file hashes provided and maintained by NIST (National Institute of Standards and Technology. If the archive's hash is not present. see www. The hash database used for this ED Loader filter is compiled from the NSRL (National Software Reference Library) RDS (Reference Data Set). E-Mails are not tested against this filter (although their attachments will be).nist. 75 . If this condition is not met. Currently. See the below "Options" section for information on downloading and configuring the hash database for use with LAW's ED Loader. select File > Import > Electronic Discovery from the main menu. or the versions of these files are mismatched. Partition database (2 of 2) (EdLoaderNistFilter-<NsrlVersion>-ISO(C-D). Partition database (1 of 2) (EdLoaderNistFilter-<NsrlVersion>-ISO(A-B). This filter is typically employed to exclude known files that have no value to a production. Master database (EdLoaderNistFilter-<NsrlVersion>. traceable software applications. the database is deployed as three files: 1.gov).Contains hashes from the *NSRL RDS_<NsrlVersion>_A and B ISO's. Click the Settings tab and click NIST(NSRL) Filter to reach the list of available options.

After enabling the filter. traceable software applications. These hashes are stored in a partitioned Access database (*. 76 . If a newer version is found. which is required in order to use this feature.Checking this box will enable the NIST(NSRL) filter for the ED Loader session.Click this link to launch an informational dialog regarding the NIST (NSRL) feature. the hash database compiled and hosted by LexisNexis will also be updated as the new data becomes available. which must be downloaded from a LexisNexishosted web site (see option below).The NSRL RDS is updated quarterly and therefore. The database provided here is the only database that can be used with the NIST filter. Check for updated NIST(NSRL) hash database .LAW PreDiscovery User Guide Options Enable NIST(NSRL) Filter . 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). Hash Database .MDB).Click this link to download the NIST(NSRL) hash database. Click here to download the latest version of the NIST(NSRL) hash database (launches browser) . Click the ellipsis button to browse to and select the MDB file and then click the Open button.zip and contains three files which make up the partitioned hash database (see "Hash Database" section above "Options"). Click here to learn more about the NIST(NSRL) hash database . The file is an archive named EdloaderNistFilter. LAW will prompt to download the updated database. the hash database path must be configured (see next setting).The hash database is a collection of SHA-1 hashes for known. Click this link to check for an updated database.

This option does not apply to mail stores as the path within mail stores will always be mirrored when imported into LAW. will be used as the top level folder name for each source when imported into LAW. Typically. depending on the selected Output options. the entire folder structure of the selected electronic files will be re-created in the tree view in LAW.Relative applies to e-doc selections only. this is the recommended setting as it may ensure shorter paths and prevent any issues with operating systems' path limitations. For example. and may be important to export specifications for the project. Relative . The path created in the tree view in LAW will begin with the selected folder.With Mirrored as the selected output scheme. Options Categorize output sources (E-Mails/E-Docs) . This only applies when <Case Root> is NOT set as the target folder for a source or sources. This will prevent records in both EDOC folders from being loaded into one folder.Acquiring Documents Output To access the LAW Electronic Discovery Loader. as displayed in the Source Queue on the Sources tab. Ensure root output folder is unique in LAW . or the folder containing the selected files. Use source name as top level folder . select File > Import > Electronic Discovery from the main menu. Click the Settings tab and click Output to reach the list of available options. LAW will import one of the EDOC folders into a 001CD-001 folder and the other EDOC folder into a 001CD-002 folder. Folder Output Scheme Mirrored .When enabled. Structure The structure section provides a preview of the folder structure in LAW (following the import). 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.The Source Name. 77 .Ensures the target folder for each source is unique in LAW. The Output settings will determine how selected sources are identified and organized in the tree view of LAW. all mail store sources will be imported into an "EMail" folder and all e-doc sources (including loose e-mail) will be imported into an "E-Doc" folder.

Perform full-text indexing .Following the import. select File > Import > Electronic Discovery from the main menu. This option will not be available unless one of the above options has been enabled.Allows users to specify the number of seconds to pass before the results dialog is closed and the selected post import action takes place. LAW will automatically begin indexing any documents flagged to be indexed immediately after closing the results dialog that appears following the import. If no options are selected. the grid view will launch and display only the records imported during that session. Then. 78 . Results dialog will close after <N> seconds. Display imported documents in grid . Click the Settings tab and click Post Import Actions to reach the list of available options. LAW will prompt to index the documents (SQL cases only).When enabled. following a manual exit from the results dialog. LAW will close the results dialog after the specified number or seconds.When enabled. Post Import Actions are used to determine which action will occur automatically following an ED Loader import. 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.LAW PreDiscovery User Guide Post Import Actions To access the LAW Electronic Discovery Loader. Be sure to make any desired changes to the tiff conversion settings prior to configuring and initializing the ED Loader session. unattended . Convert imported documents to TIFF . the "Display imported documents in grid" option will be automatically selected as well and grayed out.

it is recommended that users also select the "Validate extracted text" option (below). so that all file types will be scanned for text.Scans each text file for readable text. Author.Enables the extraction of text from applicable files during an ED Loader import session. Any text files that do not contain readable text will be considered invalid and discarded (i. Text" flag in the File Type Manager (see File Types).Includes any available document properties in the extracted text file (i.Acquiring Documents Text Extraction To access the LAW Electronic Discovery Loader.Overrides the "Ext.e. text files with only form feed characters). This category is used to configure settings related to the text that is extracted from files during an ED Loader import.e. Enable binary scanning in text extraction . Title). Include metadata in extracted text . Click the Settings tab and then click Text Extraction to reach the list of available options. Validate extracted text . 79 . select File > Import > Electronic Discovery from the main menu. Enable Text Extraction . If this option is enabled.

Set as Default . Once enabled.This option will save the current settings to a case-level ED Loader configuration file.LAW PreDiscovery User Guide Session Defaults In addition to the various configuration settings for ED Loader sessions. This feature will be useful if a user needs to cancel out of the Loader prior to starting a session.This option is used to set the current settings as the defaults for all LAW cases that are launched with the same LAW executable. 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. applying the settings will ensure that the user does not have to "start over" when re-launching the Loader. 80 . All settings in the Settings tab are saved as well as the DocID Seed. Apply Settings . for example. the button will read "Unlock Settings" and will do just that when clicked. the Settings tab contains three options that should be considered when users are configuring sessions for import.

such as warnings and any errors that occurred during the import.Provides a list of session totals. and have no. while the UnderlyingValue field displays the value of the setting in the configuration file. The Session Viewer may also be launched by clicking File > Import > Electronic Discovery.Acquiring Documents Reviewing Sessions Session Viewer Once an Electronic Discovery Loader session is complete. then File > Open Session from within the ED Loader.Lists all ED Loader settings.ini. The number of records listed in each tab is shown beside the tab name in parentheses. These logs will be displayed in the Session Viewer. Settings .ini (located in root LAW case folder).config. such as the number of items processed. Choose a session and then click View Session to view the contents. Tabs There are 13 tabs in the Session Viewer containing information about the currently selected session. or if it only exists in the EDLoader. and the state of those settings during the selected session. The Session Browser dialog will appear providing a list of existing sessions for the current LAW case. The VisibleInUi field will indicate if the setting is visible in the ED Loader interface. and filtered items. The Show all sessions option will allow users to view logs for sessions initialized on all workstations (for the current case). The SettingKey displays the name of the setting in the configuration file.config. attachments. Overview . as well as certain settings from the EDLoader. 2.case. errors. a log containing important information about the session may be viewed.case. 81 . Items listed in bold within the grid are either parent documents or documents that are not. 1. which is accessible by clicking the View Logs button on the results dialog that appears following the import.

Click Yes at the prompt to view the output file or click No to view the file later. these documents are still imported despite the error.Lists all records that were imported during the current session. Click View > Expand All or right-click > Expand All to expand the groups.Lists all sources that were included in the session. this tab will provide the error message in the row of the item that failed. Warnings .Lists records that received an error message during the import. 10. choose File > Save As from the Session Viewer's main menu or click the Save As button on the toolbar. Typically. See Session Configuration for more information on session labels. Duplicates . 13. The properties for attachment records will contain information about the parent record as well. and the PDF extension would be assigned to the OrigExt field. NIST Exclusions . Select a file type (CSV or TXT). The sessions will be named according to the user-defined Session Labels (specified in the ED Loader prior to import). LAW validates all files to ensure the original file extension reflects the actual file type. If a source-level failure occurred. 7. depending on the selected action in the File Types settings. The warning message will also be logged in the ErrorMsg field for the affected records. These records are not written to the LAW case database. Check the box beside a field to display it in the grid. the error message will be logged to the ErrorMsg field for affected records. Conditional Exclusions . Fields The Fields section lists the fields available for display for the currently selected tab. 6. 5.LAW PreDiscovery User Guide 3. 11. depending on the selected action in the Deduplication settings. 8. To save the currently selected tab only. Click View > Collapse All or right-click > Collapse All to collapse the groups. The documents may or may not have been imported. Commit Errors . This may have been due to the cancelling of a session. Sources .Lists records that were filtered based on the Include or Exclude list. and if so.Lists records that were determined to be suspect files based on the file extension. location. 12. See File Types for more information. or due to a problem file that caused a crash during the import (see Cancelling/Resuming Sessions).Lists records that were excluded based on the Exclusions settings. To group by a particular field.Lists any records that did not complete the import process.PDF extension. Processing Errors .Lists documents that errored during the import process. Incomplete .Lists records that received some sort of warning message during import. 9. the documents listed in this tab were unable to be imported due to the error. Typically. 4. 82 . 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.DOC file that was renamed and given a .Lists all records that were flagged as duplicates during the import process. All . If the 'Auto Assign Suspect Extensions' option is enabled in this situation. make the field visible and then drag the column header into the grouping area above the grid. Exporting Session Data The data contained within the tabs in the Session Viewer may be exported to a separate file. the DOC extension would be assigned to the DocExt field in LAW. An example of a suspect file would be a Word . FileType Exclusions . and then click Save. These documents are not written to the LAW database. and file name.Lists records that were filtered based on the NIST/NSRL database. These records may or may not have been imported. Suspect . Item Properties The Item Properties panel displays metadata and other information specific to the selected record.

83 . click File > Export To Excel or click the Export to Excel button on the toolbar.Acquiring Documents To save all tabs in the Session Viewer to file. Each tab will appear in its own worksheet in the output Excel file. Select a location and file name for the output file and then click Save.

84 . clicking the globe icon on the main toolbar.LAW PreDiscovery User Guide Summary Reports Once documents have been loaded via the Electronic Discovery Loader. or by selecting a folder and clicking Folder > Grid View (or Grid View (Recurse)). the ED Reports feature may be used to generate reports based on the imported data. click Tools > ED Reports to launch the Report Preview dialog. (These reports are also available from the View Reports dialog in File > Administration. If the EDPages field contains data.) There are currently four reports to choose from when utilizing this feature: Supported Files by Type: Lists all supported files loaded via ED Loader. The term 'supported' refers to records that have an application assigned in the SourceApp field. grouped by file type. See the Viewing Reports topic for more information. Once the standalone grid has been launched. Launch the standalone grid display by clicking Tools > Display All Records. and a count of supported files for each file type. these values will also be included in the report. a total count of supported files. running a query. The report contains paths to each file.

a total count of unsupported files. 85 . Once the report appears in the preview window. The report contains a total count of supported files and a count of supported files for each file type. To create a report. Unsupported Files by Type: Lists all unsupported files loaded via ED Loader. choose Format > File Numbering prior to creating a report. If the EDPages field contains data. these values will also be included in the report. click the name of a report from the list or choose it from the "Selected Report" drop-down list. If the EDPages field contains data. grouped by file type. but does not include paths/filenames to each individual file. these values will also be included in the report. and a count of unsupported files for each file type. A preview of the report will appear in the Report Preview dialog and may be saved to a PDF or HTM file. The report contains paths to each file. The report contains a total count of unsupported files and a count of unsupported files for each file type. The term 'unsupported' refers to records that do NOT have an application assigned in the SourceApp field (<No Source Specified>). a different report may be selected using the "Selected Report" drop-down. but does not include paths/filenames to each individual file. Unsupported Files by Type (Condensed): This report is similar to the Unsupported Files by Type report. Supported Files by Type (Condensed): This report is similar to the Supported Files by Type report. or printed to paper.Acquiring Documents Note: The EDPages field contains data when the Extract ED Pages Counts or the E-Print process is run on the documents. If the EDPages field contains data these values will also be included in the report. File Numbering To number the file path entries in the Supported and Unsupported Files by Type reports. Watermarks Watermarks may be applied to reports by selecting the Apply watermark to reports option and browsing to the desired watermark file.

click File > Import > Electronic Discovery and then File > Sessions from the ED Loader. Cancelling Sessions When a user attempts to cancel an ED Loader session. To restart a session. possibly resulting in incomplete items. The "Safe Cancel" is the recommended option. Choose the incomplete session from the Session Browser dialog. The "Continue" option may be used if the user decides not to cancel the session. three options will be presented in a Confirm Cancellation dialog. 86 . The ED Loader will wait until the current item is complete before ending the session whereas the "Normal Cancel" will stop the session immediately.LAW PreDiscovery User Guide 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. Resuming Sessions ED Loader sessions may be easily restarted after a user cancels a session manually.

Sessions that end unexpectedly due to some sort of crash may generate a restart prompt when the ED Loader is relaunched from the same machine in the same LAW case. the Loader will pick up where it stopped at the time it was cancelled. Click the Resume button to restart the session. 87 . The import process can be stopped manually by clicking the Cancel button. Note: Only sessions initialized from the current workstation may be resumed. the Loader will attempt to reconnect to the database and continue processing. Lost Database Connection If the connection to a SQL Server is lost during the ED Loader import process. During this time.Acquiring Documents Incomplete sessions will show "recoverable" in the Status message as shown in the above image. the ED Loader will display a notification on the Progress dialog just above the total progress bar.

choose Select Scanner from the Scan menu to display a list of all available scanner drivers.LAW PreDiscovery User Guide Scanning Documents Selecting a Scanner Before scanning any documents from LAW. LAW will attempt to load the default scanner each time LAW is launched and a case is opened. 88 . Ensure that the scanner is on and restart the computer. do not automatically run the install for the scanner driver. If a new model scanner has been purchased that came bundled with an ISIS driver. To select a scanner. there are two possible explanations: either the wrong driver was selected or the scanner was not recognized by Windows. If the connected scanner is not in the list. contact LexisNexis to determine if a driver is available for the scanner. First. LAW will generally run any scanner that uses an ISIS driver. Bundled driver installations typically contain additional system files that may overwrite critical image libraries and cause problems when running LAW. If Windows recognizes the scanner and it still cannot be selected. If an error occurs when selecting a scanner. the user must first select a scanner. check the LAW CD for that scanner model or contact us to determine if we have a driver for that scanner. All scan functions will be disabled until a scanner has been recognized. This is not a complete list of supported scanners. contact LexisNexis for assistance. The scanner will not be recognized if it was not turned on prior to the operating system loading. Once a scanner has been selected.

89 . grayscale). Common scanner settings include mode (black & white. resolution. The Scanner Settings dialog will appear. resolution (DPI). and page size may vary from scanner to scanner. Setting a custom scan area may be necessary with some scanner models that frequently exhibit a black border around scanned images. 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. it cannot be adequately removed with black-border removal and must be removed by adjusting the scan area. and contrast. Settings such as mode. Scan Area The scan area can be further adjusted by selecting the Area button. color. page size. A Scan Area dialog will be displayed that allows users to fine-tune the scan area for the current page size. These settings can be modified by selecting Scanner Settings from the Scan menu. The scan area dialog allows users to set an X and Y offset for the page as well as a custom height and width. brightness. Because the black border is not even on all sides.Acquiring Documents Scanner Settings Scanner settings are those properties that control the operation of the scanner directly. This custom area applies only to the current page size.

LAW PreDiscovery User Guide Scan Brightness Scan brightness can be adjusted in the Brightness section of the Scanner Settings dialog box. Alternatively. shortcut keys may be used. 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. The hot keys for adjusting the brightness of the scanner are (Alt+UpArw/DnArw). 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. 90 . select the More button from the Scanner Settings dialog. Using the <Alt+UpArw> combination will increase brightness by 32 points (-32 points for Alt+DnArw). The special settings available will vary depending on the selected scanner. Special Settings To display any special settings for your particular scanner.

if pages are in the document feeder. Legal (<F8>). Double Letter (<F9>). 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. Simplex is used to scan single-sided documents and Duplex is for double-sided documents. Scan Mode The Scan Mode controls how the scanner will scan documents: Simplex (<F10>). shown below). 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. The scan options can be toggled by selecting the desired option from the Scan > Scan Options menu.Acquiring Documents Scan Options In addition to the standard scanner settings. and A4. it defaults to 91 . although. This option allows users to toggle between the four most popular page sizes: Letter (<F7>). Duplex (<F11>). LAW provides several scan options to help improve scanning efficiency. The Flatbed setting is used to scan a page from the glass bed. Scan Menu Status Bar Page Size The Page Size setting provides a quick alternative to selecting the page size from the Scanner Settings dialog. or Flatbed (<F12>).

The scan area can be adjusted from the Scanner Settings dialog. See the Flagging Documents/Pages for OCR section for information on flagging pages after they have been scanned. use the Turnover Mode option (see below) to scan double-sided documents. These images can be opened with any image viewer and printed if users need to prepare a scan job with break sheets. This feature can be extremely useful as it allows users to combine both single. If the black edge is uneven or slanted down the page. 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. Light-colored paper is recommended when printing barcode sheets (e. LAW relies on the contrast between the bars in the barcode and the background color of the paper for detecting the barcode value. Invert Pages The Invert Pages setting allows users to invert (rotate 180 degrees) odd or even pages of a document. This filter will only pick up even black edges. 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). all pages scanned will be saved. If the scanner does not support duplex scanning. The settings for the break sheets can be specified from the Imaging tab of the Options form. Scanner brightness or contrast (Scan > Scanner Settings) may require adjustment if LAW is having a difficult time recognizing the barcodes. 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. OCR results may improve if Noise Removal is performed on a document before converting it to text.g. If this option is not set. The backsides of the double-sided documents containing text or images will be retained. OCR All New Pages The OCR All New Pages setting determines whether or not all new pages being scanned will be flagged for OCR. so this filter should be selected if using the Drop Blank Pages scan option. Pages with graphs and tables or handwriting are not good OCR candidates and may negatively impact OCR performance.. light yellow.LAW PreDiscovery User Guide Simplex and scans a single page from the feeder. Blank backsides of all singlesided documents will be dropped. 92 . The black-border removal filter can also be applied to multiple documents during Batch Processing.and folder-level breaks while scanning. Barcode pages can be used to determine both document. it will not be dropped. Auto-Deskew The Auto-Deskew scan option will deskew (straighten) documents as they are scanned. pages with very low pixel ratios will not be saved. If this option is set. or light green). The deskew filter can also be applied to multiple documents during Batch Processing and to individual documents (see Page-level Cleanup). LAW allows users to flag certain pages for OCR to help increase OCR speed and efficiency. Images with the default barcode settings can be found in the installation directory for LAW. This feature is used for double-sided documents that are printed with opposite orientations on the front and back. Detect Barcode Breaks The Detect Barcode Breaks setting allows users to scan multiple documents in a single batch. white. light blue. See Using Barcodes for more information about barcodes. Black borders left on pages can prevent LAW from recognizing blank pages. Black-Border Removal The Black-Border Removal scan option will remove black edges from all newly scanned images.and double-sided documents in a single batch.

saving a great deal of time. This feature can be very useful for scanning checks or note cards. Scan Page Limit The Scan Page Limit feature can be used to specify a page limit for the number of pages scanned per document. Turnover Mode The Turnover Mode setting can be used to scan double-sided documents without a duplex scanner. This can be used to scan a large group of single-page documents in one batch. Note: If this option is enabled. If using this feature to scan landscape. 93 .Acquiring Documents Scan Rotation The Scan Rotation setting can be used to rotate pages as they are scanned. Single Pages The Single Pages setting instructs LAW to save all pages in a batch as one-page documents. or 270 degrees. 180. the "Detect Barcode Breaks" setting will be ignored because the document must be flipped after the front side has been scanned. Scanning documents in landscape mode may increase the scanner throughput and help prevent paper jams. the scanner must support double-letter page size in order to capture the full height of the document. Note: These settings should only be modified if the default settings are not working or causing problems. for example. 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. Images can be rotated 90. Configure Filters This option allows advanced users to modify the default settings of certain filters. LAW then rebuilds the document in the proper order.

Scanner Output Color Format This setting is for display purposes only. Note: TIFF images (specifically CCITT Group 4) are accepted as the industry standard and are the recommended format for black & white images. certain features (e.tif).jbg). This setting identifies the color format selected by the scanner and determines which file types are available. 94 . and TIFF (*.LAW PreDiscovery User Guide Imaging Options Imaging options will control the format used to save images when scanning and the settings used for barcode break sheets. is used to save newly scanned images. or packaging. (See the Using Barcodes section for additional details.pdf). if Binary (Black & White) is the current color mode. it may not be modified from this form.bmp).pda). Portable Network Graphics (*.. To change the color format displayed. The file types available are determined by the color format selected.png). Calera (*. Users can scan to PDF (a frequent request). Bitmaps (*. However.dcx). Fax (*. JPEG (*.jpg). users must change the color mode via Scanner Settings. PaintBrush (*. Common file types include Adobe (*. JBIG (*.g.) These options are available by selecting Tools > Options > Imaging from the main form. File Type The File Type setting determines what type of format. JPEG is not available as a file type because it can only be used for True Color and 256-Level Grey images. For example.pcx).

In order to use these settings. Barcode Breaks Barcodes are used in scanning to establish barcode break settings. The Multipage option stores images as multiple pages in one file. CCITT Group 4 is the common compression for a TIFF image. If scanning color or grayscale images. scanning a 5 page document stores each page as a separate file. 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). although this compression is not available for non-bitonal images. 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. The files are stored in the $Image Archive folder located in the root case folder. For example. For example. See Using Barcodes for more information. Note: Moving pages in the thumbnails display is not currently supported for records scanned using the Serialized Storage Schema. 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. If PDF images are required in the destination application. we recommend Sequential JPEG as the compression type (TIFF as the File Type). the "Detect Barcode Breaks" scan option must be enabled. Storage Schema The Storage Schema setting determines how scanned documents are stored. The Serialized option stores images as single-page images. 95 . 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. It offers excellent compression for both color and grayscale images and can be used with multi-page images.Acquiring Documents endorsing images and OCR to a non-text format) will not be available to PDF images.

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. and select New Document (<F3>) from the Scan menu. Attachments cannot be added at scan time to intermediate documents in a folder. If scanning from the document feeder. attachments should be preceded by an attachment break sheet as opposed to a standard document break sheet. For scanner models without this functionality. select New Attachment (<Ctrl+F3>) from the Scan menu. The break sheet for attachments is named attach1. A shortcut to this file (Attachment Break #1) can be found in the Break Sheets subfolder in the LAW program group. clips.LAW PreDiscovery User Guide Scanning in LAW Once the scanner has been selected and any additional scan options have been set. open the desired folder. and an attachment break sheet would precede each of the three attachments. users are ready to begin scanning. All new documents will be added to the end of the folder. Attached documents' ItemNo value will appear indented in the document list to indicate that they are attached to the previous document. 96 . Therefore. see the Working with Attachments section. New Documents Adding Documents To add new documents to the current folder. The new document will be added as an attachment to the last document in the current folder. Adding Attachments Documents can also be added as attachments to other documents. move it immediately behind the appropriate parent document. For more information on attaching existing documents. When scanning documents. All newly scanned documents will be saved in the current folder. If this option is enabled. LAW scans until the feeder is empty. remove any staples. set the 'Prompt to continue scanning when feeder is empty' option on the Preferences tab of the Options form (Tools > Options). users will be prompted to insert more pages when the feeder is empty or users can cancel to end the batch. rubber bands or other bindery materials. This allows logical grouping of related documents. Documents preceded by an attachment break sheet will always be attached to the previous parent document. If using barcode break sheets to scan multiple documents. and then place the page(s) to be scanned in the auto-document feeder or on the flatbed. and then manually attach it. so encourage scanner operators to make periodic checks to ensure they are still in the intended folder. Adding attachments during scan time can be done in two ways. To manually add an attachment. a standard document break sheet would precede the parent. This is helpful if scanning large documents that exceed the capacity of the feeder or multiple documents separated by barcode document break sheets. the user will have to scan the attachment as a normal document to the end of the folder. to scan a document with three attachments.tif and can be found in the installation directory for LAW. If documents have been scanned out of 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. all processing functions (batch processing. Note: The Append Pages function is not a batch scanning function. 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. Note: If multiple documents are selected. select the Existing Page(s) menu item from the Insert menu. even if the "Detect Barcode Breaks" feature is activated. select the Edit > Insert > New Page(s). To append new pages.. use the "Prompt to continue scanning. select the document to which the pages should be appended. exports) are executed in scan order. To insert pages from existing documents. If users need to insert new pages from the scanner. 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. 97 . The inserted document will be placed above the currently selected document in the current folder. the user will be prompted to select one or more existing images to insert. If inserting existing pages." setting to allow users to keep adding pages to the current batch until it is complete. This feature is very important because. allowing users the ability to insert a document that was missed at scan time.. unless documents are specified by a query. Inserting Pages LAW also allows users to insert pages into existing documents in the event that pages were missed or acquired from another source. In other words. The new page(s) will be added to the end of the selected document. If using break sheets. 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. Modifying Existing Documents Appending Pages The Append Pages function lets users append new pages to an existing document. It is only intended to add pages to a single document.Acquiring Documents (In the above figure. and select Append (<F5>) from the Scan menu. The new pages will be inserted before the currently selected page. Also. Otherwise. they will be imported in alphabetical order by filename. it will not check for barcode break sheets.

The Edit > Replace > Image from File(s) option allows users to replace an entire document with an existing image. Both replace pages and document work the same as the append and insert page functions.LAW PreDiscovery User Guide 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). Only one existing image may be selected when using this feature. disabling the detection of barcode breaks. the new pages will replace the current page forward for as many new pages are scanned. If replacing pages. 98 .

Barcode-related settings may be found by clicking Tools > Options from the main menu and choosing the Imaging tab. If a barcode that matches this value is encountered while scanning. the barcode values may be stored in an index field or used to number the documents. it is automatically created. Folder Level This setting determines the barcode value used to represent a folder break. LAW will increment the current folder name by one for the newly created folder's name. These break sheets may be used to automatically break documents. Barcodes breaks may also be used when importing raw images. and/or create attachment records during the scan process. a new document is started in a new folder. folders.Acquiring Documents Using Barcodes Documents may be prepped for scanning using barcode break sheets. See the Importing Raw Images section for additional information. to break the documents and optionally code multiple index fields. With additional configuration. 99 . If the next logical folder does not exist.

however. If this setting is disabled. If a barcode that matches this value is encountered while scanning. Use Thorough Scan This setting causes LAW to use a more rigorous barcode detection method. To use this feature.). 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. break sheets must be created for every unique value or every document (if using to autonumber). however. This setting can help recognize poor barcodes with lines missing that may prevent recognition. To include multiple document break sheets. Multiple values to ignore may be specified by separating each value with a semi-colon (. As such. 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. When using this feature.). Attachment Level This setting determines the barcode value used to represent an attachment break. or Folder level break sheets. (Note: If spaces exist in the prefix or field name. take longer 100 . Scan Entire Page This setting causes the entire page to be scanned for barcodes at scan time. If a barcode that matches this value is encountered while scanning. it should be used with caution and only as a last resort when all other options have failed. Attachment. if the user has entered "/p/f IDDocumentID" (without quotes) for the value of a document break. The <field> is the name of the field used to store the value. enter all possible values separated by semi-colons (. Ignore Barcode Value Use this option to ignore and drop barcodes matching the specified value during scan time. and the remaining text would be stored in the DocumentID field. This method does. To create a new region. LAW would recognize all barcodes starting with "ID" as a document break. a new attachment is created and attached to the previous document. 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. This region can be modified by creating a new region and selecting Tools > Barcodes > Set Scan Region. Dilate Scan Region Dilates (widens. similar to converting a font from normal to bold) the area tested for barcodes. A barcode value of "IDABC001" would then be detected as a break sheet. and "ABC001" would be stored in the DocID field of that document. Enabling the thorough scan will improve recognition and is especially helpful in recognizing poor quality barcodes. 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. only a portion of the page will be scanned for barcodes.LAW PreDiscovery User Guide Document Level This setting determines the barcode value used to represent a document break. The region used for barcode detection will become highlighted on the current image. they MUST be enclosed in single quotes. its use may actually prevent recognition of otherwise recognizable barcodes. To use this feature for auto-numbering.) The value to be stored is the value of the barcode with the prefix stripped. a new document is started. For example. 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. simply specify BegDoc# as the field name. This notation may be used with Document.

Page. the barcode sheet will be imported as a normal page in a document. If a region has been created. e. 101 . the lower the quality of the scanned image and barcode will become.Acquiring Documents and slows scanner throughput. select Tools > Barcodes > Scan All Pages from the main form.LexisNexis recommends using a light colored paper. and any recognized barcodes will be saved to a delimited text file in the following structure: Value. choose Scan > Scanner Settings and increase or decrease the contrast or brightness of the scanner and test the new settings. if the barcode sheets are too badly wrinkled. Also. 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. DPI .. If LAW appears to be detecting barcodes sporadically.The lower the DPI. this adjustment will likely resolve the problem. The most common DPI settings are between 200-300 DPI. only this area of every page will be scanned. All pages of the current image will be scanned. the entire page will be scanned. although the difference is negligible on faster systems when using a relatively small scan region.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. LAW Settings . which can be difficult to read. This test may also reveal an unexpected value of the barcode which could be causing the problem. If no region is active.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. BarcodeNo. Tools > Options > Imaging tab: Using all three of these settings will override the "Scan Region" as noted above and scan the whole page.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. Paper . Photocopies of barcodes may result in "fuzzy" barcodes. Troubleshooting Barcode Breaks The following section contains information for troubleshooting common issues relating to barcode break sheets not being recognized in LAW. Expected Barcode Values . In LAW. each new page becomes its own document) Auto-Deskew may need to be checked Noise Removal is not checked .g.Verify that the value on the barcode matches the value shown under the Tools > Options > Imaging tab. It may be necessary to run multiple tests to find the optimal setting for the scanner. light yellow or light blue paper. A Laser Jet printer should be used to create a sharper barcode font. If these values do not match.Adjustment of the contrast and/or brightness of the scanner may be required to produce a better quality scanned document and barcode image. Extracting Barcode Information LAW can scan all pages of the current document for any barcode values. Dilate scan region is checked Scan entire page is checked Use thorough scan is checked If a barcode image is already present . Scanner Brightness . they may become unreadable as well. To access this feature. The value on the barcode must match the value in the "Doc" field to be considered an actual document break sheet.

LAW PreDiscovery User Guide If the scanner is able to scan all the barcodes but does not detect them . For additional assistance with barcodes.Re-review the items above or split the documents based on the barcode images using the Split document function. right-click. please contact Technical Support. and select Split Document > Barcode break sheets. Select the image. 102 .

This applies to Doculex. The image and native records. To toggle the setting.x or 5. This log file is named <job name>. LAW offers the option to link to files in their current location. so when attempting to view the logs in the Session Viewer from the target case. or in a case from a previous version of LAW. Opticon. **KNOWN ISSUES: The DupStatus. text.x) into a new or existing LAW case. IPRO. The path structure for the existing case will be re-created in the current case relative to the current folder. If the source image should not be altered. With the exception of Z-Print imports.e. The associated text files will be copied to the applicable location within LAW's case folder structure. Note: Modifying the images in LAW (i. single-page will remain single-page and multi-page will remain multi-page. and _DupMethod fields will be cleared for EDD records being imported into a new LAW case. 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. 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. in an existing project in another format. create a new case or open an existing case and select File > Import > LAW Case.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. and index information from the source case will be copied into the current case so there is no danger of losing any existing data. mean that the user must manually remove the existing case if everything was imported successfully and it is no longer needed. use the Import Raw Images function detailed in the Importing Raw Images section. LAW will avoid copying any native files or images associated with the load files and link to their existing location. two copies of the same images will exist. Note: LAW will not link to document text when using the "Link to source files in place when importing load files" setting. Import Formats LAW Case The LAW Case import function allow users to import an existing LAW case (created in version 4." When enabled. This does. however. To simply import raw images (without a load file or defined format). do not use the "Link to source files in place when importing load files" option. Imported files must be accompanied by a load file in one of the supported formats if document boundaries are to be determined. LAW will store imported images in the same format as the original images. rotating or annotating) will result in the source file being modified. To import an existing LAW case. all images imported via load file will be stored in the <case root>\$Image Archive folder. users will notice a "database not found" message. 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. All fields in the source case will be automatically created if they do not already exist. and Summation load file imports. _DupID. click Tools > Options > Preferences and locate "Link to source files in place when importing load files. The LAW case list will appear allowing users to select a case from the current list or browse to one not in the list. EDRM. Rather than copying files into the LAW folder structure during import.. Session databases are not copied from the source case folder to the target case folder. If single-page images exist with no document breaks defined. User-defined page-level fields existing in the source case will not be imported into the target case.csv and is located in the root destination path of the processed Z-Print 103 . otherwise.

Click the Options button to view the available import settings. LAW will import the images and metadata into the LAW case regardless of what the DocID value is for the existing documents (normal method). 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 this option is selected. Check for Matching Records .LAW PreDiscovery User Guide job. 104 . 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. This allows users to pre-screen the documents and make detailed selections on the documents they want to process. LAW can also import a pre-saved job that has not yet been processed to images. If an exact match is found. there are 3 additional options on how the matching data can be updated.If this option is not selected.

Link to images in place .If this option is set. and you choose to re-import only 1 field.g. only the 1 field will be updated with the new information and the other fields will remain unchanged.If the DocID of the incoming data matches an existing document's DocID value. it ignores records without images (those with pagecount=0).Acquiring Documents Ignore incoming record .dii). Doculex Imagebase The Doculex import allows users to import images from a Doculex imagebase. this may result in page count differences between LAW and the Pages field in the csv. So if the existing record contains 10 fields of data. BegDoc# and EndDoc#. Drop Blank Pages . This feature is useful if a csv file was only partially imported and skipping the existing records would speed up the import process.dbf). Replace existing record . To import a Doculex imagebase. If importing multiple imagebases. Opticon Load File To import an Opticon volume.opt or *. While this will not affect LAW. users can specify the sensitivity of the drop blank pages filter. A range file is simply a delimited text file with two fields. If a separate folder for each volume is not created. the 10 fields will be cleared and only the 1 field will be populated. Note: If pages are dropped. The folder structure will be re-created relative to the current folder. Existing breaks can be overwritten with new ones defined by a range file. the data from the csv will update the existing metadata for the specified document and the image itself. such as speckles. the data from the csv will replace all the existing metadata for the specified document and the image itself.If the DocID of the incoming data matches an existing document's DocID value. If text files matching the image filenames are found in the source directory.). This can be useful when using the Update Z-Print Flags feature. \002. the document breaks defined in the Doculex imagebase are used. the metadata in the csv file will not be updated to reflect the new page size in LAW. Update existing record . images from different volumes in the same folder may occur. Note: This update feature is primarily designed to attach images to existing data. etc. select File > Import > Load File and browse to the desired imagebase (Doculex3.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.The data in the csv being imported will not be imported if a document with a matching DocID value exists. which specify the ranges to use when rebuilding the documents. users may have to select the image path for the 105 . Ignore Unflagged Documents . So if the existing record contains 10 fields of data.LAW will drop any blank pages that are detected during the import process to reduce image sizes and total page counts for documents. Summation Load File The Summation import allows users to import images with document breaks defined by a Summation load file.log). Depending on the path notation in the load file. select File > Import > Load File and browse to the desired load file (*. and you choose to re-import only 1 field. the text files will be imported as OCR text. or folds. Pristine White (recommended) is used for perfectly (all white) documents and is best suited for digitally converted documents. Note: If Drop Blank Pages is enabled. \001. By changing the "Blank Sensitivity" option. If no range file is specified. Scanned images may require a slightly less sensitive filter. creases. at least 1 page will always be retained even if all the pages are blank. Dirty White allows the document to contain a small amount of (non-white) data. So when updating. The path structure for the images will be re-created relative to the current folder in LAW. The Doculex import does not require the documents breaks to be defined in the database. it can be confusing and interfere with processing order.dbf or Doculex5. all records in the csv with a Status value of N (do not print) or D (duplicate) will be skipped during the import process.. Select File > Import > Load File and browse to the load file (*. A Doculex imagebase does not contain any index information so only page numbering will apply to the imported documents. creation of a separate folder for each volume is recommended as the folder structure will frequently be a sequential numeric format (e.

depending on the user selections in the Import Fields dialog. The Type field displays the field type for each field. The Destination Name column displays the name of the field that will be created or the existing field name in the LAW case. To exclude a field. 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. A list of fields found in the Summation load file will be displayed in this dialog. If the images have been copied to a local drive from a CD or the image directory notation (@I) has been used. Note: Summation load files do not contain page IDs (or Bates numbers) for every page. The Source Name column will list every field contained within the Summation load file. The type can be changed for new fields only.LAW PreDiscovery User Guide images. A Summation load file may contain index information for each document. Note: The user must select Yes to the prompt asking to include fields in order for this dialog to appear. OCR is also imported if it exists with the images. Fields listed in blue are new fields (do not already exist in the LAW case). This index information may or may not be imported. users must specify the directory in which the images are stored. If the load file uses CD volume notation (@V). LAW automatically numbers every page based on 106 . Both new and existing field names may be changed by doubleclicking in the cell and entering the desired name. LAW will attempt to find the CD drive letter that contains the images. LAW will also import any existing word list files (*. clear the check box in the Include column in the proper row. they can only contain a beginning document number and an ending document number.ocr) with images if they exist.

select File > Import > Load File and browse to the desired load file (*. images. The Type field displays the field type for each field.lfp). 107 . but this may not match the originals exactly if gaps or changes exist in the numbering scheme within the document. To exclude a field. select File > Import > Load File and browse to the desired load file (*. Note: The XML format is only available for import in ED-enabled LAW cases. The Destination Name column displays the name of the field that will be created or the existing field name in the LAW case. and image files referenced in the load file will be copied to their respective folders in LAW. To import an EDRM XML file. Fields listed in blue are new fields (do not already exist in the LAW case).Acquiring Documents the first page of the document. the text files will be imported as OCR text. only text associated with native or image files will be copied into LAW. An Import Fields dialog will appear allowing management of fields included in the XML file. Both new and existing field names may be changed by double-clicking in the cell and entering the desired name. IPRO Load File To import an IPRO volume. text. The Source Name column will list the fields contained within the load file. text. Any native. and metadata into an electronic discovery enabled LAW case. EDRM XML 1. If the "Link to source files in place when importing load files" option in Tools > Options > Preferences is enabled.0 The EDRM XML format can be used to import any combination of native. The type can be changed for new fields only. If text files matching the image filenames are found in the source directory. clear the check box in the Include column in the proper row.XML).

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

doc. such as speckles. In this example. this option instructs LAW to import any associated text files (*. folds..wpd. 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. the "MEMO" and "ABC0001" values can be stored with the newly created document. the DocType field has been selected to store the first "non-document break" barcode value ("MEMO"). Include OCR When enabled. support for these barcodes will be available in a future release of LAW.htm) that exist with the images.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. however. button. a barcode break sheet image contains three barcode values: DOCBREAK. and ABC0001. a new document will be created. 109 . Scanned images may require a slightly less sensitive filter.. If barcode break sheets are selected. creases. button to specify the "Sensitivity" for the blank page filter. *. Each time a barcode with the specified "Barcode Value" is detected. *.txt. 'Dirty White' allows the document to contain a small amount of (non-white) data.. 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. 'Pristine White' (recommended) is used for perfectly (all white) documents and is best suited for digitally converted documents. the value of the barcode to be used to break the documents must match the document break value specified in the Barcode Settings dialog. If two index fields are 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. MEMO. *. (recommended for scanned documents). click the More. etc.. Then. Note: This feature does not currently support Folder or Attachment barcode breaks. which may be launched by clicking the More. If blank pages are selected. For example.

separated by a period (e. 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. The selected images will then be imported into the currently selected folder in the folder list window. Note: This setting is ignored if the images are on a read-only source (e. Once the file limit has been reached.. AB0001.003. AB0001. Use filename as BegDoc# This setting causes the incoming images to be numbered according to their filenames. numbering them in this manner will cause duplicate page IDs.g. Note: LAW will not auto-increment the root image folder. Auto-increment folder This setting dumps all incoming images into the current folder until the specified "File Limit" has been reached. etc. AB0002. 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.###) will force a suffix padded with three digits.tif.LAW PreDiscovery User Guide Link to images in place When enabled. AB0001. leaving only the images that have not been imported. 110 .). The separator character can be modified or omitted and the number of pad digits can be adjusted with the format string.tif. Mirror original structure This setting causes the original folder structure to be rebuilt relative to the topmost selected folder(s). Store original location This setting can be used to store the path of the imported images in an index field.002.. a new folder is automatically created on the same level as the current folder and becomes the new image destination. The default setting (*.g.). LAW will link to the selected images in their current location rather than copy the files into the LAW case folder structure. If this setting is selected. CD-ROM). if the documents are multi-page images and have been named sequentially (e. at least one folder must exist under the root folder. This feature is very helpful if the images have been named according to their document numbers. the full path of the images (path and filename) will be stored in the specified field.. However.g. This feature is extremely useful when hard drive space is limited. If the same field is used for the filename and location. Store original filename This setting can be used to store the filenames of the imported images in an index field. AB0001. Users can resume at a later time without re-importing any of the same images. etc.

. If the image is modified in any way. 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. Scrolling the Image Once an image has been zoomed and cannot be entirely displayed in the image window. The Best Fit setting can also be quickly restored by double-clicking on the current image. As soon as the mouse is released. LAW even allows launching of the image in a separate viewer by selecting Tools > Launch Viewer. 111 . To activate the pan window. To reset all pages to the default mode of Best Fit.e. users must scroll the image to view different areas. Turn it off by selecting it again. When inspecting documents. LAW allows users to zoom in and out. Zoom Lock The Zoom Lock feature allows users to use the same zoom factor for all pages opened in LAW. otherwise. To zoom to a selected area. These settings are both available from the View menu by selecting Best Fit or Fit to Width. LAW gives users all basic image viewing capabilities provided with any image viewer. the area that it pans over is displayed in the main image window. a locking violation will occur. the image may be scrolled by holding the <Ctrl> key and using the arrow keys rather than the mouse. This feature is useful when inspecting a certain portion of all documents (i. users must first set the zoom lock by selecting Zoom Lock (Ctrl+Z) from the View menu. 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. LAW zooms to the area defined by the rectangle. When an image is zoomed in. view in grayscale. A small pan window with a black box that represents the zoomed portion of the current image will open. 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. When the zoom lock is activated. 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). lower right-hand corner for a Bates number). fit to width or window. the user will need to switch documents in LAW before saving changes. simply draw a rectangle (hold left mouse button down and drag mouse to opposite corner of rectangle).Image Display Image Display Viewing Images Images will appear in the Image display on LAW's main interface. The Best Fit setting is the default when opening images. Double-click to return to the "Best Fit" state. invert. Once the zoom lock is activated. The black box can be dragged in the pan window. 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. Pan Window The Pan Window feature provides another way to scroll the image. simply zoom to the desired area and all subsequent pages will be zoomed to the same approximate area. To use this feature. select View > Pan Window from the main menu. and utilize several other features to make image viewing as effective as possible. a small lock icon will be displayed on the Image button to remind users that it is enabled. simply select Best Fit while Zoom Lock is still enabled. horizontal and vertical scrollbars will appear. view thumbnails.

Last Page. the thumbnails view will display the page with the original orientation. select View > Invert from the main menu. Pages may be rotated automatically while scanning using the 'Output Rotation' setting (see Scan Options for more details). select File > Save (Ctrl+S) and the current orientation for all pages will be saved. it is for viewing purposes only. Invert To invert an image. If one or more pages are selected. only the current page will be rotated. Note that rotating an image is for viewing purposes only. Note: Rotating an image that has been endorsed by LAW may result in undesired results if the endorsement is later modified or removed. If no pages are selected. updating both the thumbnails and Image displays. all selected pages will be rotated the specified direction. This feature is for viewing only and does not alter the image in any way. Rotating Pages LAW allows users to rotate pages in the event that one or more pages are improperly oriented. The Page menu is available by right-clicking within the thumbnails display to make the page functions more readily accessible. Rotate one or more pages by selecting Page > Rotate Left (Ctrl+L). 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. 112 . 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. Previous. The Invert feature reverses the colors and clarifies the image. To save the rotation for the image.LAW PreDiscovery User Guide Viewer Options Scale to Gray The Scale to Gray setting makes images much clearer when viewed and is the default setting for LAW. select View > Scale to Gray from the main menu. This feature does not alter the image in any way. Pages may also be rotated during the quality control process if they were not corrected at scan time or were acquired from another source. Page Navigation LAW provides several ways to navigate between pages of multi-page documents. The main image window will display the current page with the new rotation setting. The First Page. The Goto Page (Ctrl+G) function from the Page menu will launch a dialog that enables users to jump to a specific page. however. To toggle this setting. Rotate Right (Ctrl+R). or Rotate 180. making them difficult to interpret. This feature is useful when viewing documents that have shaded or colored backgrounds. See Header/Footer Options for further information on endorsing.

or rotating certain pages of a document. select pages from the thumbnail display with a combination of the <Shift> and <Ctrl> keys. This requires the ability to select multiple pages of those documents to perform certain functions like deleting pages of a document. click either View > Thumbnails or View > Page and Thumbnails. making it easy to navigate and select pages for different functions. 113 .Image Display Thumbnails Display When performing quality control of documents. LAW provides several ways to select individual pages of a multi-page document. Selecting Pages When dealing with large sets of document images. The selected pages appear highlighted in black. To view thumbnails. the thumbnails display allows users to see a thumbnail of each page within a document. deskewing individual pages of a document. users will most likely be dealing with multi-page documents. If working with the mouse.

This makes it very easy to select pages if scrolling through the pages of a document using the arrow keys. 114 . 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. Pressing Ctrl+A will cause all documents in the document list to be selected if the document list has the focus. Holding the <Shift> key while selecting the first and last page of a range selects all pages in that range.LAW PreDiscovery User Guide Holding the <Ctrl> key while selecting the desired page with a left mouse click toggles the selection of that page. 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. LAW also allows users to select pages using only the keyboard to avoid switching back to the mouse.

115 .Image Display See the Page-level Cleanup topic for details on enhancing pages of a document.

The Page Properties dialog will provide the height and width of the image in both inches and pixels. This information is useful for determining file attributes. and the compression type for the current page. LAW does not display the actual file names for the images in the document list. For scanned or imported images (non-ED). Viewing Properties for Image Records Users may also view the properties for the actual image file rather than the current page only. For images created via the TIFF Conversion batch process. but users may need to determine the file names to troubleshoot certain issues. select Page > Properties from the main menu. 116 . the color format. These file names consist of the "ID" field in the database (zero-padded to 8 characters) with the image extension added. To view the properties for the current page. and the actual file name for the image. the resolution. To display the file properties for the current image. file size. select Edit > Properties from the main menu. A standard Windows file properties dialog will be displayed. the actual file name will be displayed in the page-level PageFilename field.LAW PreDiscovery User Guide 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. An information dialog similar to the following will be displayed.

If an image does exist in addition to a native file.Image Display Viewing File Properties for Native Records For records that have associated native files but no associated images. this can be accomplished by right-clicking the native file's hyperlink (located above the Image display) and selecting Properties. if the user needs to view the native file properties for a record with both an image and a native file. 117 . the image properties will be shown by default. the native file properties will appear when choosing Edit > Properties from the main menu. However.

with certain options having buttons on the toolbar and/or shortcut key combinations as well. Black-Border Removal: The Black-Border Removal filter will remove black edges. it is due to the scanner model being used and the scan area will have to be adjusted in order to remove them. it will not be dropped. In order for holes to be removed. circular holes (partial holes will not be removed). bold e’s and o’s can appear to the filter as holes and be accidentally removed from the document. Deskew: The Deskew process is used to straighten images that show a slant from their correct orientation. If receiving borders like this. If multiple pages are selected.or page-level.Manipulating Documents Manipulating Documents Page-Level Cleanup Image enhancements such as Deskew or rotating pages may be performed at a document. Hole Removal: The Hole Removal filter removes black holes from pages such as those left by scanning 3-hole punched pages. As such. Deskew To manually deskew a page. so this filter should be selected if using the 'Drop Blank Pages' scan option. This filter will pick up only even black edges. which also appears when right-clicking a page in the thumbnail display. If the black edge is uneven or slanted down the page. Skewing occurs if the original document was unevenly pulled when it was fed into the scanner. 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. 119 . providing image enhancement options. Black borders left on pages can prevent LAW from recognizing blank pages. then all selected pages will be deskewed. Warning: When using the hole-removal filter. they must be complete. depending on the quality of the image and fonts. The scan area can be adjusted from the Scanner Settings dialog. it is a crucial step in the quality control process. only the current page will be deskewed. If no pages are selected. Enhancing Images Select Page > Enhance Image from the main form to launch the Select Image Filters dialog. Deskewing an image makes the image contents more legible and can drastically improve OCR results. Page-level options are found in the Page menu. The blackborder removal filter can also be applied to multiple documents during Batch Processing. select Page > Deskew (<F4>).

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. the thumbnail view will display the page with the original orientation.LAW PreDiscovery User Guide Line Removal: The Line Removal filter removes black lines from pages and is subject to the same requirements as the black-border removal filter. OCR results may improve if Noise Removal is performed on a document before converting it to text. so uneven or slanted lines will not be dropped. Note: Rotating an image that has been endorsed by LAW may result in undesired results if the endorsement is later modified or removed. updating both the thumbnail and page displays. See Header/Footer Options for further information on endorsing. Pages may be rotated automatically while scanning using the 'Output Rotation' setting (see Scan Options for more details). select File > Save (Ctrl+S) and the current orientation for all pages will be saved. however. If one or more pages are selected. Rotate one or more pages by selecting Page > Rotate Left (Ctrl+L). 120 . Pages may also be rotated during the quality control process if they were not corrected at scan time or were acquired from another source. To save the rotation for the image. The filter will pick up even black lines only. If no pages are selected. The main image window will display the current page with the new rotation setting. It is important to note that rotating an image is for viewing purposes only. only the current page will be rotated. Rotate Right(Ctrl+R). Rotate Pages LAW allows users to rotate pages in the event that one or more pages are improperly oriented. all selected pages will be rotated the specified direction. or Rotate 180.

121 . 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. or pressing Ctrl+A to select all documents in the current folder. Note: Moving pages in the thumbnails display is not currently supported for any image records stored as singlepage. Multiple documents can be selected from the document list by holding the <Ctrl> key while selecting individual documents. however. If the documents are being moved into an empty folder. See the Establishing Folder Structures topic for more information. An alternative to selecting all documents in a folder and using the Move Documents function would be to use the Move Folder function. The following dialog appears and allows users to select an insertion point for the documents: Once the dialog appears. If the thumbnails are not currently visible.Manipulating Documents Moving Documents/Pages In the event that documents are saved to the wrong folder. Moving Documents To move one or more documents located in the same folder. LAW allows documents to be moved between folders. select the desired page(s) from the thumbnail display. To move a page (or pages). this setting is ignored. the insertion point cannot be one of the selected documents. Moving Pages Pages can be moved within a single document by selecting a document and viewing the thumbnails display on LAW's main interface. Note: Documents can be moved within the same folder. click View > Thumbnails or View > Page and Thumbnails to display them. Note: Document list must have the focus in order for Ctrl+A to select all documents. holding the <Shift> while selecting the first and last documents in a range. This enables users to rearrange documents that may have been scanned into the wrong folder or group documents from one or more folders together. browse normally between folders and documents and then click the Insert button when the proper insertion point is found. If the documents are being moved into a folder with existing documents and a document is not selected. The "Before Current" and "After Current" settings indicate whether the selected documents should be inserted before or after the current document. select the document(s) to be moved and select Edit > Move Document(s) from the main menu. located in the Folder menu. The Edit menu is also available by right-clicking on the document list for easy access. LAW will prompt the user to select one. left-click on any of the highlighted pages (the icon will change) and drag the cursor to the selected insertion point.

so pages may need to be renumbered after the move. 122 . etc. otherwise. header/footer size.LAW PreDiscovery User Guide Warning: This feature does not currently move any page information (page ID. unexpected results may occur if re-endorsed.). Pages should ONLY be moved within a document in which all or no pages have been endorsed with the same settings. Also note that since header/footer size info will not be moved.

From the standalone grid. For more information on the grids. select Edit > Delete > Page(s) (Shift+Del). 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. use the Delete key or toolbar button. <<< Page 1 >>>). choose Edit > Delete Record(s) to delete any selected records or use the Delete key or toolbar button. When utilizing the embedded grid. or specific pages from a document. Note: If an image has associated OCR text. Deleting Records from the Grid Displays Another method of deleting records is to use one of the two available grid displays in LAW. LAW allows both types of deletion directly from the main form. choose Tools > Display All Records. Pressing Ctrl+A while the document list has the focus will select all documents in the current folder. Users can delete one or more documents. select the document(s) to be deleted from the document list. users may need to remove pages or entire documents for various reasons.Manipulating Documents Deleting Documents/Pages When dealing with large volumes of records. and any OCR files associated with that document. To delete pages from a document. Once the desired documents are selected. Deleting Pages Users have the option to delete the current page. The following verification screen will appear.. see the following sections: 123 . choose Edit > Delete > Document(s) or press the Delete key or toolbar button. Deleting Documents To delete one or more documents. a page range. Clicking the Yes button will delete the selected document(s). 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. Deleting a document deletes the image and/or native file. or selected pages when deleting pages from a single image record. The Selected Pages option will only be available if one or more pages have already been selected in the thumbnails display. an entire range of pages in a document. 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. To launch a grid.e. the database reference.

LAW PreDiscovery User Guide Launching the Grids Customizing Grid Views 124 .

so any duplicate values will automatically be cleared.All field data populated during an ED import associated with the original record will be discarded permanently. This may cause duplicate values if unique fields are defined. the document(s) may need to be split.Manipulating Documents 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. See below for information on metadata handling for ED records. select the desired document and press (Ctrl+U) or Edit > Split Document from the main menu. Copy to all records . the same native file will be converted for each of the records involved in the split. with the exception of the DocID field. all new records will point to the same file. 125 . The native file is NOT copied. the index information from the original document is applied to all new documents. The Edit menu is also available by right-clicking on the document list for easy access. If the selected image 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. For new records beyond the first record. meaning the native file was imported with ED Loader and converted to TIFF in LAW. Because of this behavior. The Split Document function can be used to split a document based on barcode pages. metadata pulled from the native file. Three Metadata Retention options for splitting ED records are: Discard all metadata . or selected pages. This function is commonly used when scanning documents as quickly as possible and determining document breaks in a separate process. Note: For non-ED records. blank pages. the "Metadata Options" in the Split Document dialog will apply. every page. Note: All records created after the split (including the first record) will lose the value used to indicate the file is an ED record. this native file link is created by placing the path to the native file into the "NativeFile" field in the LAW case.All index field data associated with the original record will be inherited by all records created as a result of the split. if the newly split records are included in a TIFF conversion process. This includes important values used to indicate duplicate record status. and ED Loader session information. The original native file will be associated with all new records. To split a document.

Click the Configure button for blank page filter options. 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. See the Using Barcodes topic for additional barcode information. the barcode will always be deleted from the image after being processed. The settings for the break sheets can be specified from the Imaging tab of the Options form. If no blank pages are found. enable the "Auto number remaining DocID's" setting in the Split Document dialog and enter the value in the "Starting Suffix" field. If no pages with barcode breaks are found. the operation is cancelled. speckles. The default is ".g.002". Users also have the option to auto-number DocID values with a suffix for records created as a result of the split operation. 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. Split Options Barcode Break Sheets If this setting is selected. record. Blank Pages This setting causes LAW to scan for any blank pages within the specified document.LAW PreDiscovery User Guide Copy to first record only . creases. The suffix will increment by one for each record. the document will be scanned for barcode break sheets.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 attachment barcode break sheet can also be detected using this feature and will create attachments accordingly. 126 . LAW will split the document if a document break is detected or create a new folder if a folder break is detected. Pristine White is used for perfectly (all white) documents and is best suited for digitally converted documents. or original. Every Page This setting causes every page of the document to be split into its own single-page document. Dirty White allows the document to contain a small amount of (non-white) data e. and folds (recommended for scanned documents). Click the Configure button for more supported barcode settings and types. Scanned images may require a slightly less sensitive filter. Other userdefined index field data will be retained for all records. This setting may be useful if the 'Detect Barcode Breaks' scan option was inadvertently disabled while scanning. Any blank pages that are found will be used as the separator pages and dropped. For each barcode break sheet detected. To use this feature.. the operation will be cancelled.

Manipulating Documents Selected Pages This setting causes all selected pages to be used as the starting page of new documents. This will also be the case if barcode break sheets or blank pages as the separator pages are manually selected. selection of this page is not necessary. 127 . prior to splitting) is automatically included as the start of the first sub-document. Because the first page (of the current document. This setting is only available if one or more pages are selected when the function is activated. The "Drop selected pages" setting causes all selected pages to be dropped.

the index information for the first document will be used as index information for the new document. select the documents to be merged. If a single document is selected. The Edit menu is also available by right-clicking on the document list for easy access. the image file has to be physically rebuilt. the Move Documents function may be used to move them into the same folder. The documents will be merged in the same order they appear in the document list. may also be merged with other image records in a case.000 pages. the average time per page increases. Be sure to verify this information after the merge. LAW can typically merge 100 pages in less than 5 seconds. move the documents prior to the merge operation. Once the documents are selected. ED records. This process can be cancelled at any time by pressing the <Esc> key. Multiple documents can be selected from the document list by holding the <Ctrl> key while selecting individual documents. meaning records imported with ED Loader that have been converted to TIFF in LAW. All Page ID information for the pages will be retained when merging documents. making the process somewhat slower once users approach 1. To merge them in a different order. holding the <Shift> key while selecting the first and last documents in a range.LAW PreDiscovery User Guide 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. To merge two or more documents. or pressing Ctrl+A to select all documents in the current folder. however. select Edit > Merge Documents or Ctrl+M. Note: The document list must have the focus in order for Ctrl+A to select documents. 128 . Use caution when merging ED records as important metadata and file links may be lost depending how the documents are merged. Because LAW stores multi-page documents in multi-page image format. If documents in different folders need to be merged. but as the number of pages increases. 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. the Merge Documents menu item will not be enabled. The documents to be merged must be located in the same folder.

Inserting Documents LAW allows users to insert documents in a particular place within the current folder by selecting Edit > Insert > Scanned Document(s). scanned pages. exports) are executed in scan order. For information regarding the Insert->E-Document feature. see the Inserting Electronic Documents topic. all processing functions (batch processing. The inserted document will be placed above the currently selected document.Manipulating Documents Inserting Document/Pages LAW allows users to insert scanned documents. To insert a page. was skipped during the initial scan process. Inserting Pages Inserting a page is often used when a page. click View > Thumbnails or View > Page and Thumbnails. and existing images in the desired locations within the current folder. If thumbnails are not displayed. unless documents are specified by a query. This feature is very important because. 129 . 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. Users can insert a document that was missed at scan time. first select the thumbnails display on the main form. for example. such as the back of a page.

LAW also allows the insertion of existing images. To insert a page. Inserting Existing Pages In addition to inserting scanned documents and pages. To use this feature. The image will be inserted as a document above the currently selected document. first select the page the inserted page will precede and highlight it by pressing the space bar. see the Inserting Electronic Documents topic. In the example above.LAW PreDiscovery User Guide LAW will always insert a page or document prior to the one highlighted. select Edit > Insert > New Page(s) from the menu. For information regarding the Insert > E-Document feature. 130 . click Edit > Insert > Existing Page(s). browse to the image file to be inserted and click Open. the new page will be inserted between pages 21 and 22. Next.

Manipulating Documents Replacing Document/Pages A document or page is commonly replaced when the image of a page or pages is poor. Replacing a Document Select the document to be replaced in the document list. first select the thumbnails display on the main form. The Replace feature simply replaces a page or document that already exists in the case. Choosing OK at the prompt will replace the selected document. 131 . click View > Thumbnails or View > Page and Thumbnails. If thumbnails are not displayed. 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. Insert the replacement document into the scanner and select Edit > Replace > Document from the main menu.

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. Choosing OK at the prompt will replace the selected page.LAW PreDiscovery User Guide Select the page to be replaced and highlight it by pressing the space bar. To use this feature. 132 . Browse to the desired image file and click Open to replace the current document with the new image file. click the document to be replaced and choose Edit > Replace > Image from File(s). Insert the replacement page into the scanner and select Edit > Replace > Page(s) from the main menu.

Manipulating Documents

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

LAW PreDiscovery User Guide

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

Manipulating Documents

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

LAW PreDiscovery User Guide

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

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 Extraction Yes Yes Yes Yes Yes Yes Yes Reads the page count from the image. Uses the alternate HTML engine to calculate page counts. Therefore, the output may not exactly match the output printed with Internet Explorer. Additional Notes

Adobe Acrobat AutoVue Suite Binary/Hex Printer Corel WordPerfect eDrawings Viewer Image Printer Internet Explorer

137

LAW PreDiscovery User Guide

Microsoft Excel Microsoft Outlook Microsoft PowerPoint Microsoft Visio Microsoft Word Quick View Plus Shell Printer Snapshot Viewer Text/RTF Printer VoloView Express <No Source Specified>

Yes No Yes Yes Yes No No Yes Yes Yes No Always returns a page count of 1. 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

Working with Native Documents

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

To choose an application.. click the downward pointing arrow located beside the Open File button. If no application is assigned in the OS. choose one of the popular applications in the list to view the file in that application or select "Choose Program. If the value is set to "<No Source Specified>". or a text editor (see above section for details). LAW will attempt to launch the file in the application assigned to this file type in the operating system. The change will affect the TIFF/E-Print process since the SourceApp values determine the application used when printing or converting the file. 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." to select any other application installed on the computer. the file will launch in the application that is specified for that document in the SourceApp index field. The native file may also be launched by right-clicking the hyperlink and selecting Open. this option provides more control as it allows the user to choose the application with which to open the native file. This field is populated automatically during an ED Loader session and is based on the specifications in the file type database. Another option available in the Open File drop-down list is Change Source Application.LAW PreDiscovery User Guide 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. LAW will attempt to launch the file in a text editor. 140 .. 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. This option can be used to change the value listed in the SourceApp field for the current document. Next. in the operating system. However.

Native E-Mail Review Lotus Notes and Outlook e-mail messages may be launched in their respective native applications after import into 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. For records containing native files. 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. Selecting AutoVue Review Mode opens the file in AutoVue. Selecting Quick View Plus Review Mode from the Open File drop-down list opens the native file in Quick View Plus. or parent. If a user needs to quickly locate a native file outside of LAW. the native file review mode options are ignored since native files do not exist for these record types. messages in mail stores as well as top-level loose messages (MSG and EML) on disk. then the path to the native file would be <case root>\$EDD\$NativeFiles\00\00\12\34. Note: The mail stores and loose messages MUST be in their original locations from which they were processed by the ED Loader. The selected review mode application needs to be installed to use this option. if a record's ID value is 1234.Working with Native Documents 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. If they have been moved. 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. regardless of how ED Loader converted the file during the import process. If this occurs. Another method of locating a native file for a particular record is to view the ID field in LAW. the ID field value will make up the folder structure for the native file (relative to the $NativeFiles folder). click the arrow to the right of the Open File button located above the image display and then click Review Parent E-Mails Natively. for example. With the option now checked.DOC file in this example). LAW will not be able to locate them when attempting to launch the native e-mail. This feature supports top-level. If using Quick View Plus version 9 or later. When selecting non-EDD records. To enable this feature. The active record's DocID is displayed in the title bar.DOC (file is a Word . 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. closing the previously opened record. 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. 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.NTV. This launches the folder that contains the native file with the native file already selected for easy access. Each record opens in the same window.NTV. 141 . 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.Understanding how this function works will allow users to browse to the native files when not using the Open Containing Folder option. please see Avantstar's license agreement prior to using this application with LAW. an ID value of 1 for a native record would result in a native path of 00\00\00\01. For example.DOC. Note: ID values are padded with zeroes to form an 8-digit number when used for this purpose.

142 . the ED Loader will appear in "Insert Mode." For information about placement of the inserted documents.LAW PreDiscovery User Guide 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. Edit > Insert > E-Document Attachment(s) > Before Current .Inserts record(s) before currently selected record. Edit > Insert > E-Document(s) > After Current .Inserts record(s) after currently selected record. click the Details button. The Insert Mode Details dialog will appear. Four insert modes are available: Edit > Insert > E-Document(s) > Before Current .Inserts record(s) as attachment to the currently selected record.Inserts record(s) as attachment to the record before the currently selected record. Edit > Insert > E-Document Attachment(s) > After Current . After selecting one of the above options.

Working with Native Documents This screen will indicate where the document is to be placed. 143 . Select the file(s) to be inserted to add them to the Source Queue. Ensure the information is correct and then click OK. Set any desired options in the Settings tab. The value will be set to the folder that was selected when choosing to insert an e-document. Note: The Default Target Folder setting cannot be configured inserting e-documents. Click Start and click OK on the Confirm Settings dialog to initialize the import process. The selected file(s) will be imported into the specified location in the case.

LAW PreDiscovery User Guide

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

Working with Native Documents

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

LAW PreDiscovery User Guide

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

LAW PreDiscovery User Guide

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

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

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

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.

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

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). choose Grid Views > Manage Grid Views > Tools > Grid Colors. and grid text colors may be customized for each profile. right-click any cell in that column and choose Send Column Right-most. To move a field to the right-most position in the grid. 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). grid line colors. select or deselect the boxes beside the fields. Changing Grid Colors Row colors (odd and even). The Field List may also be accessed by right-clicking on any column header. To move a field to the left-most position in the grid. click View > Field List. When the Field List dialog appears. To show all or hide all. To choose fields to display. Selecting Fields to Display Grid profiles will store all fields visible in the grid. selecting a profile from the Views section and clicking Done.LAW PreDiscovery User Guide bar) and choose the desired profile from the list. right-click within this dialog and choose either Show All Fields (Ctrl+A) or Hide All Fields (Ctrl+X). right-click any cell in that column and choose Send Column Left-most. To move a field. 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 change the colors from the grid display. An alternate profile may also be selected by clicking Grid Views > Manage Views. 152 .

then it may be deleted by any user that enters the case. only that user will be able to delete the profile. If a profile was created at a user level.Grid Displays When the Grid Colors dialog appears. If a profile's scope is Shared or Global. make the desired selections for each item and click OK. launch a grid display and click Grid Views > Manage Views. Choose the profile to delete from the Views section and click Edit > Delete. To delete a profile. 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. 153 .

users may sort the records based on visible index fields. click within any cell in the column for the desired field. Sorting Records Once records have been returned to the embedded or standalone grid. click Tools > Sort Records > Advanced Sort or click the Advanced Sort button on the toolbar ( standalone grid display. while the embedded grid is part of LAW's main user interface. To choose fields to display. it is important to become familiar with the grid displays in LAW. viewing and working with query results. A different sort direction may be specified for each of the four fields: ascending or descending. When the Field List dialog appears. filtering. and then click either the Ascending ( ) or Descending ( ) button located on the grid toolbar or choose Tools> Sort Records > Ascending | Descending (standalone grid only). The Field List may also be accessed by right-clicking on any column header. ) from within the 154 . 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. To show all or hide all. This topic will cover a number of functions available within these grid displays. To access this feature. There are two grids available: standalone and embedded. click View > Field List. select or deselect the boxes beside the 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. and tagging. The Advanced Sort dialog will appear.LAW PreDiscovery User Guide Grid Functions The grid displays are often used for quality control. The standalone grid is launched in a separate window. Sorting by a Single Index Field To sort records using a single index field. Before reviewing data and documents. right-click within this dialog and choose either Show All Fields (Ctrl+A) or Hide All Fields (Ctrl+X). Selecting Fields to Display Grid profiles will store all fields visible in the grid.

For example.Grid Displays Choose fields from one or more of the drop-down lists. Saving Records to File The visible field data associated with records displayed in the grids may be saved to a *. Click OK to apply the sort to the current set of records.TXT or *. See the "Selecting Fields to Display" section in this topic to learn how to display and hide fields. then by From (Descending). then by Importance (Descending). then by EDFolder (Ascending). 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.CSV file. Only fields visible in the grid will be included in the output file. Once the desired records have been returned to the grid and fields have been chosen. in the above image. click File > Save or click the Save button in the toolbar. records would first be sorted by DateSent in Ascending order. This feature can be useful for a number of reasons including import into a different application or review by another party. The Save Options dialog will appear. 155 .

If no records are highlighted. 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 Browse to change the location and file name of the output file if the default value (<current case path>\results. 156 . Use the Print Preview To print only selected record(s). In the Text format drop-down. Unicode UCS-2 (Tab delimited). Only fields visible in the grid will be included in the output. The text format may also be specified from the "Save as type" dropdown after clicking Browse to choose a new location and/or file name Note: In order to view Unicode in Microsoft Excel. The total number of records to be written to the file will be shown in this section below the two aforementioned options. Click the box to enable the delimiter selections. The Save all records option would save all records currently shown in the grid to the output file. then specify the desired characters for Field (separates each field in the file). LAW will prompt to open the TXT or CSV file for viewing after the file has been written. Text (wraps the values in each field). To restore LAW's default delimiters and discard any changes that were made. The available options are: CSV (Comma delimited). change any necessary printer settings. Once the above options have been set. the Unicode UCS-2 (Tab delimited) text format must be used.LAW PreDiscovery User Guide In the Output Filename section. Choose a printer. and Newline (to replace hard and soft returns found within the field values). click the Restore Defaults button. 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. Unicode UTF-8 (Tab delimited).<ext. 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. Text (Tab delimited). and click OK. 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. Printing Records The visible field data associated with records displayed in the grids may be printed to file or paper. See the "Selecting Fields to Display" section to learn how to display and hide fields. choose the desired format for the output file. Then.>) is not acceptable. The Save selected records option would include any records that are highlighted in the grid. The default values can also be restored by deselecting the Override Default Delimiters option. 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. click the Save button to create the file.

The Remove Field button will allow the removal of an update entry from the dialog. Batch Updating LAW allows users to track information about records to aid in retrieval. button in To update fields for multiple documents. Return only records that are to be updated using the Batch Update feature. Choose a field and then enter the desired Value in the cell beside it (Value column). Deleting Records Records in LAW. or highlight the entire row. Choose a printer.Grid Displays To print all records visible in the grid. LAW will report the number of records updated. choose an additional field from the new cell that appears in the Field column. 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. and enter a value. The Batch Update dialog will appear. unique identifier to all or a subset of documents in a case. launch the desired grid using one of the methods discussed in the Launching the Grids section. click the Add Field button. and 157 . To update fields for multiple documents from within a grid display. 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. click OK. This feature could be used to assign a new. click within a cell in the row of the record to be deleted. 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. click Edit > Batch Update in the standalone grid or click the the standalone or embedded grid toolbar. choose File > Print > Print All or click the Print button in either grid toolbar and choose Print All. along with their associated files and field data. can be permanently deleted from the standalone grid. To update multiple fields at once. After entering all desired information for the current set of records. change any necessary printer settings. and click OK. To delete a single record.

Documents: 660 / Pages: 21. Rows may need to be adjusted in order to see multiple lines of data in the cells.. To move columns. 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. the data is collected and placed into a table that is built on the fly when this setting is invoked and therefore.166). when opening either grid or when returning records from the query builder. and Cells Columns and rows can be manipulated in a number of ways to make certain aspects of quality control easier and more efficient. right-click any cell in that column and choose Send Column Left-most. This menu item controls this feature for both the standalone grid and the embedded grid. position the mouse pointer between two rows until the resize cursor appears and then click and drag until the desired row height is obtained. please see the Field Descriptions topic. to another location in the grid. Rows. The document and page counts will then appear in the lower right corner of the grid (e. highlight the source column by clicking the column header. AttRange. Click Yes to proceed with the copy. Warning: Use extreme caution when deleting records as the operation CANNOT be undone. Individual columns can be sized in a similar manner. The percentage complete will appear in the title bar of the standalone grid. this feature will introduce a slight delay. Position the mouse pointer to the right of the column to be sized and then click and drag until the desired width is obtained. Warning: Copying data into a field of a different type (e. and then click Edit > Paste. To prevent this delay. Due to its dynamic nature. To move a field to the right-most position in the grid. this number will be the total number of pages instead. or fields. The contents of a field. right-click a cell in that column and choose Shrink Column to Window first and then resize the column if needed. To resize the rows. or column. relative to the size of the case. 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. Warning: Since additional time is needed to calculate the total documents and total pages information. the fields may not appear for several seconds (longer on larger cases). memo to text) in this manner could result in a loss of data. simply disable this setting via the standalone grid under View > Doc/Page Totals. If unable to position the mouse in this manner due to the column lining up with the edge of the grid window. right-click any cell in that column and choose Send Column Right-most. To display both the document count and the total of pages associated with the documents in the current query. Red arrows will indicate the new field placement prior to "dropping" the field (or releasing the mouse button). highlight the target column by clicking the column header. For more information about these fields. Next. 158 . Working with Columns. click View > Doc/Page Totals within the standalone grid.g.g. If a page-level query was executed. The four fields displayed are: BegAttach. LAW will not allow the copying of data into locked or system fields. To move a field to the left-most position in the grid. Click Edit > Copy.LAW PreDiscovery User Guide then click Edit > Delete Record(s) in the standalone grid. click and hold the column header and then drag the field to the desired location. Click Yes on the warning message box to permanently delete the record or records. and Attachmt. Viewing Attachment Fields Four fields containing information related to attachments can be generated by clicking View > Attachment Fields in the standalone grid. EndAttach.

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

LAW will report this in a message box and return to the grid. LAW will ignore the unsupported files and proceed with the launching the Create Outlook PST dialog.LAW PreDiscovery User Guide If the BegDoc# is not populated for the images in an ED-enabled case. Provided supported message records exist in the grid when this feature is invoked. LAW will offer to launch the control list file once it has been created. This feature is located in the standalone grid which means only records currently loaded in the grid will be included. click Tools > Create Outlook PST. provided they match one or more of the aforementioned message types..eml) on disk.. regardless of whether or not these attachment records are shown in the grid. and loose RFC-822 messages (*. Next. If both exist in the grid at the same time. loose Outlook messages (*.LST and can be viewed in any text editor. Lastly.. If no supported message records exist in the record set. Creating Outlook PST Files LAW can create Outlook PST files for messages imported from Outlook mail stores. the DocID field will be used automatically.msg). the Create Outlook PST dialog will appear next.any attachments to these messages will be part of the parent items. Only top-level messages and loose e-mail items will be added when creating a store . 160 . The file extension is . To create an Outlook PST file. first load the desired records into the standalone grid (see Launching the Grids).

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. simply key the desired values into the text box or boxes. If they have been moved. elapsed time.Grid Displays Click the Browse button to specify a path and file name for the new PST. The Create Outlook PST feature creates new PSTs (or appends existing) by accessing these original stores and/or loose messages. Error logs are stored in the root of the case folder in a file named pst errors.txt. LAW will present a list of mail stores that have been moved when invoking the menu item in the grid. the number of errors. 161 . Once the output path and root folders have been specified. These values will be used as the root folders in the output PST file. LAW will report the total number of top-level messages added. The Root Output Folders area below the output path contains two columns. LAW will not be able to locate them and the new PST files cannot be generated. LAW will present an option to either append to or overwrite that file. 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. and average speed. click OK to begin generating the PST. If errors occurred during the process. The title bar of this dialog will display the percentage completed and once the process is complete. Note: The mail stores and loose messages MUST be in their original locations from which they were processed by the ED Loader. If an existing PST is selected. the error log may be launched from the status screen as well. To change any of these default folders.

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. For information on resetting OCR text flags. please see the Flagging Documents/Pages for OCR topic. or added to a custom dictionary file (custom. ensure the user-defined. To generate this summary. These functions are explained in other topics in this help file. Prior to starting the spell check. replaced. please see the Full Text Indexing topic. Next. Spell Checking The spell check feature can be used to locate misspelled words within index fields in the LAW case. and the total number of fields associated with the currently displayed documents that are coded with information. When invoked. unlocked field to be searched is visible in the standalone or embedded grid display. total number of pages associated with the documents currently displayed in the grid. then click Tools > Summary from the standalone grid. System and locked fields cannot be accessed for the spell check. Generating an Index Summary An index summary can be performed from the standalone grid. 162 .dic in LAW50 folder). load the desired records into the grid (see Launching the Grids). For information on resetting OCR text flags. this feature will display a message box containing three pieces of information: total number of documents currently displayed in the grid.LAW PreDiscovery User Guide 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.

and a user wishes to remove all groups at once.. right-click on any of the groups and choose either Expand All Groups or Collapse All Groups. Click and hold the column header for the chosen field. click the minus sign (-). To expand an individual group.Searching Searching Grouping The grouping feature allows users to organize records based on field values. The number of records that contain a particular value is listed beside the value for each group. Up to four levels of grouping may be applied at one time. click and drag the column header from the grouping area to the area containing the column headers. To collapse an individual group. simply choose another field and click and drag the field into the grouping area. DocExt). launch one of the grid views (standalone or embedded) and determine the field to be grouped (e. simply right-click on any grouping in the grid and choose Clear All Groups. When a top-level group is expanded.g. Removing Groups To clear a grouping. To expand or collapse all groups at once. If multiple groups are applied. and release the mouse button. 163 . To add a second level of grouping. drag it into the grouping area located just above the column headers ("Drag a column header here to group by that column" area). Documents will then be grouped by each unique value found in that field. This feature is useful when users wish to locate specific values in a field and review those records. a second grouping will appear below it. To group records. click the plus sign (+).

However. 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. Note: The grid displays do not currently support Unicode. To view the filtering options. Unicode data can be displayed by resting your pointer over a cell containing Unicode. right-click on any cell in the field column. first launch the desired grid display. Choosing Filter by Selection will only return the records containing the selected value to the grid. 164 .LAW PreDiscovery User Guide Filtering Documents may be filtered in the grids based on values present in the index fields. The Unicode data appears in a pop-up text box beside the cell. This feature allows users to choose any field value in the current case and quickly locate any records with that same value. Choose a field to be used when filtering such as DocExt and ensure it is displayed (View > Field List).

Removing Filters LAW allows users to easily remove the filter and return the original set of records when needed.Searching Choosing Filter Excluding Selection will only return the records that do NOT contain the selected value to the grid. 165 . The filtering options will appear. To remove a filter. right-click on any record in the filtered grid. Users may continue performing filters on the filtered sets as needed. simply launch the Batch Process or Export Utility from the grid. Note: To process the filtered documents. only the current record set will be selected for processing.

LAW PreDiscovery User Guide Choosing Remove Filter will return the original record set that was loaded prior to the first filter performed in the grid. 166 .

To launch the Query Builder. 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. 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. select Tools > Search Records from the main menu or click the binoculars ( on the main toolbar. and searching any fields in a case. using clauses within searches.Searching Query Builder It is common for clients to request that documents are produced based on certain criteria. saving common queries to re-execute as needed. Benefits of the Query Builder tool include the ability to build advanced searches by adding multiple conditions. ) icon 167 . The Database Query Builder dialog will appear.

The grid view will display a record for every page of each document. Additional page-level fields also become available after selecting this option.less than specified value Greater or Equal . To clear all items from the current list. click the Add Condition button to add the search criteria to the current list.This setting will display documents matching the specified search criteria and will also display any parents or attachments of those documents.does not equal specified value (NOT case sensitive) Greater Than . Available operators are: Equals . and "?" for any single character) can be used with the "Equals" and "Does Not Equal" operators. Return parent/attachment groups .greater than or equal to specified value Lesser or Equal . Note: Due to the nature of this query. click the Remove All button. Field Name The Field Name drop-down lists all of the index fields in the current case. Once the first condition has been added. an operator. setting this option may take significantly longer to return results than without it on larger cases. depending on the desired result of the search.greater than specified value Less Than . Select the field to be searched from this list. The Value field will be removed if either of these operators is selected. Once this is done. Returning Additional Records Return all Page ID's with query results .Select this option to return a page-level query for the returned documents. users must select a field name. Wildcard characters ("*" for any string of characters. The "Is Empty" and "Is Not Empty" operators do not require a value. and a value (for most operators). select either "AND" or "OR" from the Join drop-down to specify another condition.matches specified value (NOT case sensitive) Does Not Equal . however. 168 . This does not imply that both the parent/attachments also match the search criteria. Operator The Operator determines what type of search to apply for the specified value. Removing Conditions To remove an existing condition. select it from the list of current conditions and click the Remove button. the query will return all records in the current case.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. Note: If there are no items in the list of current conditions and the user clicks the Accept button.less than or equal to specified value Is Empty .LAW PreDiscovery User Guide Specifying Search Criteria To add search criteria.

a query that returns all or an excessive number of records could potentially lock the database for several minutes.Available to any user in any LAW case. When SQL Server executes a query that returns a large number of records. is available for SQL cases to improve query performance. when executing a query that will be used to run a batch process or export. The user and shared queries are stored in the case folder structure ($UserData). table lock is generally not an issue since the lock is for a very short period. Global . "Use NOLOCK setting to improve performance (SQL only/read-only)". Shared . Using this setting instructs SQL Server to not lock records while the query is being executed. This can block batch processing. exports. More importantly. depending on the selected storage level. With smaller cases.Searching NOLOCK Setting The setting. The performance of the query is slightly improved. Saving Queries Once a particular query is identified. while global queries are stored in <application path>\Shared. The Save As dialog will appear. because locking is not used. for example. When a table lock is active.Available to any user in the LAW case in which the query was saved. The default storage location for global queries and profiles can be changed via the Preferences tab in Tools > Options. The NOLOCK setting should only be used in cases where updates in the grid are not necessary. updates cannot be performed in LAW. it will often escalate to a table lock to improve performance. Three storage levels are available when saving queries: User .Available to the current user in the current case. Enter a name for the query (must be a valid filename) and a description (optional). Click Accept. However. As cases scale to several million records. 169 . and any other process that updates the database. the result set is read-only and updates will not be available in the grid. 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. it does not block database updates by other users. it can be saved by selecting File > Save from the Database Query Builder dialog.

and global grid profiles. global index field profiles. 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. click the Saved Filters tab from the Database Query Builder dialog. and filters option to select a new storage location.LAW PreDiscovery User Guide Click the Browse button beside the Path for global field profiles. Changing this path will affect saved global queries. 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. ) 170 . Next. grid views.

Searching Choose from User. Shared. The query results will be returned in one of the grid displays. 171 . This value will determine which queries will be displayed in the form. Double-click on the Title (or right-click > Open) to apply the query to the Advanced tab. 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. click Execute. Global. On the Advanced tab. Click on a query's Title to view a Description and Preview of the selected filter. or All Available Views in the Storage Level/Scope drop-down.

please see the Full Text Searching topic. Note: For information on executing full text searches. It will be loaded into the Advanced tab. the documents to be processed may be changed using the folder selection options within each of these utilities. Click Execute. When the Batch Process or Export Utility is executed while a set of records is displayed in the grid. 172 .LAW PreDiscovery User Guide The queries in the search history may be re-executed by simply double-clicking the desired query in the Request column. the records may be flagged (see the Tagging Documents topic) and sent for further processing. If needed. only that record set will be selected for processing. Once the desired records have been returned in the grid.

please see the Full Text Indexing section for more information. These options may be accessed by clicking the Options button within the Database Query Builder dialog or within the Fulltext Dictionary dialog. Character ? * % ~ Meaning matches any character matches any number of characters fuzzy search stemming 173 . the special directives listed below can be used. The records in LAW must also be indexed prior to searching. Full Text Search Options The full text search engine in LAW contains several options to help customize searches. Using the Full Text Search Options dialog. the LAW case database must be SQL or SQL Express.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.

Setting this value to 0 will return an unlimited number of hits. The slider on the Options dialog dictates the amount of fuzziness to apply to a search. Retrieval Thresholds Max files to retrieve .LAW PreDiscovery User Guide & ~~ : ## 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.Supports standard AND/OR connectors between search terms. Selective stemming may also be performed by using "~" at the end of the word to be stemmed (i. participle. Example: fish would also find fished and fishing If using the Full text search options dialog.Limits the number of full text results returned by the search. etc. phonic searching will be performed on all words within the query. stemming will be performed on all words in the search criteria. Abort Search After .Rather than returning the documents with the highest scoring. LAW will include a temporary ft_HitsByWord field in the search results in the standalone grid. application. The default returns 500 hits. appl? matches only apple. ap*ed matches applied. The word "fast" would also return "quick. etc.When enabled.e. this setting returns the results found up to the point when the threshold is equaled. fish~). Results Options Include hits by word in search results . All Words/Any Words . Search Syntax Boolean ." If using the Full text search options dialog. For each document. this field will display the search words that For each 174 . Files are returned by the highest score or number of hits. Synonym Searching: Finds synonyms of a word in a search request. and smithe Stemming: Finds words that cover grammatical variants of a word. Examples: appl* matches apple. Wildcard searching is particularly useful when wishing to return all variables of a particular word or a combination of a portion of a word. Phonic searches can be performed selectively by putting a "#" in front of the word being searched. even if misspelled.Alternative to using Boolean that implies all AND’s and OR’s respectively between words. 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. Note: Limiting this number improves full text performance. Users can utilize synonym searching selectively by adding the "&" character after a certain word in the request. smythe. The position of the % character determines how many letters at the beginning must match exactly. synonym searching will be performed on all words within the query. Fuzzy Searching: Finds words. Fuzziness can also be performed selectively by using the "%" character. *cipl* matches principle. If using the Full text search options dialog. Example: #Smith returns smith. etc. approved.

Performing Full Text Searches In LAW. One cause may be that the case is not a SQL or SQL Express case. Full text search results cannot be returned to the embedded (main form) grid. full text searches are performed using the Query Builder tool (Tools > Search Records or click the binoculars icon). select the "Full text search" check box. Enter the desired search terms into the text box provided. Search words and their frequency are comma-separated and multiple search words are separated by a carriage return. Any full text search terms and connectors will be displayed in the text box as shown. Once located. this field will display the search words that yielded the document. users can begin typing letters into the "Lookup" field to locate words. LAW will prompt the user to choose a 175 . Full text search terms can also be loaded through the Query Builder. To invoke the full text section of the Query Builder. Click the Load Terms button and browse to a TXT file containing the list of terms. If needed. The AND/OR connectors are available in this dialog as well for joining search terms. use the AND/OR connectors to join search phrases. Once the TXT file has been selected.Searching document. 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. A third possible cause is that none of the documents have been indexed (see Full Text Indexing). Another possible reason is that the "Send results to grid on main form" option is enabled in the Query Builder. consider three possible causes. An alternative to typing the search terms would be to launch the Fulltext Dictionary dialog by clicking the Dictionary button. paired with the frequency of those words. click the Add button to add the word to the Query Builder. Note: If this option is grayed out. In this dialog. Click Done to exit the dictionary.

The location of this pane may be changed by clicking View > Text Pane in the grid and choosing one of the following options: Left. launch the Query Builder (Tools > Search Records). When returning full text search results. This is a much faster way to flag results when dealing with large amounts of data. or Off. The single arrow buttons will navigate from hit to hit. click the Tag Text Hits button. Hits can also be navigated by entering a number within the text box in between the navigational buttons and then pressing the Enter key. Click the Execute button from the Database Query Builder dialog to perform the search.LAW PreDiscovery User Guide connector which will be inserted between each term found in the list. waiting for the search results to return to the grid display. Right. If a numeric field is used. check the box beside "Full text search". Full text searches can also be executed and records with hits can be tagged instead of returned to the grid. When the final hit for a document is reached. the standalone grid will have an additional text pane to display the text for the document and highlighted hits. LAW will simply tag the field as "Yes" for records with text hits. first create a document-level tag (Boolean) or numeric index field (Index > Modify Fields. LAW will populate the field with the number of text hits found for the record. Next. Once the field has been created. If a tag field is used. The Fulltext Hitcount indicates the number of hits within the record. This feature can be used in place of executing a search. respectively. and then enter the desired search term(s). To use this feature. The hits within a document can be navigated using the directional buttons located below the text in the text pane. Two fields will be added to the grid when displaying full text search results: Fulltext Hitcount and Fulltext Score. 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. the right arrow will navigate to the next document. and tagging documents from that interface (if needed). unless the last document in the result set is currently selected. See the "Full Text Reports" section below for more information. The flagged field can later be queried to pull results or used in conjunction with other queries. Bottom. The Select Target Field dialog will appear. Full text search results will only be returned to the standalone grid. A "NONE" option is also available when the AND/OR connectors are not needed. 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. see the Creating Index Fields and/or Creating Tag Fields topics). 176 .

The search engine effectively treats a noise word in a search request as a word level wildcard. The search request "Security Code" will return a minimum of two hits (one for each of the two words that comprise the term).) Does Not Match: "To disable security enter the code".) Matches: "I entered the security code". LAW will return a message box containing the total number of affected documents."Blue Car". Example: Request: Enter * Code (If using Any Words/All Words syntax then use: "Enter * Code". If the search syntax is set to Any Words or All Words. This file is located in the \dtconfig folder which can be found in the LAW installation path. but not in sequence. Example 1 (Noise Word: "The"): Request: The Car (If using Any Words/All Words syntax then use: "The Car") Matches: "Red Car". causing the removed words to be included in the index."Fast Car" Example 2 (Noise Word: "The"): Request: Harold The Cat (If using Any Words/All Words syntax then use: "Harold The Cat") 177 . Full Text reports count the occurrence of the entire term as one hit.) Matches: "enter unique code" . 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. the total number of hits.dat.) 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. matching any word that occurs at that position. as do counts in the ft_HitsByWord column which is controlled by the "Include hits by word in search results" Full Text Search Option. "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. Only full text searching is supported. Example: Request: Security Code (If using Any Words/All Words syntax. 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. then use: "Security Code". and the elapsed time. 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. The noise. 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.Searching All user-defined tag and numeric fields will appear in the list. (Words occur in sequence. Choose the field to be used as the target field and then click the OK button. The effect of noise words in a search request typically manifests itself when searching for terms or word sequences. 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).dat file may be edited to remove noise words from the list. Note: This feature does not incorporate any database conditions that may be selected when performing the text search. LAW manages noise words at the application level in a file named noise. (Words occur.

Next. then click the Full Text Reports button. Note: Effectively. Select a Boolean connector (AND/OR) to connect the database query to the full text query. A single word search request for a noise word will return no records. Operator. The search results will be returned to the standalone grid view. Click Execute. Combining Database and Full Text Searches LAW enables users to combine database and full text conditions into one query. enable full text searching by checking the box beside this option. so in the above example the search request is processed as: Harold * Cat. Click Add Condition to add to the list of conditions. 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. check the box beside Full text search. Within the Query Builder. The Full Text Search Reports dialog will appear. To access this feature. a search request for the term "because" would yield no results.LAW PreDiscovery User Guide Matches: "Harold my cat" Does Not Match: "Harold My Friend" (Term search. 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. For example. only matches one of the required words in the sequence). a noise word is processed as an "any word" wildcard (*). 178 . and Value for the database search. select the Field. Enter the desired full text search terms. click Tools > Search Records.

179 . One request will be added per row in the Search Results queue. the duplicate items will be ignored. The requests can be added to the queue by importing a list (Import Searches) or by entering them manually (Add New). Press the Esc key to cancel edit mode. Add New . 2. Note: Imported text files may contain Unicode terms. Unicode text files must be in UTF-8 or UCS-2 format. To edit an existing entry. This feature is for text searches only and will always search across the entire LAW case and not subsets of records. Once added. See the "Full Text Search Options" section in this topic for more information regarding these options. double-click in the Search Results cell or press the F2 key. 3. After clicking this button. browse to the text file containing the requests (input file should contain one request per line) and then click Open. 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).Searching Start by submitting search requests. 1. Import Searches . Click the button to add a row to the queue.This function is used to add search requests to the queue manually. Click the Add New button as needed to add more rows to the queue for additional search requests. Search Options . also accessible from the Advanced tab in the Query Builder by clicking the Options button.This function is used to import search terms from a text file into 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). Below is a list of the functions included in this dialog and a description of how each can be used. Press the Esc key to cancel edit mode. Duplicate search requests cannot be entered. double-click in the Search Results cell or press the F2 key. Each row is executed as a separate search request and not combined with the terms in other rows within the queue. To edit an existing entry.This function launches the Full Text Search Options dialog. If requests in the input text file match any requests that are already in the queue.

or select multiple. 6. or had its search status reset by clicking the Reset Counts button. they are not combined or joined in any way. Export Searches . Once the searches have completed. 7. After clicking the button. 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. Clear All . ANSI will be used. 180 . that row will not be included in the search process. The screen below shows a populated Search Requests queue. Delete . a report may be generated or the affected documents can be flagged using the Tag Text Hits feature.This function will clear all search requests from the queue. specify a file name for the text file.This function will execute all search requests listed in the queue. the output file will be formatted as UTF-8. If the box is not checked for a particular row. LAW will calculate the number of documents affected by the search and place it in the Docs column. and selecting the last row in the range to be deleted. and then click Save. this feature does not return records to the grid. Click Yes on the prompt message to proceed with the deletion(s) or click No to cancel. Select a row by clicking on any cell within the row. Run Searches .LAW PreDiscovery User Guide 4. The total number of hits found across all documents will be placed in the Hits column. adjacent rows by clicking a row. Unlike the full text search in the Query Builder. Only the selected searches were executed after clicking the Run Searches button.This function will delete the selected search request from the queue.This button will become available after one or more search requests have been added to the queue. It will only search documents added since the successful completion of previous searches. browse to the desired output location. 5. 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. Note: If any of the specified terms contain Unicode. This feature will export the search requests in the queue to a text file. otherwise. one request per line. holding down the Shift key. Each row is treated as an individual search. Note: When new documents are added to a case. re-running a set of searches will not search the entire case again.

Searching 8.This summary shows document and hit counts for each custodian in the case. 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).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 report will open automatically once it has been generated. and then click the Run Searches button. and then click OK. the Total Docs column shows the number of documents returned by the search request(s) (documents are counted only once. enter a file name for the HTML report. Search Summary . Tag Text Hits . When the searching has been completed. The report has two sections: a. Next. open the Query Builder and add one or more search requests to the queue. browse to the desired location. check the box to tag parent/attachment families if needed. To use this feature. The Select Target Field dialog will appear containing a list of all tag fields that exist in the current case. even if they hit across multiple searches). Choose the desired tag field.This feature can be used to "flag" a tag (Boolean) type index field for all records that contain text matching the specified search terms. b. start by creating one or more tag fields (Index > Modify Fields or see the Creating Index Fields topic).This summary contains a list of every search request and shows the total document and hit counts for each. The state of the check boxes shown at the beginning of each row will determine which search requests are included in the report. Save Reports . Custodian Summary . click the Tag Text Hits button. When using the Tag parent/attachment families feature. 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 document containing the hit will be tagged as well as the entire family if the document is a parent or attachment record. Click the Save Reports button. 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. The Hits column indicates the number of the text hits found in the documents based on the search requests in the queue. For each custodian. and then click Save. See the "Tag Text Hits" section in this topic for more information related to the Tag Text Hits feature. 181 .

LAW PreDiscovery User Guide 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. select it from the list. Uncheck All .mdb. Cancel . The "Target field for preserving text hits" drop-down will contain all user-defined. the search hits can be placed in a user-defined memo field for later usage. Reset Counts . Check All . the contents of the queue will be restored from the previous session. therefore. This data is stored in an Access database in <case root>\$UserData\TextReports\Searches. unlocked memo fields that exist in the current case. When the Full Text Search Reports dialog is re-launched.This function will select the check boxes for all search requests currently listed in the queue. Click Yes to confirm or No to return to the Full Text Search Reports dialog. as full text search results cannot be returned to the embedded grid display. 13. This feature exists in the standalone grid only.This function will de-select the check boxes for all search requests currently listed in the queue. 10. Once the standalone grid has appeared containing the results of the search. Unlike the Query Builder itself. click Tools > Persist Text Hits from within the grid. the Full Text Search Reports feature can run multiple search requests at once. 182 . the hit count would be different for each request versus the single hit count returned by the Query Builder.The Accept button will save all information currently shown in the Search Requests queue and close the dialog. 12. The Add Field dialog will appear. To utilize this feature. 11. Note: Clicking the Run Searches or the Save Reports button will automatically save all changes from the current session to the search reports database. first perform a full text. To create a new memo field instead.. Accept . LAW will populate the field with unique hits only and separate them by semi-colons.This function will clear the values in the Docs and Hits columns allowing the search requests to be re-executed. To use an existing field. select <Create New Field.If any changes have been made to the queue in the current session. 10.> from the list.. The Persist Text Hits dialog will appear. clicking the Cancel button will result in a warning prompt that all changes will be discarded. Persist Text Hits After a full text search is executed.

Note: If a term. software 183 . click Accept to execute the Persist Text Hits feature. with each hit separated by a semi-colon as previously mentioned. or multi-word. The "Insert at top of list" setting also does not apply at this time and is disabled. the new. search is executed. unique values will be appended. each word of that term is treated as a separate hit. choose the desired "Rows Spanned" value. these options are pre-selected and the Table and Type fields are disabled. Enter a new field name. and then click OK. If hits already existed in the field. if the term search request is "good software". Once the field has been selected.Searching Since only document-level memo fields may be used for this feature. then the Persist Text Hits target field will contain: good. For example.

box. 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). select all documents to be updated in the document list (using Ctrl. See Batch Updating for additional information. This allows users to code common fields (e. invalid date values for date fields or duplicate values for a unique field). enter the desired values into the field or fields on the Index display.Document-Level Coding Document-Level Coding LAW allows users to track information about records to aid in retrieval. When documents are being scanned. If any of the values are not accepted (e. enter the common values in the desired field. and click the Update button. the Batch Update dialog will appear allowing the user to select only those fields to be updated..g. 185 . If the <Update> button is clicked while multiple documents are selected. but are not editable.) and saved if accepted. Multiple Documents LAW can update multiple documents with the same values. select the document in the document list. Shift. Page-level fields created by users can only be edited using the Import Tag List and Auto-Numbering features. etc. Ctrl+A). Updating Documents Single Document To update an index field for a single document. To update fields for multiple documents.. text. User defined page-level fields can also be displayed in the Index display.or folder-level information) at scan time without having to re-enter the same values for multiple documents.g. Coding Options LAW provides the following two features to save time for users who are coding large batches of documents. which will increment from document to document). 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". The values will then be validated based on the field types (date. This data is stored in the index fields which are typically created when setting up the case. the user will receive an error message and the update will be cancelled. and click the Update button (or ALT+U).

and a value is typed directly into a list field and the document is updated. With this option selected. select the desired field name from the Index > Default Field menu. With a combination of the auto-advance feature and a default field.LAW PreDiscovery User Guide Auto-Advance LAW can auto-advance after updating a document. check the 'Auto-advance after updating a document' setting on the Preferences tab of the Options form (Tools > Options). select the 'Allow selection of multiple list items' setting on the Preferences tab of the Tools > Options form. 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 feature causes the next document to be loaded as soon as the current document has been updated. check the 'Add all new list field values to list on update' option on the Preferences tab of the Tools > Options form. To activate this feature. List Field Options List items may also be added automatically when coding documents from the main form. To disable the default field setting. To enable this feature. To set a field as the default. users can practically eliminate the need for the mouse when coding documents. the value will be added to the list (if not already present in the list). the user must also select a separator character to separate each selected list item in the field. The default field is denoted by a check mark. or tab and down arrow to the next document. thereby eliminating the need to switch to the mouse and select the next document. This eliminates the need to tab around or use the mouse to set the focus back to the index fields. If this option is enabled. To select multiple list items when updating a single document. simply select the same field again. 186 .

If the first record does contain field names. When the Import Delimited Text dialog appears. select a delimited text file (*. 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.Coding Importing Data LAW can import delimited text files to link records in LAW with existing index information stored in delimited text format. 187 . the coded data cannot be linked to the images. The Character Encoding value can be adjusted if needed to ensure the file is parsed correctly. *. This feature is useful when coding was performed in another application. The records must either be already numbered (i. for example.e. If there are any fields not to be imported. Click the Restore Defaults button to reset the delimiters back to the default comma/quote delimiters. select the fields being imported from the list of Available Fields in the same order as they appear in the text file. check the First row contains field names option to ignore the first row. select File > Import > Delimited Text from the main form. The Data Delimiters may be used to allow other types of delimited files to be imported as well. A sample of the data contained in the file will be displayed.. To use this feature. Next.csv . Note: The Image Tag field must be one of the fields selected for import.txt) to import. Otherwise. select the <!-SKIP FIELD-> field to ignore values appearing in that column. PageID for image records) or have at least one coded field to act as the image tag.

LAW PreDiscovery User Guide

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. button in To update fields for multiple documents, click Edit > Batch Update in the standalone grid or click the 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

LAW PreDiscovery User Guide

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 userdefined 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

LAW PreDiscovery User Guide

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 userspecified 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

LAW PreDiscovery User Guide

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

The setting applies to autonumbering.001.ini file in C:\<Windows>. If either the prefix or the suffix contains a matching rollover character.0001.10001 Note: By default.99z would increment to 001.001.0001. the number will first be split into prefix and suffix sections and then incremented accordingly.001.001.0001. ABC. The sub-option.002.990 If the next document is larger than nine pages. when the numbering sequence increments high enough to roll into the next section.334 .000.000).001.9998 ABC.001. The default is a ". and both document-level and page-level fields.001. IncrementAfterSectionRollover=1.0001. If "Use document level attachment numbering" is enabled.001. the value would become ABC1.9999 ABC. For example. that section will not rollover. the following contains four sections if the period is the chosen delimiter: ABC.001.001. place the entry below into the LAW50.0001. the batch Document Numbering process. simply add the key.001. the section that rolled will increment back to the value of "1" instead of "0". When the document/page level separator is enabled. Note: Rolling will not occur in sections containing non-numeric characters. below it.333 Doc 2) ABC.0001. An example with this setting disabled is shown next: Doc 1) ABC. For example. To toggle the setting.0001.999.0001. However. will determine whether or not pages of a document will span across more than one document level.0001.9998 ABC. 001.10000 ABC. If the alpha-numeric option is disabled while rolling numeric is enabled. it will start on the next level: 195 .0001 used to number a documentlevel index field. ABC.9999 would increment to ABD.661 .600 Doc 3) ABC.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 rollover calculations occur prior to appending this suffix. If the [Preferences] section already exists. rollovers will occur at the page and document levels.99aa." (period).ABC.0001.001 . [Preferences] IncrementAfterSectionRollover=1 1 = enabled.001.001. the values will be incremented as follows (using the above example values): ABC.001.001.001. the [00-00] suffix will be applied to the end of the userdefined starting value.0002 If the "Use rolling numeric sections" setting is disabled.ABC.0001 ABC.000.0001.001.999.002. So 001. Example: The "Use rolling numeric sections" setting is enabled and the value ABC.001. Allow page level numbering to span across sections. The Section delimiter is used to specify the character used to separate sections in a numbering scheme. The alpha-numeric Bates numbering setting may be used with rolling sections as well.001. For example. 0 = disabled The other settings on the Numbering tab can be used with the rolling numeric sections option.000.001 (not 002. An INI setting is available to disable the auto-increment after a rollover if this is desired.ABC.0001 with both settings enabled. if a non-numeric character exists in a section.0001.001.9999 ABC.000.999 becomes 002.

use the Query Builder. the fourth document's pages would span across sections: Doc 4) ABC.002.LAW PreDiscovery User Guide Doc 4) ABC. 196 . which allows users to edit individual Page IDs and provides the option to auto-number to the end of the document.225 Manually Numbering Pages The auto-numbering functions work well for numbering batches of sequentially numbered pages. Finding Specific Page IDs To locate specific Page IDs.001 .002.001. Doing so will launch the Edit Page ID dialog.991 .001. users may have to manually edit Page IDs. To locate groups matching a specific pattern or ranges of Page IDs.ABC.001. select Index > Edit Page ID (<Ctrl+E>) or simply double-click on the Page ID display located below the Image display. use the Find Page ID (<Ctrl+F>) function from the Index menu. Once opened. However. if frequent gaps in the numbering scheme or intermittent alpha suffixes on pages exist. To edit individual pages. 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.001. LAW will prompt for the desired Page ID and if found.002.234 With the setting enabled. the document will be opened to the page with the specified Page ID.ABC.001.

or on filtered results. produced to paper. 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. responsive documents. The tagging feature in LAW has multiple uses. Tagging may be performed on individual records. This feature makes it easier for any project. one or more tag type index fields will need to be created.Coding Creating Tag Fields LAW allows users to create tag fields at a document or page level. to be produced. The Modify Fields dialog will appear. scanned or electronic discovery. 197 . Users may even wish to tag documents that should be produced at a larger paper size or produced in color. Before documents can be tagged. etc. Users may choose to tag documents that need to be converted to tiff. on all records in a case. Click Add Field to launch the Add Field dialog. Users may also import a list of unique IDs to toggle tag values.

Select Tag (Boolean) for the type. The process of tagging documents is discussed in the Tagging Records topic. For more information on creating index fields. making the field easier to locate. see the Creating Index Fields topic. Click OK to create the tag field.LAW PreDiscovery User Guide Enter a Name for the tag field and select the Table (document-level or page-level). 198 . Choosing "Insert at top of list" will insert the field at the top of the list in the Index display.

on the Index display. the "Yes" values will appear as a green check mark and an empty field will indicate the value is "No". especially when reviewing large sets of documents for re-processing. Records may be tagged in the grids (using the mouse or hot keys). changing the value from "No" to "Yes" or vice versa. The Tagging Hotkeys dialog will appear. Assigning Hotkeys Once tag fields have been created in a case. Hotkey tagging will often be more efficient than using the mouse. using batch update. click the "Tagging Hotkeys" button ( grid display. ) in either the standalone or the embedded 199 .Coding Tagging Records Tag field values will be reflected in one of two ways in the Index display: "Yes" or "No". see the Creating Tag Fields topic. 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. 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. using batch tagging options in the grids. Tagging Individual Records To tag an individual record. To assign hotkeys. or by importing a tag list. To learn how to create a tag field. and clicking the Update button. 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. users can assign hotkeys to each field via the grid display (for use in the grids only). In the grid displays.

200 . The Hot Key cells will contain drop-down lists of keys that may be used for hotkey tagging. Tagging Multiple Records In addition to tagging individual records. using the Batch Update feature. click the "Review Mode" button ( ) located on the toolbar in the standalone and embedded grid displays. Once a relevant record is found. Using Hotkeys to Tag Records With review mode enabled. After clicking this button. simply click the "Review Mode" button once again. There are generally three methods of tagging multiple records at once: using batch tagging options in the grid. Press the hotkey a second time to toggle the current value. users can assign the same value to a tag field for multiple records at one time. 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.LAW PreDiscovery User Guide All existing tag fields will be listed in the Tag Field column. Click OK after assigning the desired hotkeys to the fields. To disable review mode in either grid. The Import Tag List method is discussed in a separate topic. Review Mode Because the tagging hotkeys may also be used as shortcut keys for other functions in LAW. To enable Review Mode. This method of tagging is often performed on a filtered set of records. a "Review Mode Enabled" message box will appear after clicking the review mode button. or using the Import Tag List feature. The cell will display a green check mark when a record is flagged with the "Yes" value. use the assigned hotkey to edit the tag value in the tag field. The button will appear "depressed" to indicate that review mode is enabled (in both grids). users will need to enable "Review Mode" in order to make use of the hotkey tagging feature. use the up and down arrow keys to navigate through the records in the grid display.

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

LAW PreDiscovery User Guide See the Importing Tag Lists topic for information on the third method of tagging multiple documents. 202 .

The range delimiter is used when importing ranges of records to be updated rather than a list of individual ID numbers (i. DocIDs). select File > Import > Tag List from the main menu. it is recommended to apply an index to the selected Document ID field. 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. For example.. The tag import file is typically a text file containing a list of unique identifiers allowing LAW to locate the records in the case. However. 203 . 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. To access this feature. For greater performance in cases with a large number of records.e. 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. check the "First row contains field names" box.e. if the user is provided a text file containing a list of DocIDs that match the DocIDs in the LAW case. ID0001-ID0048). then the user would select DocID as the Document ID Field. If the import file's first record contains the field name.csv file containing a list of document identifiers (i. An index can be manually applied to a field using the Index->Modify Fields dialog box. This list may be easily imported into the existing LAW case and later queried to locate the records for further processing. The Import Tag List dialog box will appear.txt or *. Click Browse to locate the tag import file. A list of DocIDs or BegDoc#s are commonly used for this purpose.Coding Importing Tag Lists The Import Tag List feature can be used to flag multiple records using a *.

The Target Field is the field to be updated with the "tag" value. If a tag field is selected. the grid displays will need to be closed prior to adding the index. click Add to add the entry to the list of Selected Fields. such as a text field. When adding an index using this method.LAW PreDiscovery User Guide LAW will check for the existence of an index on the selected Document ID field. Once the Target Field. If the field is not indexed after initializing the import. If other field types are selected. 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. LAW will report the number of records that have been updated and any errors that may have occurred during the import. Click OK to initialize the import. Once complete. These records may then be returned by a search using the filter functions or query tools. and Flag Value options have been configured. If the grid is active. Additional target fields may then be selected as needed. Date fields will only have an Update option. Action. 204 . Note: A memo field cannot be used as the Document ID field. LAW will allow the addition of an index for the selected Document ID field at that time. 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). LAW will display a prompt requesting the grid be closed in order to continue. the Flag Values will appear as "True" and "False".

Selected Documents . selected documents. Document and Page Counts In cases with a large number of documents and/or pages. button found on the main toolbar as well as the standalone The Batch Processing dialog is broken into three sections: Processes. and edit the invitation type. To avoid the potential delay. and OCR documents. 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. Batch processes can be applied to all documents in the current case. Processes . Sharing . To begin batch processing. See the LMC Configuration topic for more information on setting invitations and the LAW Management Console. The Calculate total documents option may be selected to include document counts (and possibly page counts . or a single document.This section is used to enable distributed batch processing.see next section) in addition to the number of folders selected. The All Documents option will result in the entire case being included in the batch. or join batches. endorse. The number of pages will no longer appear beside the number of documents. select Batch Process from the Tools menu on the main form or on the standalone grid form. Enabling this option could cause a delay when returning to the Batch Process screen in large cases.Batch Processing Overview Batch Processing Overview The Batch Processing utility allows certain processes to be performed on multiple documents. view. 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. assign a batch name. The Batch Process utility may also be launched by clicking the and embedded grid toolbars.This section lists all available processes that may be executed as a batch. edit. perform cleanup functions. print (to tiff or paper).This section allows the selection of documents to be processed and displays total document and optionally page counts of the selected records. and Sharing. a delay may be experienced when launching the Batch Process or Export Utility dialogs while LAW calculates the total number of pages to display. 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. Selected Documents. This feature can be used to number. 205 .

including the assignment of Page IDs to uniquely identify each page of a document with an associated image. The Noise Removal (despeckle) filter attempts to remove dust or scratches on an image. Image Cleanup Image Cleanup performs the specified cleanup function(s) on all included images. In order for black borders to be removed. These functions may be performed as each page is scanned (see Scan Options) or all at once in a batch process.LAW PreDiscovery User Guide Document Numbering Document numbering is used to assign numbering schemes at a document. Choose Page or Document to determine which fields will show in the Target Field drop-down. Then. The deskew filter straightens image alignment.and/or page-level. Document-level fields may also be numbered using this process. 206 . The value will increment by one for each document in the batch based on the starting number. the borders must be of uniform width (angled black edges will not be removed). Note: The image cleanup filters are only applied to bitonal (black & white) pages. The black-border removal filter removes black borders from images. the field to be numbered is selected as the Target Field and a Starting # is entered.

Use the First Page Only feature to endorse only the first page of each document. Print (Standard-Image Only) The Print process prints the selected image records to the printer specified in Options > Print Options. Warning: Endorsing with a watermark should be used with extreme caution as endorsed watermarks CANNOT be removed.) Only documents with pages flagged for OCR will be processed. OCR The OCR process performs optical character recognition on all selected documents that are flagged for OCR. If the images have not been endorsed. To do so. select Options > Header/Footer from the Batch Processing dialog. See EPrint/Tiff Output Settings for details. No resizing is performed on the watermark. if they already have OCR for the specified output format and the "Overwrite Existing Files" OCR setting is not selected. A watermark (overlaid image) can also be burned into the endorsed images. If a header or footer is specified. selecting "Yes" will add the current header/footer information for the print process only. keep in mind that most third-party applications cannot use non-text formats for search and retrieval capabilities. The E-Print Options dialog also contains options for various native file types such as MS Word and MS Excel. Note: Documents may be skipped. To do so. Warning: If the first page contains annotations. When selecting the output format. select "No" when prompted to include the header/footer information as it is already contained on the images. it is simply applied at the location specified in the Alignment option. To display or modify the current header and footer settings. and the user does not wish to permanently alter the images. See Watermark for additional information. it can either be included on the printed images or ignored. E-Print (ED-Native Files) The E-Print process prints the selected native files to the printer specified in Options > E-Print Options. If the images have already been endorsed. Selecting "Yes" will cause LAW to unnecessarily re-endorse the selected images. even if flagged. A watermark can also be applied during batch printing. Advanced batch print options can be specified from the Batch Print Options dialog. These settings are also used for single-document OCR. The OCR settings may be displayed by selecting Options > OCR Settings from the Batch Processing dialog. select the desired watermark image from the Watermark Settings dialog (Options > Watermark) and ensure the "Apply watermark to endorse process" option is checked. 207 . See the Header/Footer Options for details. available by selecting Options > Print Options. the annotations will be lost. (See the Flagging Documents/Pages for OCR section for details. 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.Batch Processing Endorse The Endorse process endorses all documents with a specified header and/or footer. select the desired watermark image from the Watermark Settings dialog (Options > Watermark) and ensure the "Apply watermark to print process" option is checked. so be sure to validate the OCR settings before starting any OCR process.

and PageHeight fields for any images in the selected record set missing this information. For a list of source applications and supported file types. creating a double endorsement.LAW PreDiscovery User Guide 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 will assist in finding the documents that were double endorsed. Version 7 of the Peernet image printer is also supported for tiff conversions. or Informatik Image Printer to convert the selected files to TIFF images. 208 . For example. Update Page Data The Update Page Data batch process can be used to populate the PageColor. see Supported File Types. but must be purchased directly from Peernet. LexisNexis® Image Driver (300 DPI). PageSource is not affected during this process as the source can only be captured at the time the image is acquired. TIFF Conversion This process will use the LexisNexis® Image Driver. See the E-Print/Tiff Output Settings section for information about native application options and TIFF printer settings. if Microsoft Word is the value in SourceApp. This feature is useful if images already containing an endorsement have been imported into a case and the documents were reendorsed again. The selected SourceApp must be installed on the computer in order to be used for TIFF Conversion. The application displayed in the SourceApp field for each record will be used to convert the native document to a TIFF image. 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. PageWidth. PageSize. then Microsoft Word will actually be used to convert the document.

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

select the pages to be flagged. This allows multiple workstations to OCR the same set of documents simultaneously without having to worry about overlapping OCR.. 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.g.LAW PreDiscovery User Guide Flagging Documents/Pages for OCR Low quality originals or cluttered pages (e. LAW allows users to specify which pages of an image will be included for OCR. select the image to be included in the OCR process. To accomplish this. they must do so one document at a time. As such. If one machine locks up or crashes during the OCR process. The OcrStatus field is a document-level field that indicates the OCR status of a document. If the user only wants to flag certain pages for OCR. All non-flagged pages are skipped during the batch OCR process. Tracking OCR Status OcrStatus Field LAW maintains two fields in the database to track the status of pages with regard to OCR. frequent crashes of the OCR engine. 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. 210 . Note: All pages will be included if using the single document OCR process regardless of the OCRFlag value. In order to make the OCR process as efficient as possible. they do not provide good OCR candidates. detailed graphs and charts) can lead to excessive processing time. OcrFlag Field The OcrFlag field is a page-level field that tracks the OCR status of each page of a document. and very poor OCR results. and click Page > Flag for OCR (or right-click on thumbnails to display the pop-up Page menu). one or more other stations can continue to OCR that set of documents. Using multiple stations to share the OCR process provides an extra layer of redundancy.

If all of the documents are in one folder. If the documents span multiple folders and can be logically grouped in a query. Displaying Flagged Pages To display the pages for the current document that are flagged for OCR. or to reset all documents in a case. From the standalone grid. It will not highlight pages that have already been completed. 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. Flagging Pages at Scan Time Pages may be flagged for OCR at scan time. 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. This function only highlights pages that are flagged for OCR. select Tools > Reset OCR Flags > ON|OFF to reset the OCR flags for all documents in the current record set. 211 . This highlights all flagged pages in the thumbnail display. it automatically becomes active so that the thumbnails are shown. This setting can be toggled by selecting Scan > Scan Options > OCR All New Pages. utilize the grid display. If the thumbnail display is not active when this function is selected. select Page > Show OCR Flags.Batch Processing Resetting the OCR flags for multiple documents can be done in one of two places. This allows users to set the OCR status of all new pages as they are being scanned.

language support. ExperVision is included with the LAW installer. The ExperVision OCR engine is much faster (2-3x) than ABBYY FineReader.ocr files which are used in the Storm and IPRO applications for on-image hit highlighting. Available Options OCR Engine LAW PreDiscovery supports two different OCR engines: ExperVision OpenRTK and ABBYY FineReader. select Tools > Options from the main form and select the OCR tab or choose Options > OCR Settings from the Batch Processing utility. and output formats. Japanese. 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. To open the Options form and modify the OCR Options. it cannot be supported by LexisNexis. and Korean languages) and is able to create PDF/A files. ABBYY FineReader includes more language support. 212 . Older versions of LAW also shipped with a Xerox TextBridge engine and while this engine will still work with LAW. giving more control over the OCR process. including CJK (Chinese.LAW PreDiscovery User Guide OCR Options The OCR tab shown below will allow users to specify various OCR options. Both engines support the creation of searchable PDF files and are able to produce <image>.

English will automatically be used as a second language if a non-English language 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. lower right. the ABBYY engine supports a Quality setting called MICR (Magnetic Ink Character Recognition). if Greek is selected and both Greek and English exist in the source image. the OCR engine presumes that only one column of text exists on a page. For the unsupported Xerox TextBridge engine. lower right. the System Default setting uses whichever language is specified by Windows as the default. When a setting other than Normal is selected. two special page layouts are available that can be used to OCR pages that are broken into even quadrants: "Quadrants. Korean. Spanish. The left to right setting will OCR the 4 quadrants in the following order: upper left. lower left. lower left. Chinese. and English is selected as the language. left to right" and "Quadrants.Batch Processing The options on this form (discussed in the remainder of this topic) will change with the selection of the OCR engine. Languages that share a common alphabet (i. Greek. Quality This setting can be used to specify the quality of the pages to be included in the OCR process. ABBYY should be able to detect and perform recognition for both languages. Language The Language setting is used to specify the language dictionary the engine should use during the OCR process. French. If the correct language is not selected prior to the OCR process. The top to bottom setting will process in the following order: upper left. upper right. Russian). The default value of Auto Detect automatically determines the layout of the page. top to bottom. English.e. Japanese. Greek characters will not be interpreted or rendered correctly in the text. The Auto Detect setting is recommended for the unsupported Xerox TextBridge engine as it accounts for varying quality levels among originals. Portuguese) will be interpreted correctly when existing in the same document if any of these languages are selected. the characters may not be recognized properly. Dutch. Note: This only pertains to languages containing Unicode characters (i. For example." Both settings will OCR the page as if it were 4 separate pages condensed onto a single page. For the unsupported Xerox TextBridge engine. For example. upper right. if a document contains Greek. Page Layout This feature can be used to improve OCR results by specifying the layout of the pages.e. German. 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. The available output formats and licensing requirements are in the following table: Output Format Required License(s) OCR (ExperVision OpenRTK) Smart Text Document Standard Text Document OCR (ExperVision OpenRTK) -OROCR (ABBYY FineReader) 213 . Output Format This feature is used to select the output format produced by the selected OCR engine. If Single Column is selected. If ABBYY is the selected engine. 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). However.

using one of the text settings is recommended as most export formats do not support non-text OCR. Page Markers can be customized via the law50. By placing the PageStampText= section under the [OCR] key. This feature is useful for providing 100% accurate bates values in the OCR text to aid searching in certain applications. both producing standard ANSI text output. 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. the text stamped by the Page Marker feature can be customized. The Smart Text and Standard Text are essentially the same. 214 .LAW PreDiscovery User Guide HTML OCR (ExperVision OpenRTK) -OROCR (ABBYY FineReader) Word for Windows OCR (ExperVision OpenRTK) -OROCR (ABBYY FineReader) Word for Windows (2007) OCR (ABBYY FineReader) WordPerfect OCR (ExperVision OpenRTK) Adobe PDF (Normal) OCR (ExperVision OpenRTK) + OCR (ExperVision PDF add-on) -OROCR (ABBYY FineReader Adobe PDF (w/ Hidden Text) OCR (ExperVision OpenRTK) + OCR (ExperVision PDF add-on) -OROCR (ABBYY FineReader) Adobe PDF/A (Normal) OCR (ABBYY FineReader) Adobe PDF/A (w/ Hidden Text) OCR (ABBYY FineReader) Warning: If planning to export the OCR results for searching functionality.ini file located in the <Windows> directory. Note: Only the text-based output formats can be modified using this feature. See Creating Searchable PDFs for more information when using the Adobe output options to create searchable PDF files.

215 . Use this setting to set the "visible" property of the thumbnails when opening the PDF file in Adobe Acrobat. "Always OFF". This can often lead to more accurate OCR (depending on the type of document).) Overwrite Existing Files Use this setting to prevent or allow the replacing of existing OCR text. However. Create PDF Thumbnails The OCR engines automatically create thumbnails during the Searchable PDF creation process. Auto Deskew Enable this option to force the OCR engine to deskew the image before OCRing the document. setting can be used to auto-rotate black & white images only.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. and "Binary Images Only. checking this option will replace the OCR for each document. It may also be necessary at times to replace all existing text files. Retain Pictures This setting determines whether pictures in the original will be preserved in the OCR results." The Binary Images Only setting. the deskew feature may align to these graphics and cause unexpected results. if the document contains graphics or angled vertical lines. the thumbnails will be hidden under the Pages tab in Adobe Acrobat. Disabling this option will OCR the document with its current orientation. If this setting is checked. otherwise. The three options are "Always ON". etc. 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. the OCR engine will skip the document and move onto the next. (Pictures are not retained in text files.) will be preserved in the OCR results (non-text output formats only). the thumbnails will be viewable automatically in Adobe Acrobat. This setting does not affect the results if the output format is set to text. If an existing text file is detected for the current document. This feature is only available if the ExperVision OCR engine is selected. available to the ExperVision engine only. thus saving processing time. which can help prevent color/grayscale images with little or no text from being improperly rotated. Retain Page Layout This setting determines whether the layout of the page (columns. Auto-Rotate This option specifies if the OCR engine should automatically rotate images for the OCR output.

LAW PreDiscovery User Guide Reset Text Index Status De-selecting this option will prevent LAW from re-flagging the document for indexing after the OCR process is performed. See the Full Text Indexing topic for more information. This means the OCR text for affected records will not be searchable in LAW. 216 .

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

218 .LAW PreDiscovery User Guide The highlighted region can be removed by pressing the <ESC> key or moving to a new document.

check the OCR Options form and verify the required settings are selected. select Tools > Options and navigate to the OCR tab. If this setting is checked. Depending on the available licenses. PDF/A is only available with the ABBYY FineReader engine selected. From the main menu. Next. the thumbnails will be hidden under the Pages tab in Adobe Acrobat.the ABBYY FineReader license for LAW. Checking the OCR Settings Prior to creating the searchable PDF files. the OCR Engine should be set to either ExperVision OpenRTK or ABBYY FineReader. Create PDF Thumbnails The OCR engines automatically create thumbnails during the Searchable PDF creation process. 219 . the thumbnails will be viewable automatically in Adobe Acrobat.Batch Processing Creating Searchable PDFs The following feature requires the OCR (ExperVision OpenRTK) +OCR (ExperVision PDF add-on) licenses -OR. Use this setting to set the "visible" property of the thumbnails when opening the PDF file in Adobe Acrobat. otherwise. set the Output Format to Adobe PDF (w/Hidden Text) or Adobe PDF/A (w/ Hidden Text).

select the PDF Conversion format as Multi-Page. the resulting single-page PDF files will not be searchable. See the PDF Conversion topic to learn about more PDF export options. Exporting the Searchable PDF Files Once the searchable PDF files have been created. the documents are ready for the OCR process. 220 . LAW will export searchable PDF files. See OCRing Documents for information on how to OCR documents in LAW.OCR file (containing coordinates for on-image hit highlighting in Storm and IPRO). 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)"). those records will have an associated image file. a text file containing the OCR text of the document. Set the remaining export options according to the specifications for the project. (If the single-page export is chosen.LAW PreDiscovery User Guide Once the options are set.) The "Include Full Text" option does not need to be selected. In the Export Utility's Formats/Documents tab. See Export Utility Overview for additional information about the Export Utility. To export the searchable PDF files from the LAW case. an . This PDF+ file is the searchable PDF created by the selected OCR engine. and a PDF+ file. launch the Export Utility (Tools > Export Utility).

Keep this in mind before stamping a large set of documents. Note: Setting the border size has no effect on the image if no text is entered for a header or footer. This same header/footer may also be applied to printed images during batch processing. The "Synchronize fonts for all sections" setting allows users to automatically use the same font for all header/footer text. 221 . select Options > Header/Footer from the Batch Processing form. If the header/footer text is too large for the specified border size. Note: If trying to position text using spaces. although it will not be stamped on the image unless the endorse process is selected. Setting Fonts Fonts can be specified for each line of each section. Users should first test the specified header/footer on a small subset of documents to ensure it will fit within the specified border. This also makes it easy to remove or replace them after an image has been stamped. place the cursor anywhere on that line before pressing the font button ( ). To specify the header/footer. it will be cropped. To specify a font for a specific line. it is easiest to use a font like "Courier New" in which all characters are the same width. If this setting is checked. The default size of 1/2" is adequate for 2 lines of text at the default font size.Batch Processing Header/Footer Options A header and/or footer may be stamped on images during Batch Processing with the 'Endorse Image' process. LAW allows users to specify a maximum of 8 lines per section for a header/footer. setting a font for any line will cause the fonts for all header/footer text to be updated to the selected font. Setting Border Size LAW allows users to control the size of the border added to the images to hold the header/footer text. When applying header/footers. LAW adds a border to the image to eliminate the chance of overwriting image data.

Inserts "&[Page]". add "++" to the end of the field notation in the header/footer code. starting each document with the value in the DocID field.. a footer value of "&[DocID]++" would cause the documents to be endorsed sequentially. If the user does. which represents the page count. although this is not necessary if the user simply wishes to modify the existing header/footer. place the cursor on the desired area and either enter the text or press one of the buttons to enter a pre-defined value.Inserts "&[Pages]". Removing a Header/Footer LAW allows users to remove headers/footers. 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. of which the contents will be used (e. . To use this feature. For example. Auto-Incrementing Using Index Fields LAW can endorse documents with sequential values based on a starting value in a specified index field. need to remove a header or footer. The pre-defined values that can be entered are: . . do so in one of two ways.Inserts "&[Page ID]".Prompts user to select an index field.g. If the endorsement does not appear on the top or bottom of the image due to a manual rotation (as viewed in LAW). This allows users to endorse or print document level coding on the images. Caution: Use caution when working with rotated images containing an existing endorsement. . however. which represents the current page number. This will cause the Pages IDs or Bates numbers to be endorsed and/or printed on all of the pages.LAW PreDiscovery User Guide Setting Text To set the text for any area. &[DocID]). 222 . Either restamp with the border size set to 'None' or clear out the header/footer information of the part to be removed and restamp. which represents the Page ID. 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. Restamping with a new header/footer automatically removes any existing headers/footers and adds the new ones.

Warning: Endorsing with a watermark should be used with extreme caution as endorsed watermarks CANNOT be removed. if the source documents are TIFF images. A few common problems can result from the situations below: Unlike endorsements. Color formats should also be considered. so it is a good idea to run a few tests with a practice document to ensure the image is being applied as desired. 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. watermarks cannot be removed once applied. 223 . 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. Use the Alignment setting to specify the starting location of the watermark. Special Notes: It is important to understand how this feature works to avoid accidentally ruining documents in the case. The watermark image may either be applied during the endorse or print batch processes. use/create a watermark which is also a TIFF image using the same resolution as the original document. 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. If the watermark appears expanded or shrunk more than expected. If the text needs to later be modified. This feature is used to permanently "stamp" a group of documents with a specified watermark image selected in the Watermark File section. Some of the watermark's image data may exist in this region and would be lost in this situation. Applying a color watermark on a black and white document will result in a black and white watermark. re-applying the endorsement will cause LAW to remove the old header/footer and re-apply the new header/footer text. For best results. This can be useful when applying a specially formatted endorsement which may require graphics or special formatting not supported with the Header/Footer settings. it could be due to a large difference in the image resolutions.Batch Processing Watermark The Watermark Settings dialog can be accessed using the Options menu under Batch Processing. The watermark cannot be removed once it is applied.

LAW PreDiscovery User Guide White is considered the transparent color in a watermark. Different textures in other image editors may be used. Using the airbrush tool. using the Text tool. If the dimensions of the watermark are greater than the size of the document. open MS Paint. Choose Image > Invert Colors. 224 .thickness’ and re-invert the color again. First. Saving this image as a BMP and using it as a watermark will provide the effect of a transparent watermark. When testing the watermark. GIF images with transparent regions are not compatible with this feature. also consider testing rotated or oversize images which may exist in the case. the watermark will be shrunk and fit to page. Creating a Custom Watermark A custom watermark may be created using any type of image editing application. 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. type the word to include in the watermark. Then. airbrush the white text to the desired ’r. The following is an example of creating a black and white semi-transparent watermark using Microsoft Paint as the image editor.

Enabling these two options also enables the printing of color separator pages.) This dialog can be displayed by selecting Options > Print Options from the Batch Processing form. This feature will also work with documents containing mixed paper sizes. the "Send jobs in batches of N pages" must also be enabled.. In order for this option to work. Auto-Rotate Pages This setting causes pages to be rotated 90 degrees if they are landscape.Batch Processing Print Options The Batch Print Options dialog contains advanced print options available during the batch printing process. If Auto-Size Paper is selected while "Send jobs. a message box will appear stating the feature requires it and will enable the option automatically.. For example. LAW will detect the page size and send it to the paper size that most closely matches the original size of the image." is not selected. for this example. (This batch process if for image printing only-see E-Print/Tiff Output Settings for native file printing settings. the document would be printed on legal sized paper. 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. 225 . 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 ½".

Clicking the Options button will launch the Separator Page Options dialog and allow customizing of separator pages for the print job. 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. 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. 226 . Batching the documents into large print jobs prevents the print spooler from reorganizing documents in most cases. The Paper Source setting determines the paper tray used for the separator pages. As such. If needed. With this feature enabled. Experiment to determine the actual trays used before batching a large set of documents when using this feature. This can be beneficial for slower printers by minimizing the amount of information queued at any one time. 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 allows the separator pages to be printed on color pages if the printer contains multiple trays. Using this feature also corrects the problem with documents being printed out of order by various digital printers. This feature can speed printing if using a PostScript printer driver as PDF is very similar in format to the PostScript format. For example. It can significantly improve printer performance for high-speed printers. The Print separator pages only option can be used to print only the separator pages for the selected documents. separator pages cannot be printed to a separate tray unless the "Auto-Size paper" is also selected. enabling separator pages to be pulled from an alternate tray than the actual images. some trays listed may have no effect on the specific printer model used. Rip to PDF Before Printing This setting causes LAW to convert images to PDF format before sending them to the printer. See the Separator Pages topic for more information on this feature. 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. If this feature is activated.LAW PreDiscovery User Guide Do Not Print Annotations Use this setting to exclude non-merged annotations from printed output. especially when printing a large number of documents with only a few pages each. This eliminates the majority of the extra time required by the printer for cycling down and then up again between documents. The spoolers used by many high-speed printers. 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. The actual documents will not be printed. in an attempt to reduce printing time. If this setting is disabled. requiring less work by the printer driver when printing. select the Options button (above) to configure the separator pages prior to printing. Include Separator Pages This setting causes separator pages to be included in front of each document. any non-merged annotations will appear on the printed output. Send Jobs in Batches This setting allows users to control the size of jobs sent to the printer. The available trays are determined by the specified printer driver and frequently apply to a wide range of models. Folder breaks can also be configured by clicking the above Options button.

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.ABC00382 227 . The count to the left of the hyphen will increment by one for each job. The <Description> will be replaced with the DocID. the <Description> will be followed by a hyphen and then "Break" for document separator pages or "Folder Break" for folder separator pages. although other models may in fact work as well. LAW will use whichever item is found first in the order shown. If "Send jobs in batches of N pages" is enabled. For separator pages. BegDoc#. or ID for documents. the <Description> portion will not be present as the job would contain multiple documents.<Description>.Folder Break Example (document break): LAW Batch 000277 .Break Example (document): LAW Batch 000278 . Example (folder break): LAW Batch 000276 . 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 .

Active Printer .Indicates the printer that will be used to print the native files to paper. E-Print Options The "E-Print" category in the E-Print Options contains the active printer and separator page settings. 228 . See Supported File Types for a list of source applications and supported file types. such as tray assignments. The E-Print settings can be launched by clicking Options > E-Print Options in the Batch Processing dialog.LAW PreDiscovery User Guide E-Print/TIFF Output Settings The E-Print and TIFF Conversion options are essentially the same. Click Setup to configure any printer-specific settings. with the exception of specific output and printer settings. 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. as both processes involve the printing native files in LAW. while the TIFF Conversion settings may be found under Options > TIFF Options.

The actual documents will not be printed. Print separator pages only .e. BegDoc#. this feature enables the printing of separator pages between documents and/or folders..Separator Example (error placeholder . Folders .E-Print): LAW Batch 000276 . LAW will use whichever item is found first in the order shown.This option can be used to print only the separator pages for the selected documents.Folder Break Example (document break . Select <Custom> to enable the Options button.ID000384 .Placeholder TIFF Output Options The "TIFF Output" category in the TIFF Options will contain options specific to the tiff image output (i.ntv. making QC of print jobs via the print spooler easier to perform: LAW Batch 000000 .When selected.doc. The name of the print job for native files will display in the spooler as the filename stored in LAW.E-Print): LAW Batch 000277 .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). Clicking Options will launch the Separator Pages Options dialog and will allow customizing of separator pages. Included .Select a printer tray from the drop-down to print separator pages at the beginning of each new folder when printing. The count to the left of the hyphen will increment by one for each job. The <description> will be replaced by "Separator" for document separator pages and "Placeholder" for documents that error during TIFF Conversion.Batch Processing Print Separator Pages .ID000385 .<description>. Select a predefined template from above or click the Options button to configure custom separator pages. such as 01. Example (folder break .TIFF Conversion): LAW Batch 000278 . See the Separator Pages topic for more information. Excluded . Folder breaks will not have the document identifier as they are not associated with a single document. Template .<document identifier> . The <document identifier> will be replaced with the DocID. 229 . Print Jobs Each separator page or placeholder sent to the print spooler will be named in the following format. or ID for document separator pages and placeholders that are generated for documents that error during TIFF conversion.Select a printer tray from the drop-down to print separator pages in front of any "included" file types (supported for printing). format and color) and placeholders.Contains a list of available templates for the separator pages.

The images created by this printer will always be forced to 300 DPI. then 230 . Note: The LexisNexis Image Driver. the LexisNexis Image Driver is the supported printer for TIFF conversions.LAW PreDiscovery User Guide Active Driver: Stores the active tiff printer driver. Limited technical support will be provided for this driver. and Peernet TIFF Image Printer version 7.0 is not officially supported on Windows Vista.2 and higher. 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. is now included in LAW full installs and can be used for batch TIFF conversion and single document TIFF conversions. The Informatik Image Driver version 4. but can still be used for batch and single document TIFF Conversions. Also included with the LAW full installer is the LexisNexis Image Driver (300 DPI) printer. LAW currently supports the Informatik Image Driver. Click Setup to configure printer-specific settings. LexisNexis® Image Driver. If the image contains any color. Note: The Informatik Image Driver is no longer included in LAW full installs for versions 5. Unlike other supported drivers. the LexisNexis Image Driver supports text extraction during conversions. based on the Zan Image Printer. and LexisNexis® Image Driver (300 DPI) (both included with LAW).0 (must be purchased from Peernet).

To edit the default list of file types for this feature. 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. These file type ID numbers correspond to the ID numbers stored in the file type database used by the ED Loader. See the Separator Pages topic for information on customizing placeholders. If the multi-page format is selected. and no compression settings may also be used. LAW will detect any blank pages created during the tiff conversion and remove them from the output tiff image. Treat native TIFF images as image for record (bypass TIFF conversion): When enabled. LAW stores the output tiff images in the <case root>\$Image Archive folder. but the file sizes will be larger than the JPEG format and may not be viewable in the destination application. An error will be logged if an image is not a supported file type. Right-click the text and select Open Text (Printed). LAW will copy the native TIFF image file from the $EDD\$NativeFiles folder and place it in the $Image Archive folder. Output Format: LAW can produce output tiff images in either single-page (serialized) or multi-page format. Drop blank pages: When selected. The 'Reduce to grayscale' setting will reduce color images to a grayscale format. and 146. Select the document and then select the Text tab. See "Template" below for more information. Use this feature to force those documents over a certain file size to be converted serialized instead of multi-paged. LZW. Note: Adobe PDF files are not supported for text extraction during TIFF Conversion. File IDs can be removed from the list and/or other image file IDs can be added. each document will have its own tiff image associated with it containing all the pages of the document in the single tiff file. select <Custom> from the drop-down list and then click the Options button. LAW will produce a placeholder image for any documents that received errors and could not be converted to tiff. The File ID column contains the ID number for each file type.ini file located in the application path (i. The most widely supported and more commonly used format is the JPEG compression format. Save text with images (LexisNexis® Image Driver only): When enabled. Print placeholders for documents that error during conversion: When enabled. Print placeholders for unsupported/excluded docs: With this setting enabled. Color Compression: The Color Compression setting allows users to specify the compression type of the produced images. separated by semi-colons. 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.Batch Processing the tiff image will be saved in a color tiff format. the image will be saved as black and white. 298. place the following setting in the LAW50. By default. if no color is found. To view a list of all file IDs and their associated file extensions. 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).De-selecting this sub-option of "Save text with images" will prevent LAW from reflagging the document for indexing after the TIFF conversion and printed text is created.298. this feature applies to the following TIFF image file type IDs: 321. This format will also produce the smallest file sizes compared to the other two formats. See "Template" below for more information. The Packbits. click File > Import > Electronic Discovery and then click Tools > File Type Manager within the ED Loader. Reset text index status . To customize these placeholder images. This text can be viewed from the main LAW window. Overwrite Existing Files: With this option selected while tiffing. LAW will print a placeholder image for any documents that were included for printing but did not have a source application assigned. the LexisNexis Image Driver will extract text from documents during the TIFF conversion process.146 The default types are shown above. LAW will overwrite any existing images that were created as a result of the TIFF Conversion batch process. This means the printed text for affected records will not be searchable in LAW. C:\Program Files\Law50): [TreatNativeAsImage] ImageFileTypes=321. 231 . This feature is limited to image files that are supported by the imaging toolkit used by LAW.e. See the Full Text Indexing topic for more information.

8. LAW will use whichever item is found first in the order shown.Placeholder 232 .<document identifier> . or ID for document separator pages and placeholders that are generated for documents that error during TIFF conversion. The count to the left of the hyphen will increment by one for each job.5x11) instead of using the treat native as image setting can prevent this issue. The <document identifier> will be replaced with the DocID. Converting the image to a larger TIFF image (i.Folder Break Example (document break .E-Print): LAW Batch 000277 . The <description> will be replaced by "Separator" for document separator pages and "Placeholder" for documents that error during TIFF Conversion. and drop blank pages settings to a copy of the native image. If the image dimensions are very small. color compression.E-Print): LAW Batch 000276 . output format (multi-page or serialized). BegDoc#. The modified image is then saved and moved into the $Image Archive folder. Folder breaks will not have the document identifier as they are not associated with a single document. the endorsement may appear quite large on the image or be unviewable. Tracking Print Jobs in the Spooler Each separator page or placeholder sent to the print spooler will be named in the following format.e.Separator Example (error placeholder .ID000385 .TIFF Conversion): LAW Batch 000278 . such as 2x2. When selected. ▪ Force TIFF conversion settings on native TIFF images: When enabled. Example (folder break .ID000384 . 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. such as 01. LAW will apply the active color reduction. any currently selected settings will remain as the default selections for all new cases.LAW PreDiscovery User Guide Note: Use caution when adding file types to the list if planning to endorse the "native image" files.<description>. 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. making QC of print jobs via the print spooler easier to perform: LAW Batch 000000 . The name of the print job for native files will display in the spooler as the filename stored in LAW.ntv.doc.

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

a free viewer can be downloaded from Microsoft.bat.tif. a user imports a text file into LAW and sets the SourceApp to Shell Printer. you must have Microsoft Excel installed. *. *. The output image will be added to the record in LAW. In order to use the "Snapshot Viewer". 234 . LAW also supports printing zipped archives (*. For example. if you can right-click on a file in Windows and select Print. then the application supports command line printing. Special File Type Notes LAW does not support printing Lotus 1-2-3 documents directly. The contents of the archive will be processed according to the specified file types for printing. Printing WordPerfect files to MS Word may require an additional add-on found on the MS Office installation CD. *. *. to print the file through the associated application. use Microsoft Word or the Shell Printer as the source application. 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. The filename extraction format for Zip files is in the format <Archive>^<Filename>. *. Notepad supports shell prints.awd. In order to print these documents. On the user’s computer. This is a limitation of the underlying component.rtf. *. To print Unicode text files.bmp. When the Shell Printer is set as the SourceApp for a document in LAW. *.ini. *.java. *. *. If this add-on is not installed prior to printing WordPerfect files.jpg. If Microsoft Access is not installed. If a zip file happens to contain a zip file.exe). For example. Z-Print will recursively open the archives and process the supported file types.pex.dcx.gif. *. you must ensure that the application registered on the system for text files supports shell prints.LAW PreDiscovery User Guide Text/RTF Printer *.vbs. When the user converts the file to TIFF in LAW.txt. If Microsoft Office with Access is installed. Zipped files will automatically be included in both file and e-mail print jobs. In other words. RTF with Unicode is supported.cpp (and various other text based types) Note: Unicode text files are not supported with the Text/RTF Printer. it can be added from the Office installation media. If using the Shell Printer. Word will be unable to recognize the file format and an error will be logged. *. you must install support for the Microsoft Access Snapshot Viewer.zip) and self-extracting zip archives (*.xif The Shell Printer source application can be used to print file types through any application that supports command line printing. Image Printer Shell Printer *. However. Notepad will be used to print the file to TIFF. as it would when using any other SourceApp. *. text files are associated with Notepad.

The last viewed tab remains the default. Printing files with VoloView Express (*.htm and *. as opposed to 2008 which is the only version supported with previous versions of LAW. By default LAW prints these two file types to Internet Explorer due to issues with Word. select the Drawing Settings tab.14 and above.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. open a document. To ensure it works correctly. the page count will return 1 if the file is exactly 1 page long. 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. In LAW versions 5. 235 .html files. and click OK. 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.Batch Processing Both Internet Explorer and Word are capable of printing *. Note: HTM and HTML files will always return a page count of 1 if the source application is set to Internet Explorer. It is recommended to uninstall version 2008 prior to installing 2009 and using it as a source application in LAW. or it will return 2 pages for any document containing more than 1 page. This tab should remain the default tab allowing LAW to send the appropriate messages to the dialog.3. 2009 is the only version of eDrawings supported as a print source application. If the source application is MS Word.

If necessary. 236 . and choosing the desired Print Method. this setting may be modified by enabling Allow Binary Data. 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.LAW PreDiscovery User Guide Acrobat If experiencing problems while printing Adobe Acrobat files.

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.NSF) must remain in same location from which they were imported. Note: When using this option. the output retains the original Lotus formatting. The E-Mail option requires access to the source mail store during the print process. attempts to access the store will fail and error messages will be logged for all e-mails. Using this option. including inline images and RTF content. the Lotus mail stores (*. 237 . If the mail stores are moved after the import. The E-Mail option is selected by default for new cases.

. If this option is not checked. only the information contained within the page break boundaries will be printed. QC of Excel files for readability and formatting purposes after being printed to TIFF or paper is recommended. These options will help standardize the format of the Excel files being processed. Excel will determine it to be important printable information. 238 . 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. If this data exists.000 column AAA. Excel documents will be printed based on how the document was saved. then the user would check the "Override Default Settings" option. An Excel file can contain a very small amount of information (e. page boundaries can be difficult to determine through Excel. If this option is not checked.g. Note: Excel automatically determines the printable area of a document when using this feature. This feature is helpful for guaranteeing that all Excel files are being processed with the same settings. so it is important to QC Excel files after printing. a space or formatting data) in row 10. Since spreadsheets are not limited to physical paper constraints like a Word document.LAW PreDiscovery User Guide Excel The many options in LAW for printing Excel documents can be found in the Excel category in the e-Print and TIFF Options. LAW is currently unable to prevent this type of situation. For example. the spreadsheets’ page boundaries may need to be adjusted manually to format the output correctly. for example. In some rare cases. which may then result in numerous (sometimes thousands) of blank pages being printed. 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.

Batch Processing Orientation Use this option to select the orientation of the pages to be printed (portrait or landscape). Fit to Page . Caution: This option may cause unreadable or extremely small font sizes if the sheets are very large.Forces the entire spreadsheet to fit onto one page when printed. Scaling Auto-Size Columns . 239 .Adjusts the column sizes so the information contained within the cells is not "cropped" or hidden by an adjacent cell. This feature is not recommended if printing Excel files with unknown content or large amounts of data per sheet.

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.Comments saved in the Excel files can be printed using this option. This warning will also be logged in the event the actual page count happens to match the limit specified in the options . and Show field codes. and Show field codes. This can be helpful if a header contains date information that the user does not want included in the output. removing all background colors and forcing all text to black. Print black & white . the following warning will be logged to the ErrorMsg field: [tiff]: Output limited by Excel page count threshold (ErrCode=-1. 240 . if selected.Prevents sheets from including headers on processed documents when disabled. Do not print.LAW cannot filter out these occurrences.This option allows the selection of one of five items: Do not modify (print as is). Row and column headings . which will act the same as disabling the setting (does not limit pages printed). Footers . The maximum value is 99999. Remove repeating columns . Page Order Down. Replace with modified date. If this setting is enabled. They can be shown 'As Displayed' (as saved in the Excel file) or at the 'End of the Sheet'.Displays the gridlines or cell outlines in the spreadsheet if selected. then down the columns and back over. Headers . Hidden columns/rows . Limit output to <N> pages: Limits the number of printed pages to the number specified in the text box. Date/Time Fields . The minimum value for this setting is 0.Forces Excel documents to be printed as black and white only. which can prevent unnecessary parts of a worksheet from being printed. if selected. Remove repeating rows .Prevents any columns set to repeat from repeating in the tiff output when selected. Line=3780). then Over . Replace with date created.Causes the spreadsheet to be printed across first. Replace path from filename. then Down . all background fills and patterns are cleared. When LAW limits the number of pages for a file. Filename Fields .Prevents any rows set to repeat from repeating in the tiff output when selected.Prints any hidden sheets contained in the Excel file when selected. Do not print.Prints any columns and rows that have been hidden when selected.Includes the headings in the printed spreadsheet when selected.This option allows the selection of one of four items: Do not modify (print as is).Causes the spreadsheet to be printed down the sheet. 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. then over and back down.LAW PreDiscovery User Guide Print Gridlines . This can be helpful if a footer contains date information that the user does not want included in the output. Hidden sheets . Over. Comments .Prevents sheets from including footers on processed documents when disabled.

there is no way to test every possibility and LexisNexis cannot absolutely guarantee the quality of any third-party product. LexisNexis STRONGLY encourages users to perform their own tests on some small samples and perform periodic QA on any output produced with this engine.Removes the indentation from e-mails converted to HTML for printing.Batch Processing HTML This category contains options for HTML documents printed to paper or tiff through LAW. 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. Although substantial effort has been taken to verify the output of a wide array of HTML documents printed using this engine. However. 241 . 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. Before using this alternate engine for large scale productions. This setting affects only printed output and does not directly affect the native files. Remove indentation from presaved e-mails (HTML) when printing . Use alternate HTML rendering engine for Internet Explorer . If enabled.This HTML engine will increase print speeds dramatically for HTML documents printed using Internet Explorer.

making the printing of such images easier to print to paper. some of the images would appear correctly in portrait.This feature will automatically rotate images printed through the Image Printer ONLY so each image is oriented consistently.LAW PreDiscovery User Guide Image Printer This category contains options for documents printed to paper or tiff via the Image Printer source application through LAW. This is useful for images containing a mixture of landscape and portrait orientations. Auto-Rotate Images . If printed directly to paper. 242 . and others would appear as a landscape image printed on portrait paper.

243 . while an unlimited number of passwords may be specified for Microsoft Office applications. Click Add to enter a password. Up to three passwords may be specified at one time for Adobe Acrobat.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.

This setting allows users to select the information to print from the document.Forces the PowerPoint slide to be scaled to the current page size. These are the header and footer sections which will be disabled for each slide if either of this option is enabled.Forces PowerPoint to print any hidden slides which may exist in the presentation. Print What . 244 . The contents of the header and footer fields can be viewed in PowerPoint under View > Header and Footer.. 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. Do not print headers/footers .Removes the auto-date and auto-time fields from a slide if they exist and prevents the printing of that information..LAW PreDiscovery User Guide PowerPoint This category contains options for Microsoft PowerPoint documents and will be used when printing to paper or converting to TIFF through LAW. Print hidden slides . Do not print date/time stamps . The two options are to print only the Slides or Slides and Notes. Scale to fit paper .Use this setting to disable the values placed in the header and footer sections of a slide.

Grayscale. the color reduction must be set to None or Reduce to optimal palette.Use this setting to adjust the color settings of the printed slide to either Pure black and white. 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. Note: This setting only affects how PowerPoint will send the file to the printer.Batch Processing Color mode . and if printing to TIFF. 245 . or Color. not the actual printed output.

Disables printing of footers contained within the Word document. 246 .This option causes Word to repaginate itself before printing which can prevent the last line from running onto the next page in certain conditions. Do not print footers .LAW PreDiscovery User Guide Word This category contains options for Microsoft Word documents and will be used when printing to paper or converting to TIFF through LAW. This can be useful if the original document contains information in the footer which is not desired in the printed output.Disables printing of headers contained within the Word document. Settings Do not print headers . Force manual repagination before printing . This can be useful if the original document contains information in the header which is not desired in the printed output.

. Filename Fields . Replace with modified date.e. In prior versions.Some Word documents may also contain tracked changes which can be printed through LAW by selecting this option. Replace with date created. the Track Changes Options in Word should be set to Use Balloons > Always. the notes will be printed after the last page of the document. Note: How comments appear in the printed output is dependent on the settings currently set in Microsoft Word on the processing station.Batch Processing Log warnings for Word 95/6. For example. Do not print. and Show field codes. and Show field codes. Printing of comments on the actual page where they occur is only available in Word XP and higher. Note: How revisions appear in the printed output is dependent on the settings currently set in Microsoft Word on the processing station. 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. Do not print. if balloons are desired. 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. Date/Time Fields . This makes it easier to isolate. 247 .This option allows selection of one of four actions: Do not modify (print as is). QC. white text on a white background) or text matching the highlight color in the source document.This option allows selection of one of five actions: Do not modify (print as is). Show comments . For example. LAW will only print the changes that have been made to the document if Track Changes has been enabled for the document. Replace path from filename.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.0 documents . Show revisions . and optionally reprint all Word 95 documents if needed. Reveal hidden text . Note: This setting is not recommended unless it is an absolute requirement.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. the Track Changes Options in Word should be set to Use Balloons > Always. It may slow the printing of Word documents dramatically. if balloons are desired.This option enables the printing of comments included in the Word document if present.

remember to configure the tray settings below the Print Separator Pages option. Separator pages and placeholders can be configured via the Separator Page Options form. Separator pages are useful for keeping documents and folders separate from one another and organized when dealing with hard copies. To access these options.LAW PreDiscovery User Guide Separator Pages Separator pages can be optionally inserted before documents or folders during the Print and E-Print batch processes. click Options > TIFF Options and choose the TIFF Output category. first click Tools > Batch Process to launch the Batch Processing dialog. for the TIFF Conversion process. LAW also allows the customizing of separator pages and placeholders for the E-Print. and TIFF Conversion batch processes. Note: After configuring separator pages for the E-Print process. choose <Custom> from the Template drop-down list. See the E-Print/TIFF Output Settings topic for more information. This form is accessible from three locations as it applies to three different processes. To configure separator pages for E-Print. Next. While pre-configured separator page and placeholder templates exist for the E-Print and TIFF Conversion processes. select one or both 248 . click Options > E-Print Options from this dialog and choose the E-Print category. Print. This topic discusses the creation of custom separator pages. To configure placeholders for excluded/unsupported documents. or documents that received errors. for information on the templates or other print functions. Next. see the following topics: Print Options or E-Print/TIFF Output Settings. enable Print separator pages. and then click the Options button.

click the button labeled with the letter "A" below the header sections if modifying a header. click Options > Print Options. enter the desired text into the text box below the section in the Header and/or Footer areas. font style. Doing so will enable the Placeholder Template drop-down.Batch Processing of the following options: Print placeholders for excluded/unsupported documents or Print placeholders for documents that error during TIFF Conversion. If modifying a footer. Select the Include separator pages option and then click the Options button. To configure separator pages for the standard image Print process. Header and Footer The Header and Footer sections are used to display custom information in the left. This text will then appear on the separator page or placeholder during the print or conversion process. To select a font. To display text in a particular section. The remainder of the topic will discuss the specific features available in this form. and font size. The Separator Page Options dialog will appear after clicking the Options in any of the aforementioned dialogs. choose <Custom> from the drop-down list and then click the Options button. Next. click the 249 . center. and/or right sections of the top (header) or bottom (footer) of the separator page or placeholder.

for unsupported file types. E-Mail. and the standard Print batch processes. this field will contain the following message: UNSUPPORTED OR EXCLUDED FILE TYPE. since the other types will not apply to this process. The Display As column can be used to force an alternate field name to be displayed on the separator page or placeholder. 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. Folder separator pages will be printed each time a new folder is encountered and will apply to the E-Print and Print processes.or page-level. The folder path. each type of placeholder is allowed to display different text values using different font settings. When enabled (checked). To enter a new display name for a field.Separator page and placeholder settings can be configured for the types listed in the drop-down. The selected font and text settings for the header and footer sections are specific to the currently selected placeholder type. Most system fields and all userdefined fields will appear in this list. double-click in the Display As cell beside the desired field and then key in the new name. The field selection will not apply to folder pages as the fields are only document. The placeholder type will be grayed out and set to "Raw Images" when viewing this setting via the Print Options. in addition to the specified header and footer text. tasks. font style. E-Mail separator pages will be printed in front of e-mail records and other store-based items including calendar items. The Fields section will be disabled when the Folder placeholder type is selected as field information does not exist at the folder level. This setting applies to E-Print. 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. the fields selected for the active placeholder type (type selected in Placeholder Type drop-down) will be applied to the File. will be printed on each folder separator page. The currently selected placeholder type will also appear in parentheses beside the Fields heading just above the Selected Fields list.When enabled. The File. Synchronize field settings for all types . (Fields do not apply to Folder separator 250 . If multiple placeholder types are available in the drop down box (possible with E-Print and TIFF Conversion). and Attachment separator pages and placeholders.LAW PreDiscovery User Guide button below the footer sections. If the Display As cell is blank. 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. TIFF Conversion. 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. and notes. and Attachment types will also be used as placeholders for excluded/unsupported records or as an error placeholder during the TIFF Conversion process. File separator pages will print in front of e-documents imported via ED Loader or XML load file. 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. 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. E-Mail. then the name in the Field Name column will be used. By default. journal entries. For E-Print and TIFF Conversion jobs. Each of the three columns in the Fields grid may be sorted ascending or descending by clicking on the desired column header. See the Options section below for more information on placeholder types. Placeholder Type . and font size for the field names and field values. ensure "Show Comments field" is enabled and then enter the desired text in the Unsupported file type message text box. Click the button labeled with the letter "A" to configure the font. The fields wrapped in < >'s are fields derived from the standard Default Template for each placeholder type. To customize this message. contacts.

Do not print field names for blank values setting. The values should be entered as twips as indicated in the interface (1440 twips = 1 inch). For example. if "Save settings as default" is enabled in the TIFF Options dialog. Left. This setting is unique to each placeholder type. The values will be forced to zero and grayed out when configuring placeholders for TIFF Conversion. Vertical field spacing (in twips) .exe). 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.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.The separator and placeholder margins can be modified by entering the desired values in one or more of the available text boxes: Top. file. separator. the current separator page settings will not be saved or affected in any way.ini file before looking in the application path.e. Margins .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. Enter values in milliseconds (1000ms=1 second) and test various values to determine what works best in your environment. When this option is selected. The margin settings are unique to each placeholder type. LAW will create a separator. Show Comments field setting.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). and Right. The print delay values are unique to each placeholder type. If settings are modified in a case and not saved as default. Note: This setting and the "Save settings as default" setting in the TIFF Options and E-print Options dialogs are independent of each other. LAW cannot always prevent every occurrence of this behavior but specifying a print delay can reduce the chances of this occurring. Print Delays (in ms) . 251 . Bottom. separator.) Also applied with this setting are the following: field fonts. The settings in this file will be applied to all new cases going forward.Batch Processing pages. LAW will always look for the case-level separator.ini file located in the application folder (same folder as law50. and the Unsupported file type message text box value. separator). Certain printers rearrange jobs in the spooler causing the printing of smaller files first while larger files are still spooling. the current settings will be saved to a separator.

while using the same settings that were specified on the machine that initiated the shared job. first select Tools > Batch Process from the main menu. This value will determine how the job is handled by other stations when utilizing the LMC. Click Begin to start processing. This batch name is also important for managing jobs in the LAW Management Console ("LMC"). In the Sharing section of the Batch Processing dialog. See the LAW Management Console Configuration topic for more information on managing distributed batches. The Type field reflects the currently selected invitation type. 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. 252 . select the documents to be processed. Shared processing is available for the following batch processes: Image Cleanup Endorse OCR TIFF Conversion Update Page Data Scan for Suspect Footers When a shared batch has been generated. This name is a reference for users to aid in identifying a batch and will appear on other workstations when prompted to join. Initializing a Shared Batch To initialize a shared batch. the user will be given the option to "Join" processing. Users could also run a query or perform a filter in the grid and then launch the Batch Process utility from the grid display. an INI file will be placed in the case folder (\$UserData\BatchProcessing\All Users) that uniquely identifies the batch. In the Batch Processing dialog.LAW PreDiscovery User Guide Distributed Batch Processing Distributed batch processing was designed to allow multiple LAW stations to process the same batch simultaneously. Only the documents selected on this initial machine will be processed. check the box beside the Enable Distributed Batch Processing option. Enter a Name for the batch. This directory is scanned for INI files when the Batch Process utility is launched and if any are present.

select Tools > Batch Process from the main menu. The Running Batches dialog will appear in front of the Batch Processing dialog. If a batch becomes available. click the View button to view the running batch. click the batch to select it in the Running Batches dialog. 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. 253 . Then. first open the same LAW case on another workstation. choose Edit > Delete. All active batches created in this case will be listed. This will launch the Running Batches dialog as well and allow users to choose a batch to join. The shared batch will be deleted from the list. Next. To delete an incomplete batch that is no longer needed.Batch Processing Joining a Shared Batch Once a distributed batch has been initialized on one station. Note: If "Cancel" is chosen on the Running Batches dialog. The batch may also be started by clicking View in the Batch Processing dialog in the Sharing section. it will no longer appear as a "running batch" in LAW. other machines can join and assist with the processing. Deleting Shared Batches Once a shared batch has completed successfully. the batch will not be cancelled on other stations. To join. Note: If the Running Batches dialog does not appear as expected. Locate the desired batch and highlight the name in the grid. try clicking the Refresh button in the Sharing section of the Batch Processing dialog. Click Join.

3. the local instance of the LMC will be used when using the method listed next. The local instance of LMC will be launched at this time and will be executed each time Windows is started. The executable file used to run the LMC is LAWConsole. a message will appear prompting to launch the LMC. By default. allow available LAW workstations to join jobs automatically. and the LMC is not running.exe. The LMC will run on each workstation running LAW PreDiscovery. 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.exe in the Console folder. this location is C:\Program Files\Law50\Console. The console may be started using the local instance or using a shared EXE file. These features are only applicable to jobs and workstations that have been made visible to the LAW Management Console by LAW (see Configuration). Double-click the LAWConsole. 255 . When the box is checked. When the LMC instances on individual workstations are connected to the same SQL Server (the server used to create LAW cases). The application can be started on each LAW machine using one of two methods: 1. This application also displays license information for workstations visible to the LMC. and monitor license usage. The information recorded on each workstation is stored in a central location and shared with other LMC instances. the LMC will also list distributed batch processing jobs in SQL cases.14 and above. The application is located in the Console folder within the LAW installation folder. Licensing details can be viewed by clicking the Licenses node or on an individual key. Click Yes.LAW Management Console LAW Management Console LMC Overview The LAW Management Console ("LMC") is a companion utility to LAW PreDiscovery versions 5. Please note. In addition to displaying clients and client details. Startup The LMC is included with the full installs of LAW as well as the updates. Check the option Start the Management Console on Windows Startup in LAW (Tools > Options > Preferences). 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. 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). A tally of all licenses can be viewed here as well as license details for each individual key. 2.

an icon will appear in the system tray. the application can be restored by single-clicking the icon in the tray or right-clicking and choosing Restore. Once restored. A client represents a workstation running an LMC instance. each LMC instance is represented by that workstation’s computer name. but not close the application. The icon will be green when the application successfully connects ( ) and red if the application fails to initialize ( ). See the Configuration topic for information on the initial configuration of the LMC and creating batches in LAW. the minimize and close buttons in the upper right-corner will both minimize the application to the system tray. 256 . right-click the icon in the system tray and choose Quit or press Alt+F4 on the keyboard while the application is in focus. To completely exit the LMC. After the LMC is added to the system tray. An LMC instance is referred to as a "client" throughout the related Help topics.LAW PreDiscovery User Guide Once the LMC is running.

information about connected clients (workstations running the LMC and connected to the same SQL Server).LAW Management Console 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). 257 . it will attempt to pull SQL information from the law50. Enter the SQL login information (see Configuring LAW and SQL Server) and then click Accept. The SQL Server used when connecting the LMC should be the same instance used to create the cases in LAW. or the LMC is unable to connect to the server at that time. an error will appear in the right panel of the main interface. 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 icon will remain red. With minimal initial configuration. If able to connect successfully.When this option is chosen. the LMC can begin providing these services and eliminate multiple steps involved with distributed batch processing and license tracking. 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. and the SQL Connection Information dialog will reappear also displaying the error message. I have a SQL Server and would like to configure the LMC client to remotely manage shared batch processing jobs. If this information is not available. an introduction screen will appear. . 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.ini file in the application path ([SQL Server] section). the LMC icon will turn green. When the LMC is launched for the first time on a machine (see LMC Overview). the progress of the jobs. the Server Connection Information dialog will appear. Three options are presented: 1.

To remove the application from the system tray. the LMC will be completely closed and removed from startup.When this option is selected. displaying the machine name of the current workstation below the Clients node. To launch the LMC at a later time. The first panel in the task bar in the main interface will also display a status of "Connected to" followed by the server name.ini and was able to connect successfully. 3. the LMC icon will remain red and it will be minimized to the system tray. I do not have a SQL Server or do not plan to use the client.LAW PreDiscovery User Guide 2.When this option is chosen. . . the LMC will bypass the introduction screen and the main interface will appear. The introduction screen will appear once again if the application is restored at a later time. If the LMC was able to locate SQL information from the law50. but would like it to remain running in the system tray for future configuration. 258 . use one of the methods discussed in the LMC Overview. right-click the icon and choose Quit. I do not want to configure the client right now. The introduction screen will appear once again and the three options listed here will be presented. Close the client and remove it from system startup.

Creating a Shared Batch in LAW In order to utilize the batch processing management features provided by the LAW Management Console. view the invitation “Type” listed below the Name field. Create or open a SQL LAW case to create the shared batch. Remember. click Server > Connect from the main menu. that job’s progress will be visible to the LMC. the LMC will pull SQL Server information from a local configuration file (%AppData\LawConsole\LAWConsoleSettings. then the LMC will use the SQL information stored in the application path (LAW50 folder) in the law50. Select one or more of the six processes supported for job sharing: Image Cleanup Endorse OCR TIFF Conversion Update Page Data Scan for Suspect Footers Enter a name for the batch in the Name text box. the clients must be connected to the same SQL Server. click Server > Disconnect. To disconnect from the current SQL Server. Click Tools > Batch Process. When a job is visible to the LMC.ini file. To change the SQL Server used with the LMC. When the Batch Processing dialog is launched. the distributed batch process must be created in a SQL case. If this file is not present or does not have valid SQL information. in order to view information about other workstations running the LMC client.ini).LAW Management Console Configure the LMC clients on other workstations when running the LMC client locally rather than using a shared EXE. 259 . and then enter the SQL Server name and credentials. Next.

LAW PreDiscovery User Guide All shared jobs are created with an invitation. 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 . 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.

If one of those five stations was restarted. 2. Open: All LMC instances will 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. 261 . but are sorted visibly by name under the Jobs node. 2. the job will appear below the Jobs node in the LMC. There are currently three types of invitations: 1. Jobs will be joined in the order in which they were created. Other LAW workstations can now join the job automatically provided certain criteria are met. open the SQL case. Similarly. If these conditions are met. Closed: (Default) None of the LMC instances will be able to auto-join LAW to the shared batch. Automatically Joining Shared Jobs The LMC's ability to join LAW workstations to a shared job in an unattended manner relies on certain conditions. instances of LAW on other workstations will be joined to the job automatically. The next section discusses these criteria in more detail. the applicable machine name(s) must be selected in the invitation editor when creating the batch or at any time via the LMC. Once the shared batch has been initialized on a machine. if a shared batch is created named TIFF01 and the invitation type is set to Open. Restricted: Only LMC instances specified in the Create/Modify Job Invitation dialog will auto-join LAW to the shared batch. 3. LAW is not running. if Restricted is selected. 3. Clients not selected in this dialog will not attempt to join the batch. then the job will be ignored until after 1am. then it would be subject to the change in the invitation. LAW will launch.LAW Management Console Note: Changing an invitation only affects the behavior of LMC instances that have yet to auto-join the job. and begin processing the job without user interaction. but the user specified that the job cannot be joined until 1 am. The station is in a "system idle" state (see Operation). the invitation may contain a timestamp restriction. Invitation must be set to Open or Restricted. those five stations will be unaffected by the change in the invitation and will continue processing. The LMC client must be connected to the same SQL server in which the case database is stored in order to see the job. For example. 1. The LMC client must be running on the machine. In addition to the type of invitation. Check the boxes beside the desired clients. then this will take precedence over the invitation type. LMC clients must be connected to the same SQL server in order to “see” each other in the console. Provided the criteria in the "Auto-joining Jobs" section (below) have been met. If the invitation specifies that the job cannot be joined until after a certain time. 4. a. If the invitation is changed after five stations have joined.

The job’s status must be Active (see the Operation topic for possible job status values). and joining the batch process (Tools > Batch Process). This value is set within the LMC in Tools > Options > General > System Idle Timeout. The system idle timeout value for each client station must be greater than 0. As discussed in the Distributed Batch Processing topic. The Operation topic will discuss the components of the LMC interface and application usage. When the workstation is idle (no keyboard or mouse movement) for the specified number of seconds. it will report the station’s progress in the same fashion as if the LMC asked LAW to join the job. Currently. 5. If a companion LMC instance is running. 6. LMC does not indicate if a job was joined manually vs.LAW PreDiscovery User Guide a. Invitations and Exclusions (see Operation) do not restrict a manual join. 262 . opening the case. The client is not Excluded (see Operation). 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. automatically. jobs can also be started manually by opening LAW.

Multiple views are available in the LMC to monitor these clients and workstations. LAW Version . Case .LAW Management Console Operation Once the LMC has been configured and one or more shared batches are visible within the LMC (see Configuration).Displays the name of the LAW case currently open on the workstation.Machine name of the connected client. Status . 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. User . The LMC can also report license usage for these LMC-visible workstations. The clients overview panel displays the following information about each client: Computer .Displays the status of the workstation. Client Overview Selecting the main Clients node will display an overview of information about these workstations in the right panel. this field will be blank. If LAW is not running. 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.Displays the name of the LAW case currently open on the workstation. Possible values are: 263 . Running .Displays the user currently logged in on the workstation.Indicates if LAW is running on the workstation.

LAW PreDiscovery User Guide

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

LAW Management Console

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: Job Name - Corresponds to the value entered in the Name field when creating the batch in LAW (Tools>Batch Process dialog). 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

LAW PreDiscovery User Guide

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

LAW Management Console

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

LAW PreDiscovery User Guide

The Job Details section contains six information fields, a Cancel Job button, and the invitation editor: Job Name - Corresponds to the value entered in the Name field when creating the batch in LAW (Tools>Batch Process dialog). 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

LAW Management Console

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

LAW PreDiscovery User Guide

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

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). and visible to the current instance of the LMC.LAW Management Console LAW's action after the cancellation may differ depending on how LAW was started.Lists all license modules found on the keys listed below the Licenses node. 271 . The licenses overview panel displays the following information: License . The number in parentheses beside the term "Licenses" is the total number of keys on workstations running the LMC. and was joined to the batch via traditional means. Total . If LAW was started in an automated fashion via the LMC. then LAW will behave in the same manner as if the Cancel button was clicked. 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. In Use . not connected to SQL.Displays a total count of each license module found on the collection of keys listed below the Licenses node. Note: If a workstation is accessing licenses. but not running the LAW Management Console. that workstation's license usage will not be reported in the LMC interface. or is connected to a different instance of SQL than other workstations.Displays a total count of available licenses for each module for all keys listed below the Licenses node. If LAW was started manually. connected to the same SQL Server. Available .

only clients connected to the same SQL Server instance and running the LMC will report their key usage to the LMC. 272 . 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 details panel will look very similar to the overview panel with some exceptions. 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. The machine names and user names will be displayed. As mentioned.LAW PreDiscovery User Guide Clients using '<license module>' . License Details Each individual license key will be listed below the Licenses node in the left panel of the LMC.Displays a list of clients using the module selected in the license module list.

The Deduplication Utility can be launched by clicking Tools > Deduplication Utility from within LAW. At this point. a warning message will appear when the utility is first launched: Warning: As indicated in the warning message above. Also. discussed below: Info. 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. 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. If the case has not been already deduplicated using the Inter-Case Deduplication utility. filtering. See the Deduplication Information topic for more information. The utility contains three tabs. the Info tab will appear displaying a Load button. This utility may be used if deduplication was not performed when importing via the Electronic Discovery Loader or using the Inter-Case Deduplication utility. For more information. see the Inter-Case Deduplication topic. or reviewing duplicate records. 273 . Info Tab If the current case has already been deduplicated externally using the Inter-Case Deduplication utility. Tools. before running the internal deduplication. Click the X in the upper right corner to close the dialog. and Settings. the current case should be removed from the external database. 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.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. Doing so will present a mixture of internal and external duplicates and could cause problems when purging.

LAW PreDiscovery User Guide Click the Load button to retrieve the current deduplication statistics for the LAW case. 274 . such as number of duplicates (global or custodian level) and number of root duplicate records.

Click on each item in the Info tab to view its description as shown in the above image. Settings Tab The Settings tab contains processing and processing range options. 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). 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. If records had been deduplicated externally (see above). the entire case will be in a state as if deduplication has never been performed. This tool is included for troubleshooting purposes and does not check external deduplication databases. the values for each displayed item will be zero. As mentioned above. 275 .Deduplication If deduplication has not yet been performed on the records. two additional rows would be included here to show the "Records deduplicated externally" count as well as the "External deduplication database" path. The Verify Deduplication Log tool will verify that all entries in the log exist in the LAW case. 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. In other words.

this option will force LAW to only process records that have not been tested previously in the deduplication process.When enabled.LAW PreDiscovery User Guide Working digest . Test for duplicate against (Scope) . Only test records with selected custodians . LAW provides two hash keys to choose from: MD5 (128-bit output) and SHA-1 (160-bit output). only untested records with the specified custodian values will be tested. 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). this option allows the specification of one or more custodians and forces LAW to process only records with those custodians during deduplication.This setting pertains to the scope in which duplicates are tested.This setting is used to select the hash key to be used for determining duplicates. Click the Select button to launch the Custom Value Selection [Custodian] dialog. 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 . The hash values are obtained through metadata fields (e-mail) or by hashing the entire file (e-docs). If the "Only test records with selected custodians" option is also enabled. 276 .When enabled.

The number of selected custodians will appear beside the Select button in the Settings tab.Deduplication Check the boxes beside the custodians to include them in the deduplication process. The Reset button can be used to reset any options that were modified in the current session. Click Accept to save the changes and close this dialog. 277 . Click Start to initialize the deduplication process.

To start. Records added to these cases during subsequent imports can also be deduplicated.LAW PreDiscovery User Guide 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). 278 .exe file). and filtering duplicate records caused by a mixture of internal and external duplicates existing in the case. These cases are ready for inter-case deduplication once they have been populated with records via the ED Loader import. the Inter-Case Deduplication utility enables deduplication across LAW cases. open the utility by clicking Start > All Programs > LAW PreDiscovery > Inter-Case Deduplication Utility or double-click the InterCaseDedup. or after the import against other records in the case and other LAW cases (covered in this topic). the case should not be deduplicated using the internal Deduplication Utility.exe file in the \Law50 folder (same folder as Law50. and incoming documents should not be deduplicated using ED loader. A master database (separate from the LAW database) is created to house the deduplication information for the cases. Once a case is deduplicated externally using the Inter-Case Deduplication utility. Doing so can lead to issues with purging. See the Deduplication and/or Deduplication Utility topics for more information about these risks and associated warnings. reviewing. after the import against other records in the case (Deduplication Utility in LAW). Unlike other methods. The Inter-Case Deduplication dialog will appear.

If the database has already been used in the inter-case deduplication process. To open an existing database from a previous deduplication session. The next step is to set the deduplication options (see the "Options" section below).This hash value is stored in the MD5Hash field in LAW for each document.Records will only be deduplicated against others records with the same custodian assigned. Custodian Level . and both SQL and Access cases are supported. 279 . The "Mode" value will change from "No Database Selected" to "New" at this time. b. move to the Member Cases area to add LAW cases. SHA-1 (160-bit output digest) . Two options are available: a. and then click the Save button.Records will be deduplicated against all records in all member cases. click the ellipsis button to the left of the New button or choose File > Open. If documents are added to the cases after the inter-case deduplication process. See the "Deduplication Mode" section in this topic for more information. click the New button or choose File > New. As noted in the description in the interface. It is recommended that this database be placed in a shared location accessible to all member cases (see "Member Cases"). The external deduplication database is a "master" Access database (*. b. 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 will be deduplicated against each other in the inter-case deduplication process. this mode indicates that all documents in the member cases will be deduplicated against each other. Browse to the desired location in the Create Deduplication Database dialog. they can be deduplicated against the other records as well. Records with no custodian value set will be evaluated globally. 2. The path to the database will now be displayed. and then click Open.Deduplication External Deduplication Database The first step when using this utility is to create a new database (or open an existing database). This type of deduplication is intended for cases that are already populated with documents imported via the ED Loader. To create the external deduplication database.The digest refers to the type of hash that will be used to determine duplicates.This hash value is stored in the Sha1Hash field in LAW for each document. These cases must be ED-enabled. Global . See the "Resume/Append Mode" section below for details. See the "Member Cases" section for details. the Mode will change to Resume/Append.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. Digest . the utility will obtain information from the LAW case databases during the deduplication process. 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. browse to the external deduplication database. MD5 (128-bit output digest) . however. Once the desired options have been set. Scope . Options Two deduplication options are available for the inter-case deduplication process: 1. change the file name or use the default (DuplicateLog).This option refers to the scope in which duplicates are tested.

and errors at a case level. These buttons can only be used in New or Rebuild/Flush mode. The Inter-Case Deduplication Progress screen will appear. See the "Summary" section below for more information regarding errors and logging. click Begin to start the inter-case deduplication process. This screen will display. the options have been set. Once the member cases have been 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. the second case is next. Cases can also be added to the list by dragging and dropping one or more root case folders (folder containing the project. The first case shown in the grid will be processed first. or aborted due to some sort of error condition. The Remove button (or Case > Remove) can be used to remove the selected LAW case from the Member Cases grid. Process Summary The Summary screen will appear once the deduplication process has been completed. such as the case not being ED-enabled.ini file for the case (contained in the root LAW case folder) and then click Open.ini) or the project. The summary will also list total counts for documents loaded. click the Add button or choose Case > Add.LAW PreDiscovery User Guide To begin adding cases. the summary will show the Digest and Scope options that were selected and the total number of member cases included in the process. Since the cases are validated at the time they are added to the grid. The Clear button (or Case > Clear) will remove all cases from the grid. duplicate records. and the member cases have been added. These buttons can only be used in New or Rebuild/Flush mode.ini file itself into the Member Cases grid. The Errors value is a count of all errors that occurred during processing. Browse to the project. Deduplication Process Once the external database has been specified. The Progress area provides both visual (progress bar) and textual indicators of how much work is remaining and what has been done thus far. an error will occur at this time if the case does not meet the requirements for inter-case deduplication. 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. via the Operation field. and so on. For a successful process. The total error count will be displayed in a summary screen once processing has been completed. the Up and Dn keys (or Case > Move Up | Move Down) may be used to specify the order in which records are deduplicated. 280 . canceled. the series of steps (five total) that take place during the deduplication process. not including any attachment records. Once added. that were loaded in the current deduplication session. The "Documents Loaded In This Session" value is the total number documents.

and then click Save. a View Errors button will be included at the bottom of the Summary screen. Field information for all LAW fields can also be found in the Field Descriptions topic. 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. See the "Deduplication Mode" section for details. Similar behavior will occur if the process is cancelled by the user. Note: Errors that halt processing or cancelling the deduplication process will both result in the database entering Rebuild/Flush mode. The log file that appears is stored in <drive>\Documents and Settings\<user>\Application Data\Law50\LawInterCaseDedup\LawInterCaseDedup. Please see the Deduplication Information topic for a list of these fields. The Elapsed field displays the amount of time that has passed during the process. Browse to the desired location. The Summary screen will appear with a message stating the process was cancelled. the Summary screen will appear with a message stating the process was aborted. The contents of the summary can be saved to a text file by clicking File > Save As from the Summary screen. Click this button to view the error details. Deduplication Mode The Mode indicator shown below the External Deduplication Database path will display one of four possible mode values: 281 .ErrorLog.txt. enter a file name. their descriptions. If an error occurs during processing that aborts the deduplication process completely. and possible values.Deduplication If errors occurred during processing.

This mode indicates that the external database was previously in Resume/Append mode. See the "External Deduplication Database" section above for information on creating and opening existing databases. Please see the Duplicate Viewer topic for details. 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. The Refresh button can be used to inspect member cases for changes that may the mode. Cancelling the inter-case deduplication process Deleting a document from a member case Renaming. 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. this mode is the same as the New mode. 3. A "Click here for 'Rebuild/Flush' details" link will become available beside the mode value. If changes are detected. b. When the external database is in this mode.This mode will be set when no external deduplication database is selected. When the process is run again on this existing database. d. the mode will be updated to the correct state. or Inter-Case Deduplication). removing. Clicking this link will launch a message box that lists the reasons why the deduplication database was placed in Rebuild/Flush mode.LAW PreDiscovery User Guide 1.This mode will be set when the selected external deduplication database has already been through the deduplication process. 4. but a change was made to one of the member cases that requires that the external database be rebuilt. New . c. Functionally. as the cases will need to be re-deduplicated once this mode has been assigned. 282 . 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.This mode will be set when the selected external deduplication database has not yet been involved in the inter-case deduplication process. Deduplication Utility. Rebuild/Flush . 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. No Database Selected . Resume/Append . or adding a custodian in a member case when the Custodian Level scope was used Deduplicating a member case using ED Loader's Deduplication or the internal Deduplication Utility 2. The following actions are possible reasons for this mode or occur: a.

Deduplication Utility. To launch this viewer from the main interface in LAW. the viewer will look similar to the below image. If the DocID field is not populated. This viewer presents a tree view of these duplicate documents and makes it possible to click on a record. The DocID in the viewer matches the LAW DocID field value for the selected record.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. whether or not that document is a duplicate. click Tools > Duplicate Viewer. LAW's "ID" field will be used instead. Navigating documents via the main document list or one of the grid displays will also update the viewer. Figure 1 If a document is selected that is not a "parent" duplicate (DupStatus=P) or not a duplicate record (DupStatus=G or C). If a document is not selected when the viewer is launched. or Inter-Case Deduplication). Please note. and if a document is selected. 283 . The Duplicate Viewer will always display on top of the main LAW form. immediately see whether or not the record is a duplicate or has duplicates. ensuring the duplicate information matches the current record. and quickly navigate to any duplicates that exist in the current case or other LAW case. The appearance of the dialog upon launching will depend on whether or not a document is selected. attachment records are not listed in the Duplicate Viewer. the viewer will look similar to the below image.

The parent document has one duplicate which exists in the same case. In this example. Figure 3 If a record has multiple duplicates. the parent record is DocID ID00001 and has a _DupID (and ID) value of 4. the duplicate records will be represented in the same manner .as entries below the parent node (see Figure 4). The duplicate record's DocID is ID00004 and has a DupStatus of G. the viewer will look similar to Figure 3. 284 . Clicking the DocID of the duplicate in the viewer will force LAW to automatically navigate to the duplicate record within the case.LAW PreDiscovery User Guide 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. which indicates it is a global duplicate (of ID00001). If a parent duplicate is selected in a case. Parent documents are shown as the parent node in the tree view within the Duplicate Viewer.

Deduplication Figure 4 Records Deduplicated Externally The examples in this section involve records that were deduplicated externally via the Inter-Case Deduplication Utility. 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. or deleted. renamed. the Duplicate Viewer relies on the external deduplication database to retrieve deduplication information. Clicking the DocID of the duplicate in the viewer will force LAW to automatically navigate to the duplicate record within the case. If the database is moved. CaseA01. 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. _DupId=6) and the duplicate record (ID00018) is located in the same LAW case. a parent record is selected (ID00008. Warning: When cases are deduplicated using the Inter-Case Deduplication Utility. 285 . the Duplicate Viewer will display an error (see image below).

a parent duplicate is selected and the duplicate document is located in a different LAW case. The parent. DocID ID00002. 286 . The duplicate record is located in case CaseA02 and has a DocID of ID00020. has two duplicate records: ID00032 in CaseA02 and ID00019 in CaseA01. To navigate to the actual duplicate record in the other case. Clicking the case node (CaseA02 in Figure 6) will force LAW to switch to that case. and also a duplicate in a separate case. The parent record. click the DocID of the duplicate in the viewer.LAW PreDiscovery User Guide Figure 5 In the next example (Figure 6). exists in case CaseA01 and has a _DupID of 2. Figure 6 Figure 7 shows a parent with a duplicate in the same case. ID00016.

Figure 8 shows the resulting viewer after a parent's duplicate document is deleted. the viewer will display a status similar to what is shown in Figure 9. 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. 287 . a warning will appear in the Duplicate Viewer in place of the typical entry. 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.Deduplication Figure 7 Deleted Records If a record is a parent or duplicate record. and it is deleted from the LAW case.

LAW PreDiscovery User Guide Figure 9 288 .

Because the supported export formats are quite different from each other. 289 . LAW supports all of the popular litigation support packages and several others. and full text. Many of the supported formats are strictly viewers and do not support index or OCR information.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. LAW provides users with target application-specific settings to better suit the selected format(s). images. standalone. metadata/index field data. select Tools > Export Utility from the main form or standalone grid. button on the The LAW Export Utility also includes the ability to set up export profiles to save export settings as explained in the Export Profiles section. To launch the Export Utility. or click the main form. or embedded grid toolbar. Consult the documentation for the intended target applications before doing any coding or OCR to avoid wasting time performing unnecessary steps in LAW.

With the exception of Doculex (which use a FoxPro database) and the Concordance DCB export. one with index data and one with image information. all of the load files created are text files that conform to the specifications defined by the target application. If images created via TIFF Conversion in LAW were stored in multipage format and a single-page export format was chosen. Some applications use one multipage 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. In the case of Concordance and JFS. the images would need to be split upon exporting.LAW PreDiscovery User Guide Image Format The image format required is a result of the target application and its image viewer. Therefore. Load File Extensions The load file extensions indicate the extensions of the load files that are created for each of the supported formats. conversion to single-page tiffs is recommended whenever possible. the export actually produces two export files. which can significantly slow the process. The load files can be found in the export path after the export is complete. The load files are named (with the appropriate 290 .

etc.oll Single / Multi Page PreDefined No Yes CaseLogistix CaseMap Single / Multi Page Single / Multi Page Yes Yes No Yes No.opt ImportText.dii".5 dtSearch EDRM XML 1.x Doculex Viewer 5/6 DocuMatrix 1.xml [VolName].ndx [VolName].dbf Doculex5.dcb [VolName].dat [VolName].xml [VolName].key [VolName].csv Doculex3.xml [VolName].csv [VolName]. Format Output Files Single / Multi Page Meta Data Support 16-Bit Naming Required (8. and support for (single.0 iCONECT inData's TrialDirector Single / Multi Page Single Single Single / Multi Page Multi Single / Multi Page Single / Multi Page Single / Multi Page Yes No No Yes Yes Yes Yes Yes No Yes No No No No No No Yes No No Yes Yes Yes Yes No 291 .tex ImportText.cpt [VolName]. unless using older version than 2. for an export path of "D:\Exports\Case1\Vol001"). as LAW assumes this is the volume label for the export.3 Characters) Full Text Support BlueTrace [VolName]. "Vol001.cpt [VolName]. image file formats (single or multi-page images).dat".cpt [VolName].xml N/A [VolName]. "Vol001.dat [VolName].opt ImportText.g..0 of Opticon Yes Yes Concordance Single / Multi Page Yes Yes Concordance Direct (DCB) Single / Multi Page Yes No Yes Delimited Text Doculex Viewer 4.Exporting extensions) according to the last folder in the export path (e. load file extensions.opt [VolName].dbf [VolName]. Supported Formats Below is a quick reference to all supported export formats.or multipage) OCR.ini [VolName]. formats that support importing of index information. native file support.

idx [VolName].LAW PreDiscovery User Guide Inmagic's DB/TextWorks Introspect eCM IPRO IntelliVIEW [VolName].lst [VolName].jfs [VolName].mdb (Access Single / Multi Page DB) [VolName].opt Single / Multi Page No No No 292 .txt (Metadata if exported Single / Multi Page field count is 6 or more) Yes No Yes (externa TotalVzn [VolName].log jfs.ID Straight PDFs Searchable PDFs Single / Multi Page Multi Single / Multi Page Yes Yes Yes No No No Yes (embedd Yes Yes (embedd JFS Litigator's Notebook Single Yes Yes Yes LaserFiche OmniDox (Custom) PDF Conversion PDF Hidden Text Single Single Single / Multi Page Multi Yes Yes No Yes (embedded) No No No No No Yes No Yes (embedd Ringtail CaseBook Ringtail.oll ImageBase.dii [VolName].add [VolName].col [VolName].lfp [VolName].add + Supporter Tables Single Yes No Yes (embedd Sanction Yes No Yes \ No (ex Storm Viewer Single / Multi Page Yes No Yes (externa Summation Blaze [VolName].

modified. If the profile does not meet the requirements. that same profile will be automatically selected when the Export Utility is launched in that LAW case. it may be edited within the Export Utility by simply opening the profile. The profile can be created and saved to a file at any time when working in the Export Utility. and opened from the Export Utility and are saved as a *. The Save As dialog will appear. the settings needed for a particular export.Exporting Export Profiles Export profiles are used to save settings used in a particular export such as index field selection and format-specific settings. A prompt will appear prior to the export process initializing. saved. Note: When a profile is used and an export is executed.pfl file and click Open. asking if the user wishes to save the current settings. All settings saved to this profile will be applied to the current export session. the user can enter a file name for the profile and a location in which to save the file. To open and apply an existing profile. first launch the Export Utility by clicking Tools > Export Utility from the main menu or standalone grid. Opening Saved Profiles Saved profiles can be applied to additional exports for any LAW case provided they match. click File > Open from within the Export Utility. If a profile is already applied as in the above example. The Open dialog will appear. allowing users to re-open the profile and apply or review those settings at a later time. Simply click the desired profile to apply it. the profile name will appear in the title bar of the Export Utility dialog as shown. LAW50 folder) or may choose to keep the profiles with the associated LAW case.. the location and name of the profile is determined by the user. or click the button from the main or embedded grid toolbar. The profile can also be created after clicking Finish from the Options tab of the Export Utility. No profile is loaded by default when the Export Utility is launched in a new case.e. At any rate. Profiles will be created. clicking Yes will force the settings to be saved to the currently active profile. Choose a location and enter a name for the profile. Browse to the desired *. changing the desired settings. or closely match.pfl file in a user-specified location. Once created. The Export Utility dialog will appear. Click Save to save and apply the profile. and then saving the changes. 293 . otherwise.. The last four profiles opened in a case will be listed in the File menu within the Export Utility. Click File from the menu bar and choose Save As. If Yes is chosen. the user will be prompted to save the settings after clicking Finish to initialize the export. Profiles may also be opened and applied using the "recent profiles" menu.. Creating Profiles To create a profile. Users may choose to create an 'ExportProfiles' folder in a directory (i.

LAW PreDiscovery User Guide Formats/Documents Tab The Formats/Documents tab will be used to specify the export type. the type of files (e. the target application and its configuration settings (if any). File Types Because LAW is both a scanning and an electronic discovery application.g.. native files). The Selected Types drop-down contains three options: 294 . and image format. the files to be included for exporting. the Export Utility allows users to choose which type of data should be included in the export.

Ringtail. Electronic Discovery . This text may have been extracted during the pre-save or created during the OCR process. Currently. and the user wishes to include both types in the export. EDRM XML 1. LAW will export the OCR text for any documents that have associated OCR. iCONECT. and Printed Text. If OCR is chosen as Option 1. and images created during the Tiff Conversion batch process or single document tiffing. and Summation. Concordance Direct (DCB).Exporting All Records .Includes text files for any documents that contain text. Options . Introspect eCM. If no OCR text is found. Four options are available: Include Images .0.Includes scanned images. Include Full Text .The Text Options dialog allows users to choose the type of text to take precedence when exporting.Use this option when exporting only scanned images or images imported using a feature other than the ED Loader (such as Import Raw Images). Delimited Text. LAW will move to Option 2 295 . images imported via Import Raw Images or Import Load File. This option may also be used if the case is all e-discovery or all scanned data. Note: Keep in mind. CaseLogistix. Scanned Data .This option may be used when a LAW case contains both scanned (or imported) images and native files. not all target applications support native file review. The type of text included in the export will depend on the option selected in the Text Options dialog (see below). The next section is used to choose which document "states" to include in the export. Extracted Text. Concordance. The options are: OCR Text. native file exports apply only to Blue Trace.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).

When enabled. Export as single page text .Includes the native files imported during the e-discovery import process. then the record in LAW would not have a native file. Again. only Blue Trace. Omit text for tagged documents . printed. LAW will include any UNICODE characters in the exported text if present. non-ED data will not be included in the export. Note: This option will be disabled if the Scanned Data export type is selected. This feature may be used to avoid potential problems caused by extremely large text files associated with LAW records. If Include Native is the only option selected.When enabled. For example. Include records without files . Include Native . CaseLogistix. and the action was set to log a record but exclude the native file. 296 . Note: Only two formats. and Summation will be displayed in the Formats section.When enabled. if this option is selected. or extracted text from the export for certain records. Ringtail.LAW PreDiscovery User Guide and export either the Extracted Text or no text at all if set to 'None'. LAW will only export records imported as e-discovery. this run command has not been fully tested and cannot be supported in the event of a problem.Includes all documents in the case.Single-page text files for each document will be exported if this option is enabled. Documents The Documents section will allow users to choose which documents to include in the export. The tag field will appear in the drop-down list below this option. LAW will convert the default UTF-8 extracted text files to ANSI upon exporting. iCONECT. This feature should be used with caution as many export formats do not support UNICODE. This provides an easier method of locating large text files and tagging them for use with the "Omit text for tagged documents" feature. A tag field must be created and records tagged prior to launching the Export Utility. this record would not be included in the export output and a warning would be logged. Allow UNICODE in text . Summation and Sanction. depending on the selected Export Type. and Electronic Discovery is chosen in the File Types section. If this export setting is disabled. 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 option can be used to omit the OCR. Concordance Direct (DCB). Decode UTF-8 to ANSI . For example. if a duplicate file was detected during an ED Loader import. All Documents . 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. Please note. 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. not all export formats support native file review. Concordance. support single-page text.

As mentioned. Formats This section is used to specify the target application(s) as well as the load file/image format. If the Configure button becomes enabled.0 iCONECT inData's TrialDirector Introspect eCM IPRO IntelliVIEW 297 . Also. Select Documents . Once the format has been moved. Note: Many applications may be chosen but not all support the same options or image formats. Check the boxes next to the starting and ending documents. single-click the application title in the Selected Formats list. Choose a format by clicking the appropriate radio button. certain formats will have additional configuration settings specific to that application. single-click the desired application title in the Available Formats list.5 EDRM XML 1. The formats below support additional configuration settings: CaseLogistix CaseMap Concordance Concordance Direct (DCB) Delimited Text DocuMatrix 1. To determine if a format has additional configuration options. Note: The image format MUST be selected BEFORE moving the application format to the Selected Formats list. two image format options exist: Single-Page and Multi-Page. To move the format to the Selected Formats list. Enabling this option could cause a delay when returning to the main Export Utility screen in large cases. To select a range of documents. To avoid the potential delay. this indicates additional settings exist and can be viewed by clicking Configure.Allows users to choose certain folders and/or ranges of documents within folders for processing.Includes all records currently displayed in the grid. Click Select to launch the Select Folders dialog and check the boxes next to any folders that need to be included for export. a delay may be experienced when launching the Batch Process or Export Utility dialogs while LAW calculates the total number of pages to display. The Calculate total documents option may be selected to include document counts (and possibly page counts . Directly below this list. The number of pages will no longer appear beside the number of documents.Exporting Search Results .see next section) in addition to the number of folders selected. 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. Document and Page Counts In cases with a large number of documents and/or pages. click the folder containing the desired records and click the Set Range button. certain applications will have special configuration settings available in the Export Utility. To select a format. 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. 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. simply double-click the application title or ensure the format is highlighted and click the Select button.

LAW PreDiscovery User Guide JFS Litigator's Notebook PDF Conversion Ringtail CaseBook Sanction Storm Viewer 298 .

and the export path is a mapped network drive. If the UNC Path option is selected. 299 .tif. move the format from the Available Formats list to the Selected Formats list (Export Utility > Formats/Documents tab).. Path Notation The path notation allows users to specify how image paths are written to the load files during the export process.. Other When enabled. The CaseMap Settings dialog will appear.Exporting Format-Specific Settings CaseMap To view CaseMap configuration settings. choose <other> and key the delimiter into the "Other" text box. such as C:\Exports\TestCase\Vol001\image. The Relative Path setting uses a relative path to the images from the export path instead of the entire path (minus the drive letter). With Hard Path selected. 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. To specify a delimiter not in the Field drop-down list.). the image paths are written using an UNC notation (\\computername\sharename\. highlight the application title and click Configure. Data Delimiters Choose the desired delimiters to surround each field and/or field value in the load file. the load file will display a full path to each output file.

LAW PreDiscovery User Guide CaseLogistix To view CaseLogistix configuration settings. The CaseLogistix Settings dialog will appear.). Note: In LAW 5. With Hard Path selected. Path Notation The path notation allows users to specify how image paths are written to the load files during the export process. such as C:\Exports\TestCase\Vol001\image. the image paths are written using an UNC notation ( \\computername\sharename\ . any Unicode data included in exported fields is automatically included in CaseLogistix load files.2 and higher. 300 .. Other When enabled. If the UNC Path option is selected. 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.tif. the load file will display a full path to each output file. The Field Name text box is used to specify the name of the field to which the text will be exported.. highlight the application title and click Configure. move the format from the Available Formats list to the Selected Formats list (Export Utility > Formats/Documents tab). and the export path is a mapped network drive. The Relative Path setting uses a relative path to the images from the export path instead of the entire path (minus the drive letter).

This is useful when viewing the data manually or importing into other applications. If the UNC Path option is selected and the export path is a mapped network drive.dat file. the load file will display a full path to each output file.dat file which will contain the text... the image paths are written using an UNC notation (\\computername\sharename\.). 301 . The Relative Path setting uses a relative path to the images from the export path instead of the entire path (minus the drive letter).dat file. highlight the application title and click Configure.These options allow users to specify which data delimiters to use in the Concordance . such as C:\Exports\TestCase\Vol001\image.dat file into Concordance. The Field Name is the name of the field in the . If the selected field contains more than ~8MB of text.The text for the selected documents will be included in the .tif. Include field names as first record . LAW will automatically create sequential fields to adhere to Concordance's field size limitations. With Hard Path selected. The data delimiters used when exporting will also need to be used when importing the . Path Notation . This setting also overwrites the Include Full Text setting on the Formats/Documents tab of the Export Utility.Exporting Concordance To view Concordance configuration settings.dat file if this option is enabled. The default values Concordance uses by default can be applied by clicking the Restore Defaults button.Inserts the field names for each field as the first record in the . Include document/OCR text as a field in load file . Settings Data Delimiters .The path notation allows users to specify how image paths are written to the load files during the export process. move the format from the Available Formats list to the Selected Formats list (Export Utility > Formats/Documents tab). The Concordance Settings dialog will appear.

This feature greatly improves the speed of the export because no files are being copied and LAW must only generate the load files. Note: The "Allow Unicode data" setting only applies to Concordance database versions 10 and above. please ensure the version of Concordance being used will support the Unicode data.Allows Unicode field data to be included in the load file if any exists in the records selected for export.OPT) and not the .Leaves any images and native files included in the export in their location (LAW case directory).With this option selected. LAW will only create an Opticon load file (. 302 . Allow Unicode data (UCS-2 format) .DAT file. Create Opticon load file only . Prior to exporting.LAW PreDiscovery User Guide Link to images and native files in their current location . Paths in the load file will reflect the current location of the files.

Security . highlight the application title and click Configure. Settings Use specific database (*.dcb) override path .Allows users to append to the desired database.Exporting Concordance Direct (DCB) To view Concordance Direct (DCB) configuration settings. 303 . The Concordance Direct Settings dialog will appear. move the format from the Available Formats list to the Selected Formats list (Export Utility > Formats/Documents tab).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.

Note: These field settings only apply to Concordance 8 databases (or higher). the selected key and indexed fields are listed in File > Modify. the Security button will be grayed out.Click this button to open the Concordance Field Settings dialog box. When the Concordance database is opened.. Database path . if one is located.The path notation is used to specify how image paths are written to the Opticon load file during the export process. such as C:\Exports\TestCase\Vol001\image.Record will be omitted if it already exists. The fields can be selected as "Key" or "Indexed" fields before exporting the database to Concordance. To modify fields for earlier database versions. exported records will be appended to the selected *.All records will be appended to existing database.Any new information will be applied to the existing record. Field Indexing . instead of the entire path (minus the drive letter).This option is used in conjunction with the "Use specific database (*.  If Record Match is Found . edit the "E-Discovery. listing the fields in the current LAW case. Append All Records .dcb file.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.tif..LAW PreDiscovery User Guide If the version of Concordance installed on the current workstation does not support this feature. Click Browse to locate a Concordance database. Update Existing Record . the load file will display a full path to each output file. If the UNC Path option is selected. and the export path is a mapped network drive. With Hard Path selected. the image paths are written using an UNC notation ( \\computername\sharename\ . The three options are: Skip Record . Note: Hard paths will always be used if the "Automatically load Opticon imagebase files" option is enabled. 304 .dcb) override path" option.dcb" database template located in the Template folder in the LAW installation directory.). Path Notation . The Relative Path setting uses a relative path to the images from the export path.

When enabled. The partition size is set in the Options tab of the Export Utility. field size. eliminating the need for the user to do so once the Concordance database is created. these records will not be added to the DCB and errors will be logged. All of the database partitions are treated as one database. a partition size of 650 MB creates partitions of the concatenated database that can be copied to CDs. and the offending data size. Automatically load Opticon imagebase files . When disabled. Link to images and native files in their current location . The warning and error messages will include the field name. Enter the desired Field name below this option in the text box provided. For example. Paths in the load file will reflect the current location of the files. Include document/OCR text as a field in database file .If this setting is enabled.Exporting Concatenate DCB's across separate partitions . 305 .Leaves any images and/or native files included in the export in their current location (LAW case directory). this feature includes exported text to a field in the database. LAW will automatically load any exported images into Opticon. Truncate text values that exceed their field size . This feature greatly improves the speed of the export because no files are being copied and LAW must only generate the load files. records with text values that exceed their field size in the target DCB will still be added to the database.Select this option to concatenate the databases into one database and then export it into partitions.When enabled. The offending text values will be truncated and a warning will be logged.

the image paths are written using an UNC notation ( \\computername\sharename\ . The Relative Path setting uses a relative path to the images from the export path instead of the entire path (minus the drive letter). The Delimited Text export generates a *.csv). such as C:\Exports\TestCase\Vol001\image.. 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. Data Delimiters Choose the desired delimiters to surround each field and/or field value in the delimited text file.csv file named for the last folder in the export path (i. Note: Excel will not parse a Unicode file correctly by default unless a tab [009] is used for the field delimiter. Vol001. Path Notation The path notation allows users to specify how image paths are written to the load files during the export process. move the format from the Available Formats list to the Selected Formats list (Export Utility > Formats/Documents tab).. the load file will display a full path to each output file.e.LAW PreDiscovery User Guide Delimited Text To view Delimited Text configuration settings..). With Hard Path selected.tif. 306 . If the UNC Path option is selected and the export path is a mapped network drive. highlight the application title and click Configure. The Delimited Text Settings dialog will appear.

Renumber documents sequentially . The DocuMatrix Settings dialog will appear. OCR text will be included in the load file. LAW will renumber the documents in the . Without this setting enabled.) Create XML for fixing existing documents .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. 307 . Case Name and Database Name .Exporting DocuMatrix 1. Include page offset data with OCR . Note: DocuMatrix requires attachment (child) documents to have a parent in the load file. starting with the specified value in the Starting # field.xml load file. These values may be entered if requested.Use this setting to create an XML file specifically used for updating existing records in an existing DocuMatrix case. this may cause problems when loading the file into DocuMatrix. ("Include Full Text" must also be checked on the Formats/Documents tab of the Export Utility. If an attachment is included to be exported but the parent is not (using the manual document range selection).5 To view DocuMatrix configuration settings. Include attachments by parent .Forces LAW to include attachments with any selected parent.When enabled.These are both optional settings and are not required to create the export from LAW. but the location of each word will not be included. 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.

Batch Name The Batch Name setting is used to associate a specific name with the exported set of files and metadata. Path Notation The path notation allows users to specify how image paths are written to the load files during the export process.. Specifically. When enabled.tif. 308 .. The EDRM Settings dialog will appear. the image paths are written using a UNC notation ( \\computername\sharename\ . The Relative Path setting uses a relative path to the images from the export path instead of the entire path (minus the drive letter).LAW PreDiscovery User Guide EDRM XML 1. the load file will display a full path to each output file. The value entered in the text box will be stored in the XML load file in the Batch Name tag. the Include document/OCR text as content in load file setting includes the text for each document (if available) within the EDRM XML file. highlight the application title and click Configure. such as C:\Exports\TestCase\Vol001\image. the text will appear between the starting and ending InlineContent tags.0 To view EDRM XML 1. If the UNC Path option is selected and the export path is a mapped network drive.0 configuration settings. move the format from the Available Formats list to the Selected Formats list (Export Utility > Formats/Documents tab). With Hard Path selected.).

If the UNC Path option is selected and the export path is a mapped network drive. Choose the desired format from the drop-down list. move the format from the Available Formats list to the Selected Formats list (Export Utility > Formats/Documents tab)..tif. 309 . 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. the load file will display a full path to each output file.. With Hard Path selected. Path Notation The path notation allows users to specify how image paths are written to the load files during the export process. The iCONECT Settings dialog will appear. The Relative Path setting uses a relative path to the images from the export path instead of the entire path (minus the drive letter). The Field Name text box is used to specify the name of the field to which the text will be exported. such as C:\Exports\TestCase\Vol001\image. highlight the application title and click Configure.Exporting iCONECT To view iCONECT configuration settings. 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. When enabled.).

Each of these three values is usually provided if this format has been requested. Index ID.txt" for each multi-page document and contains a list of PageIDs contained in the multi-page document. the files are not copied. Link to images and files in current location . Include all Bates numbers .Click this button to display the field configuration dialog shown below: 310 . 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. <Field IDs. Use IDX Version 5 format . move the format from the Available Formats list to the Selected Formats list (Export Utility > Formats/Documents tab). the export process will generate the load file(s) and link them to the images and/or native files in their current location. enter values for the Batch Name.Creates a text file called "<image>_uid.. A shortcut to the load file will be created in the export path referencing the load file in the image directory of the case. The Introspect Settings dialog will appear.LAW PreDiscovery User Guide Introspect eCM To view Introspect eCM configuration settings.Forces LAW to configure the load file to match the specifications for Introspect 5. Also. the volume name of the exported load file will be used by default. If the Batch Name is left blank. highlight the application title and click Configure.When enabled. The Index ID and Folder ID values will appear as repeating values in the load file. and Folder ID text boxes. General In the General section.> . images MUST be in multi-page format in the LAW case in order for Introspect to view all pages of the images. Note: When using this setting.

311 . The fields shown in this list are all of the index fields which exist in the current LAW case.idx load file.Exporting The Introspect Field Information dialog may be used to define specific Field ID values for any of the fields. These fields will exist in the Header section of the .

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. Click the Edit button to display the IPRO Field Information dialog.LAW PreDiscovery User Guide IPRO IntelliVIEW To view IPRO configuration settings. Include index fields in load file . The IPRO Settings dialog will appear. 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.Use this setting to include index information in the . an index value (1-10) must be assigned to the selected field and will match the 312 .lfp file.

Note: This annotation is applied directly on top of the existing image. or Right. click OK to save the changes and return to the IPRO Settings dialog. it could potentially cover existing image data. otherwise.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. Use new folder flags (DocBreak = F) . The Vertical Position setting is for placing the annotation relative to the height of the document. select the option to Write to separate LFP file. To separate the OCR text from the image information. The IPRO annotation does not modify the image itself.OCR produced using the ExperVision or ABBYY OCR engine may be included in the IPRO load file using the full text (FT) tag. The default value for this feature uses the document (D) flag. Once the desired selections have been made. a volume path notation will be used. The Alignment setting is used to determine the horizontal location of the annotation: Left. which allows full text searching in IPRO. a full path (with drive letter) will be used and no volume will be specified.Exporting corresponding field in IPRO. Use volume path notation . No two selected IO fields may have the same index value. 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." This allows IPRO users to view/hide the PageID annotation just as if the annotation were created in IPRO itself.lfp. Include OCR Word Information . This option will generate two IPRO files displayed as [Volume]. 313 .lfp and [Volume](ocr). therefore.lfp file as the document break at the beginning of each new folder.If this option is checked. Centered. Number pages (w/IPRO annotations) . Selection of index fields in this window is independent of the fields selected under the Fields tab in the Export Utility.Use this setting to include an (F) flag in the IPRO .

LAW PreDiscovery User Guide JFS Litigator's Notebook To view JFS configuration settings. 314 . move the format from the Available Formats list to the Selected Formats list (Export Utility > Formats/Documents tab). The JFS Litigator's Notebook Settings dialog will appear. 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. choose a field in the Available Fields list and then choose a field in the JFS Fields list. The JFS settings allow users to map LAW fields to default JFS fields. To link a field. highlight the application title and click Configure.

The PDF Settings dialog will appear. found in the Export Utility under the Options tab. Populate PDF metadata . If a document is not a parent or contains no attachments. This feature must be used in conjunction with the "Combine Parents/Attachments" setting located in the Options tab of the Export Utility. move the format from the Available Formats list to the Selected Formats list (Export Utility > Formats/Documents tab). Bookmark Caption .This setting may be used to populate the metadata of a PDF file with index field values stored in the LAW case. to create bookmarks in exported PDF files.Use this setting in conjunction with the Combine Parents/Attachments option. no bookmarks will be created in the PDF file for that document. 315 .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. Create bookmarks for grouped documents . highlight the application title and click Configure.Exporting PDF Conversion To view PDF Conversion configuration settings.

The Ringtail Settings dialog will appear. highlight the application title and click Configure. Include document/OCR text as a field in load file .When enabled. This feature is useful if the OCR in LAW already contains these markers but document boundaries have since changed. Allow long folder names (over 20 chars) . This option is available due to special LAW user requests. Ringtail will locate the native files and allow viewing of them in the Content frame. If images and native files are included for export. The Replace existing page markers option will remove any existing page markers currently on the OCR and replace them with the new value.LAW PreDiscovery User Guide Ringtail Casebook To view Ringtail configuration settings. Caution: This setting is not recommended as Ringtail does not officially support long folder names. provided the native files are named the same as the associated image and are located in the same folder.This option allows LAW to ignore Ringtail's recommended folder name length limit of 20 characters. This tag is used by Ringtail for linking the OCR text to the actual images. Ringtail does not directly support this method and it should be used with caution. Records referenced in the pages table will be available for viewing in the Image frame in Ringtail. and native files are included for export. This was the default method for handling Ringtail OCR with LAW versions 4. move the format from the Available Formats list to the Selected Formats list (Export Utility > Formats/Documents tab). Instead of re-OCRing the documents. LAW will write a record for each native file to the Pages table in the Ringtail load file (export.41 and below.02.This option inserts a special page marker onto the OCR text of each page in the following format: "###{Page}|||Page {PageID}^^^". this feature replaces the old tag with the new.mdb). and the native records are not referenced in the Pages table.Use this option to place the document text into a memo field inside the Ringtail load file. 316 . Insert special page markers in OCR text . Include reference to native file in Pages table .

If LAW's folder name length exceeds the 20 character maximum length. Ringtail requires a filename format named the same as the image tag with a .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. Folder character length not to exceed 20 characters . 317 .Spaces in folder names will automatically be converted to underscores ("_") during the export process. BegDoc#. and PgCount . EndDoc#. LAW will automatically truncate the folder path to 20 characters (unless the "Allow long folder names" option is selected).Exporting Ringtail Format Notes The requirements for the Ringtail format should be followed closely to avoid possible problems importing this load file into Ringtail. Supports Single-Page or Multi-Page Tiffs (single-page most common) . Folder names may not contain spaces .The filenames for the exported text files are unlike other formats.txt extension.Ringtail supports either singlepage or multi-page tiffs. the most commonly used image format is single-page tiff. Exported text filenames . however.

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. 318 . so no more than 5 users may have a single database open at one time. a free CD-runtime viewer. speed. For users who wish to scale Storm for use as a document retrieval tool. The viewer runs as a front-end to the Storm imagebase. Storm Versions 1. and have more clients. The Storm imagebase can be built and distributed freely by users of LAW and Storm-X. and more connections to existing imagebases.LAW PreDiscovery User Guide Storm Viewer Storm Viewer is a freely distributable viewer available to the public. Note: Storm Viewer exports will also work for the Stormi software. The local server has a 5-user concurrent connection limit. the Advantage Database Server is a lightweight and powerful RDBMS solution that will add stability.

Exporting Summation To view Summation configuration settings. the 319 . Include PST tokens directly in dii file . The default export method is to write the index fields to a . highlight the application title and click Configure. 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.Enables features not compatible with versions 5.Allows the text for the exported documents to be included in the dii load file. although all the data does appear to get imported. Write all fields to dii file .Allows the writing of seven or more index fields to be written to the dii file. it will overwrite the 'Include Full Text' option on the Fields tab of the Export Utility for the Summation format. Include document/OCR text directly in dii file . The Summation Settings dialog will appear.txt file if the number of index fields is greater than seven. move the format from the Available Formats list to the Selected Formats list (Export Utility > Formats/Documents tab). Form feed characters to delimit text pages are not supported and errors about unsupported operations may occur. Settings Allow advanced (iBlaze) dii features . Warning: This feature appears to have bugs in Summation.Forces LAW to include an extra 'tag' in the edii file. If this setting is enabled.21 and below of Summation.

LAW will populate the @MEDIA token for these attachments as "Attachment" per the Summation documentation. Data Delimiters . add the entire setting as shown. MSG attached to an MSG).Places the index field names in the first line of the delimited text file.e. All available tokens are selected by default. By default. eDii Tokens . add the key below it. This setting is disabled in LAW cases that are have not been enabled for electronic discovery. 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. either remove (or comment out) the setting above or replace the eMail value with Attachment.This feature allows users to choose which tokens are placed in the Summation load file.This setting is used to specify the type of volume notation to use in the dii file. However.The data delimiters for the delimited text file may be defined in this section. To switch back to the default of "Attachment".LAW PreDiscovery User Guide @PSTFile token will be omitted from the edii file. Include field names as first record of delimited text file . Note: An INI setting is available to modify the @MEDIA value used for e-mail attachments that are e-mail files (i. Dii Path Notation . Always write index fields to separate file . the value can be changed to "eMail" for e-mails attached to e-mails by adding the following setting in the Law50. Most users of Summation have a preferred way of importing the dii files so it is important to check on the preferred method. otherwise.exe): [Summation] EmailAttachEmailMedia=eMail If the [Summation] section already exists.Forces LAW to place all index field information into a delimited text file regardless of the number of index fields selected for export. 320 . 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 default values for this feature can be reset by clicking the Restore Defaults button. Hard Path creates a tag similar to: "@D C:\Exports\Vol001\001\". This is useful for determining the field order of the data in the load file or for importing into other applications. The two options (@V and @I) are the most commonly used with @I being the recommended (most versatile) method.ini file in the application path (same folder as Law50.

Object ID . EX001.Exporting TrialDirector and Sanction The TrialDirector and Sanction formats utilize the same configuration settings. 321 .Uniquely identifies each document within the collection. Description (Optional) . The TrialDirector Settings or Sanction Settings dialog will appear. Users may choose BegDoc# or any other index field in the LAW case. To view these settings. EX001. EX001. This field may either be Page ID (used when BegDoc# is selected as the Document ID field) or Auto-Generate.. depending on the selected format.002.Optional setting allowing users to populate the Description field in TrialDirector or Sanction with values from a user-defined field in the LAW database. The Auto-Generate feature is most commonly used when a field other than BegDoc# is selected as the Document ID.001 extension (and so on) after the Document ID to each page within the document (i.e. which assigns a .001. highlight the application title. Document ID . then click Configure.003). move the format(s) from the Available Formats list to the Selected Formats list (Export Utility > Formats/Documents tab). such as DocID or Exhibit Number (for example).References each page within the document.

Concordance Direct (DCB).LAW PreDiscovery User Guide 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." option. Concordance. check the "Use format specific fields over default selections" option. In certain situations. and the specifications call for different index fields to be included in each type of load file. Concordance. or document identifier.. In another example. The user would first choose the Storm Viewer fields with <Default> as the Selected Format in the Fields tab. check the "Use format specific. Selected Format The Selected Format drop-down will contain up to five items. and then choose the desired fields for the Summation load file. Next. For example. the user would simply need to choose <Default> in the Selected Format drop-down and then select 322 . 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. and Storm Viewer. a user needs to export to Summation. The final step would be to choose Concordance from the Selected Formats drop-down. but would like to perform both exports at one time.. a user must export to Summation and Storm Viewer and needs to include the same fields for both formats. Summation. and Ringtail. the user would select Summation from the Selected Formats list. users may need to include certain fields in a Summation load file and a different set of fields in a Concordance load file. depending on the formats selected in the Formats/Documents tab: Default (always present in list). for example. which will be used to link the index field data to the associated image or native document. and then choose the desired fields for the Concordance load file. In this scenario.

The field name will no longer appear in red once the name has been properly changed.Allows users to rename the field upon export. field name is too long or contains unsupported characters). allowing users to choose fields to be included in that format's load file. while the Demote button will move the selected field down the list. To remove a field. The field will then be moved to the Selected Fields list. The Selected Fields list is divided into two columns: Field Name . These fields would then be included in both the Storm Viewer database and the Summation load file. Fields may also be selected or deselected by clicking the Select All or Remove All buttons. The field will need to be renamed in the 'Export As' column prior to export. 323 . This is useful for applications that require fields to be named a certain way. highlight the index field in the Available Fields list and then click Select or simply doubleclick the field name. The "Use format specific fields over default selections" option enables the Available and Selected Fields lists when a format other than <Default> is chosen. The Promote and Demote buttons may be used to change the order of the fields in the Selected Fields list and ultimately. such as Summation. Selecting Fields The Available Fields area displays a list of both user-defined and system fields that are available for export.. in the load file.e. or document identifier. field is used to link images or native documents to the matching index field data. To include a field in the export. double-click the desired field from the Selected Fields list or select it first and press the Remove button. but other user-defined fields may be used provided they contain a unique value and do not contain blank values for any record. Export As . just in the load file. Image Tag Field The Image Tag. The BegDoc# and DocID fields are commonly used for this purpose. This does not rename the field in the LAW case itself. 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. The Promote button will move the selected field further up in the list.Exporting the desired fields.Displays the name of the selected index field.

such as file format.This value will be the location to which the exported files will be saved. Partition Size . For example. and various other output settings. native. if the export path listed is C:\Exports\EDD_001\Vol001.This setting is used to determine how much data is written to each volume. Output Path This section contains settings related to the location in which the files will be exported. folder and file naming schemes. text. Export Path . export logging. a Vol002 folder will be created. depending on the selected options. full text. When the partition size has been reached.LAW PreDiscovery User Guide Options Tab The Options tab contains settings for the output path (for images. and load files). then the first volume will be Vol001. native files. The default of 650 MB should be used if planning on burning the exported 324 . and load files. These files may include one or a combination of images. etc. The last folder listed in the output path is considered to be the volume name.

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

native. creates a "002" folder. The Folder Naming scheme (see next option) will be applied following the Root Folder. Root Folder . Mirror Original. use this field to launch the Custom Folder Structure dialog and choose the field or fields containing the folder structure. Mirror Original .Used to override the Default settings for the desired file type.If a root folder value is specified here. the user could select 'Override' beside the Native file type and then choose Incremental in the Folder Naming column. which will apply to all types unless the Override option is used. the file type(s) (images. and other miscellaneous settings. Folder Naming . if a ”r.Places the specified number of files in a "001" folder. etc. One option may be applied to all by selecting the desired option as the <Default>. enter the desired number of files to be placed in each folder or use the default of 250. Files/Folder . native. If Custom was chosen.Text” root folder is specified for the Full Text file type. Note: If a folder or file name length exceeds 250 characters for any records.Three options exist for folder naming: Custom. (see Files/Folder option below). use the Override setting and choose different options for each. if <Default> is set to Mirror Original. text) included in the export as well as a '<Default>' option. Incremental . For example. Output Settings The Output Settings section contains options related to output image files.Uses 1-3 of the specified index fields to create a folder structure when exporting (see Files/Folder option below). Or. then the full text will be placed in C:\Exports\EDD_001\vol001\Text. If Incremental was chosen. 326 . following this folder structure: <Export Path>\<Root Folder>. and the specified export path is C:\Exports\EDD_001\vol001. but the job specifications call for Incremental folders for native files only (and mirrored for images and text). annotations.This option only applies to the Incremental and Custom folder naming schemes. Override .LAW PreDiscovery User Guide File Type . For example. o o o Custom .Mirrors the current structure as shown in the folder tree in LAW’s main interface. the export path for those records will be changed to <Export Path>\$Invalid_Paths.Lists each type of file (images. and/or full text) will be placed in the mirrored or incremental folders. and Incremental.

The PDF setting can be used to convert images to PDF and may be used with single. B&W TIFF images will not be affected by this process. and PNG formats only support single-page image files and should NOT be used with exports that produce multi-page images.Exporting Output Format . 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. PDF. This setting has the same effect as choosing the 'PDF Conversion' export format. The Retain Color setting for annotations currently only exists in the Export Utility. this setting will replace the drive letter (with the designated letter) written to the load files. This setting is typically used to create a set of images to be viewed over the Internet or an intranet where bandwidth is limited. The <Default> setting uses the drive letter of the export path. and the “Use Pegasus Image Library” is disabled. Retain Color . PCX. Also. but necessary with some formats). JPEG. 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. Choosing PDF (Image Only) forces LAW to create an image-only type PDF file. PDF (Image Only). Note: If exporting multi-page color or grayscale tiff images to a single page format with the Output Format set to Default.or multi-page image formats. Image Drive . Output format settings are: Default. The PDF Conversion format provides a means to export images as PDF with no load files. It is ONLY applied when an output format of TIFF or PDF is selected for a multi-page export. TIFF. See Annotations for more information on merging.The Image Drive setting allows users to specify an alternate drive letter for hard image paths written to load files.The Output Scale setting allows users to reduce the size (AND quality) of the images during the export process.The Output Format setting allows users to convert images to an alternate format during the export process. Output Scale is not available for use if the "Use Pegasus Image Library" setting is enabled. 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. PNG. The JPEG. Output Scale . and TIFF (Binary). 327 . The TIFF (Binary) format forces the export of black and white tiff images. Note: This requires changing the color format of the page and may significantly increase the size of the images. so they can be imported without modification from another system. LAW will automatically export these files as JPEG images. If using hard paths for images (not recommended. whereas the PDF output format setting produces PDF images with all specified load files.Merging annotations will "burn" all annotations onto the exported images. PCX. Merge Annotations . if using the PDF setting users should first ensure that the target application supports PDF images.This setting allows color annotations to be preserved when merging annotations.

2:1:1 (horizontal). creating a single document. There are four possible selections for this setting ranked by displayed image quality starting with the highest: 1:1:1. LAW's Value 1:1:1 2:1:1 (horz) 4:1:1 2:1:1 (vert) Summation's Value 4:4:4 4:2:2 4:1:1 4:4:4 Export Status This feature allows users to track whether or not a file has been exported. Some users of Summation iBlaze have reported a noticeable improvement in displayed image quality when using the 1:1:1 subsampling format. 328 . JPEG subsampling . and 4:1:1. 2:1:1 (vertical). Depending on the content of the image.Enabled only when the Pegasus Image Library is selected. records that did not export will receive a value of N. the difference in image quality between the four possible subsampling formats may not be noticeable. the missing pixels can be determined. enable this setting and choose the field from the list. 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.LAW PreDiscovery User Guide Combine parents/attachments . LAW uses the Pixel Image Library. JPEG subsampling is used to adjust the color quality of a JPEG-compressed color image exported out of LAW. A user-defined field must be selected to store the export status from the drop-down. However. These two options differ by the direction in which they average nearby pixels in the image. 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. the existence of this data results in a larger file size. If the "Reset export status" option is enabled. If the highest quality display image is desired. LAW will update the export status for all documents in the case (regardless of the documents selected for export).When enabled. 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. If an index field was created for this purpose. LAW uses the Pegasus Image Library to manipulate images during export. however. the 1:1:1 subsampling option should be used instead. Exported files will receive a value of Y.This feature merges attached documents to their respective parents during the export process. Use Pegasus Image Library . By averaging the known colors of nearby pixels. Subsampling is used to calculate the color values of pixels that have been removed from the image to reduce the size of the file. common "assertion failure" errors may occur when using the Pixel Image Library. When this option is not selected. Note: Summation iBlaze defines these subsampling options differently than LAW.

All of these settings are enabled by default (and always have been in previous versions of LAW). Perform Blank Value Checks These options determine whether LAW performs a check for blank values prior to exporting.When enabled. On image tag(s) . Perform Duplicate Checks These options determine whether LAW performs a check for duplicate values prior to exporting.When enabled.When enabled. 329 . If these checks are not needed. LAW will check the selected image tag field (Fields tab) for duplicate values and notify the user if any are found. 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. a speed increase in export initialization is a potential benefit of disabling the settings in larger cases.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. 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. LAW will check the selected image tag field (Fields tab) for blank values and notify the user if any are found. On image tag(s) . On file naming scheme . 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.

using the default value of 650MB is recommended. All load files created (with the exception of Doculex) are named after the volume label (e. this extra space is used for fitting the last document on the CD. The load files should appear inside the Vol001 folder on the final CD.dat. depending on the size of the case. If creating standard CD’s. Inside this section are options to determine the export path and to set the partition size of the volumes created. It is VERY important this step is followed exactly or the load files may not load properly into the destination application. Repeat this step for each volume. 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". If the volume of the CD is not specified as the last folder name. Vol001. Vol001. along with the images/native/text files for the case. The last folder of the export path is used as the volume label for the export.LAW PreDiscovery User Guide Creating CD Volumes LAW can export a case into volumes during the export process. 330 . but LAW needs some extra room for "buffer" space. this sample case created three volumes: Next.. begin burning the volume folders onto the CD.g. Once the export has been created. etc. those applications will not be able to find the images located on the CD. an export path of "D:\Exports\Cases\John Doe\Vol001" will use "Vol001" as the volume label.oll. Vol001. For example. The resulting volume size could result anywhere from ~630MB to ~670MB depending on the documents in the case. This is critical when performing exports that read image information from a CD with a reference to the CD via the volume name.) and all load files that reference a volume label will use this as the CD volume name. Since LAW must prevent documents from spanning across CD’s. so it needs to be named accordingly. The Options tab in the Export Utility contains an Output Path section. Most CD’s today can hold 700MB.dii. multiple volume folders may have been created. For example.

For electronic discovery reports based on data loaded via ED Loader. 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). select File > Administration > Case Summary from the main form. If opting to do so. and the number of pages completed. The summary reports the number of documents. The case summary is a quick and easy-to-use report for general billing and progress reports.) To generate the case summary. the total number of pages. LAW will prompt the user to enter a date range for narrowing summary information (optional). 331 . the Summary function in the standalone grid display (Tools > Summary) may be used.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. click Tools > ED Reports in the standalone grid. (See Flagging Documents/Pages for OCR section for details. the number of pages flagged for OCR. users can specify a date range and only documents that were created during that date range will be included.

332 .LAW PreDiscovery User Guide 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.

The space used by records is not reclaimed when records are deleted. To compact the current database. Compacting should be done on a weekly basis at a minimum. This unused space is removed during the compact operation. However. Database "bloating" occurs naturally as information is added and removed. consider compacting on a daily basis. reducing the size of the database. so users can see how much spaced was recovered (Access only). 333 . The size of the database before and after the compact operation will be reported. Note: The Compact Database feature is not supported for SQL/SQL Express cases. Compacting removes unused space and rebuilds indexes which can decrease the size of the database significantly and increase performance. if multiple users are performing extensive coding and scanning in a case. causing the size of the database to grow over time.Administration Compacting the Database Compacting databases is an essential part of database maintenance. 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. select File > Administration > Compact Database.

the error logs may be viewed at a later time using the Log Viewer. and Page Count Extraction Logs. Deduplication Logs. This dialog will contain seven tabs: All Logs. Error logs for most processes are stored in <case root>\$Logs in *. The Log Viewer dialog will appear displaying the filename of the error log in the title bar. If the user chooses not to view the errors and selects No. The Open Error Log dialog will appear. Export Logs. The All Logs tab will contain all error logs associated with the current case. select a log from the list and click Open. LAW will generate an error log and prompt the user to view the contents. 334 .csv format. Scan Logs. This viewer may be launched by clicking Tools > Log Viewer from the main form. Reorg Logs. the error log will be displayed in the Log Viewer dialog. If Yes is selected (to view errors).LAW PreDiscovery User Guide Log Viewer Reviewing Errors When certain processes in LAW have completed such as an export or batch process and errors have occurred. Batch Logs. To launch the Log Viewer.

Records shown in the Log Viewer can be tagged for future review.csv file. Click the Synchronize button to synchronize with the document list.Administration Sort columns (ascending or descending) by clicking on a column header. click the Tag All Records button. click the Open Log button and choose a different log from the Open Error Log dialog. click the Save As button. and dropping the column in the desired location. and then click Save. (See the Creating Tag Fields topic to learn how to create tag fields. 335 .) Once the tag field has been created and is selected from the Tag Field list in the Log Viewer. browse to the desired location. etc. To tag only certain records. To tag all the records currently listed in the Log Viewer. determine which records need to be tagged. The Log Viewer may be synchronized with the main form in LAW. Tagged records will appear checked in the grid displays and set to <Yes> in the Index display. enter a file name. To save the contents of the Log Viewer to a new *. first use the Ctrl or Shift keys and left mouse button to select the desired records and then click the Tag Selected Records button. 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. processing. The columns can also be moved within the Log Viewer by dragging. Tag values cannot be toggled using this feature. allowing users to view the documents that received errors when reviewing the error details. To view additional error logs once the Log Viewer has been launched (if any exist).

After selecting the range file. inserting new pages into a document after the OCR process. LAW will begin rebuilding documents based on the specified ranges. The reorganize function should be performed prior to the OCR process to avoid complications. This issue can occur for several reasons including: aborting the OCR process by canceling or an OCR engine crash. select File > Administration > Reorganize Documents. To reorganize documents.LAW PreDiscovery User Guide Reorganize Documents The Reorganize Documents function will automatically reorganize documents based on the ranges specified in the selected range file. If an error occurs stating the image and OCR text are not synchronized. Any non-text OCR not associated with the leading document for a range will be discarded. the reorganize process will be aborted and the OCR will have to be either removed or corrected for the image that caused the problem. or merging of documents with incomplete OCR. 336 . although it will reorganize text-based OCR during the reorganize process.

. Any errors detected are reported in a log file named "scandb. Find blank/missing Page IDs 337 . select the Remove if found option. Options Find invalid records (missing images) This option verifies each record in the database has a corresponding image. Documents This section allows the selection of either All Documents or the Current Folder to be scanned for errors. users will need a way to detect and/or eliminate certain types of problems. This function can be run by selecting File > Administration > Scan For Errors. from the main menu. To remove any such records. These extra records can affect processing and summary functions. The Include subfolders option will allow LAW to also scan the folders below the currently selected folder. Users often delete or move files through Windows causing LAW to contain records that do not point to valid images. The Scan For Errors feature provides a means to automatically search the database for some common problems. LAW will present the option to view this file when the scan is complete. The Ignore Native Documents option prevents native documents (records without images) from being repeatedly scanned and logged as errors.log" and is located in the "Log" folder in the user's temp folder (%temp%\Law50\Log). so users should remove them.Administration Scanning for Errors As cases increase in size. If errors are detected..

once returned to the grid. 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. First of all. it will be updated. 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. it ensures that none of the images have become corrupted (if they are. Verify Page Counts This option validates the page count of every image in the case (with a record). this record is safe to remove. These records are also safe to remove from the database. An orphan page record is a page level record that no longer belongs to an existing document. If the page count in the database is incorrect. Since there can only be one 'page 3'. this option has several benefits. it ensures that the total page count displayed in the Case Summary is accurate for billing purposes. are intentional and correspond to the original documents. This option allows users to find these breaks to ensure that all pages are accounted for and to confirm these breaks. Sometimes. Third. it will be logged). use the Query->Blank Page IDs function in the standalone grid display. Second. 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. This may have occurred after a document was deleted. 338 . by opening every image file. Whether intentional or simply operator errors. If any missing page records are found.LAW PreDiscovery User Guide This option is used to find documents with pages that have blank or empty Page ID entries. Pages in a case are typically numbered sequentially. certain export formats require non-blank Page ID entries for renaming or linking purposes. the records can be easily modified or processed. provided the Correct invalid database page counts option is selected. Because every image has to be opened. It does so by opening every image and comparing the actual page count with the page count stored in the database. Find gaps in Page IDs This option is used to find gaps or breaks in the numbering sequence. However. Since each document should have the same number of page-level records as the document's page count. This option provides a way to find the documents with blank entries so users can take the appropriate measures to correct them. LAW will automatically sequentially number the PageID values of the missing page level records if Auto-number missing pages is selected. if any. this check ensures (for example) that a 5-page document has exactly 5 records in LAW's page table. To modify the pages after they are found. A 'missing' Page ID is defined as being a document record with an incorrect number of page-level records. there may be breaks in the numbering sequence. however. but a failure occurred deleting the page records for the deleted document. this option can be very time consuming when cases become large.

339 . 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#). the documents will be compared against the range file in two passes. document breaks can often be incorrectly determined at scan time. LAW will prompt the user for a range file. If Yes is selected. the error log will be displayed. LAW may report an excessive amount of errors. but users may not know what the actual document breaks should be unless pre-determined by a separate process. Any ranges that are not found will be reported.Administration Validating Document Ranges When scanning documents at the production level. Once specified. they can be validated after the scan process using the Validate Ranges function and optionally reorganized using the Reorganize Documents function. Otherwise. The first pass checks to ensure all pages fall within the specified ranges. Any pages that do not fall within one of the specified ranges will be reported in the error log. Validating Ranges To run this function. This pass is only useful if the documents and ranges are numbered sequentially with few or no gaps. The second pass actually validates all of the specified ranges against the documents in the case. Document breaks can be manually corrected with a combination of the Merge Documents and Split Documents functions. select File > Administration > Validate Ranges .

mdb file. so the output is not suitable for a standalone working case. Note: This function works with either ADS or Access databases and always produces a project. this feature dumps data and images of the current folder to a selected output folder. This feature has been designed for quick partial backups or re-importing purposes. This feature is not currently supported with SQL Server cases.LAW PreDiscovery User Guide Extracting Subsets Located under Folder > Extract as Subset in the main menu. Not all indexes and field properties are retained. 340 .

e-mail. However. Populate RecordType Values <RecordType> is a "virtual" field available only in the Export Utility and is used to classify exported records as e-docs. Dim cnn as New ADODB. For a listing of index fields existing in LAW for both ED and non-ED-enabled cases. An index field to store the values must be created prior to accessing the run command.Recordset cnn. This command is intended for EDenabled LAW cases only. but LexisNexis assumes NO responsibility for any damage done by a user-defined command.. adOpenKeyset rs2. cnn.Open "tblDoc". cnn.Command) property will return the connection strings for both an Access database and an ADS database.Command rs1. it does not need to be named RecordType. The (VBA. please see the Field Descriptions topic.e.Recordset Dim rs2 as New ADODB. Enter the name of the target field and then click Begin. 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 possible values are: LOOSE E-MAIL ATTACHMENT E-MAIL ATTACHMENT E-DOC ATTACHMENT LOOSE E-MAIL E-MAIL 341 . The connection string to the current database will be passed to the executable so that it may open and manipulate the current database. The name of the field does not matter. Javascript) in addition to actual executables. etc. adOpenKeyset Note: Custom commands may be created by customers. the field must be document-level and the type is restricted to Text or Memo. All command executables must be located in the <AppPath>\Commands directory in order to be detected.Connection Dim rs1 as New ADODB. This feature also allows the running of scripts (i. VBScript. Below is a run command provided by LexisNexis that can be used to populate RecordType values in the LAW case. Once the field is created. Below is a sample Visual Basic connection string. click Tools > Run Command > Populate RecordType Values.Open "tblPage".Open VBA. 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. The file description of the exe will be used as the menu item name or the filename without extension if no description exists.Administration Run Commands The following information is for advanced users of LAW and requires previous programming experience to utilize this functionality.

a "Success" message box will appear indicating the number of records successfully updated.LAW PreDiscovery User Guide E-DOC IMAGE ATTACHMENT IMAGE When the process has completed. 342 .

etc. 3. the text for the records must be indexed. Records in LAW can have up to three types of text: 1. However. If OCR is not found for a particular document. For example. Auto-indexing can also be enabled from this form. LAW will look for Printed text. OCR Printed Extracted Only one type of text for each record can be included in the index at any given time. only the OCR text will be indexed. the order in which LAW looks for text to index can be modified . 2. are handled during indexing. then by default.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. Indexing Options Options specific to the full text indexing process are located in the Indexing tab in Tools > Options. punctuation. In order to perform full text searches in LAW. 343 . These options can control how certain words. and then Extracted if Printed text is not found.see the below "Indexing Options" section. if a document contains all three types and an indexing process is executed.

Japanese. and review speed and efficiency by only including unique files in the index. The "parent" duplicate. and Korean characters .LAW PreDiscovery User Guide Indexing options include: Accent-sensitive . e-mail address. 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. Some Chinese. "Apple". Because there are no spaces separating the words on each line. LAW will not index any duplicate records in the case.Enable this option to have the indexer scan for anything that looks like a date. the text appears as lines of characters with no spaces between the words. Insert word breaks between Chinese. In a case-sensitive index. Ignore duplicate documents during indexing . and credit card numbers . "APPLE". the indexer sees each line of text as a single long word. Instead. or Korean documents that do not contain word breaks. searching. e-mail addresses. and Korean text does not include word breaks. and "apple" would be three different words. Japanese. Japanese. Automatically recognize dates. enable automatic 344 . will be included. DupStatus=P.The indexer will take accents into account in indexing words with this option enabled.Check this box if planning to search Chinese. Duplicate records will have a DupStatus of either G or C.When enabled prior to indexing. To make this type of text searchable.The indexer will take capitalization into account in indexing words when this option is enabled. Case-sensitive . or credit card number during indexing. This option is not recommended because most users would like to retrieve a document containing Apple in a search for apple. Enabling this option could increase indexing.

click the Configure button." Treat hyphens as searchable .When enabled. Auto-start indexing prior to electronic discovery imports . 345 ." Ignore hyphens . NAS. To change this order. This allows the indexing of documents during the import process. The indexer will automatically delete the word list files when the index update completes. "first-class" would be indexed as "firstclass. This is the recommended setting for cases on network drives. When running the indexer in this mode. Printed. Treat hyphens as spaces . The option is useful in the event the auto-indexing option is inadvertently left disabled.Enable this option to ensure auto-indexing is enabled prior to ED Loader imports. To restore. these files will be placed in the index folder. such as Batch Processing and the Query Builder. Options specific to the handling of hyphens are also available. As mentioned above. only one type of text (of the three possible types) can be indexed for a document at any given time. The Configure Text Priority dialog will appear. Japanese. and Korean characters so each character will be treated as single word. "firstclass" would be treated as "first class.This is the default method of handling hyphens for indexing. The Text Priority section displays the current order in which LAW looks for text when indexing document text. "first-class" would be indexed as "first-class. the documents are indexed and ready to be searched. and then Extracted. Use this setting to instruct the indexer to use the local user’s temporary folder for these files. For example." All three . right-click the icon in the system tray and choose Restore. the indexer will continue to poll the database for new documents to index until it is cancelled.During indexing. For example. A count of total documents indexed will appear when resting the mouse pointer over the icon. Use local folder for temporary files during indexing . referred to as auto-indexing. Clicking the Hide button will minimize the Auto-Indexer Status dialog to the system tray.Applies all of the above options to allow multiple ways of finding text. Note: The auto-indexer cannot be restored from the system tray when certain forms are displayed.Hyphens are treated as searchable text. The default order is OCR. For example. or SAN devices. Run index process in background until cancelled (auto-index mode) .Administration insertion of word breaks around Chinese. so that when an ED loader session is complete. the indexing process will run in the background.Hyphens are ignored 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.

such as Extracted. To remove the flag.LAW PreDiscovery User Guide Choose the desired text types for options 1. and that document is later converted to TIFF and printed text is added. choose Extracted for Option 1. This means the printed text for affected records will not be searchable in LAW. For example. [TIFF Conversion] Reset text index status . To flag a single document for indexing. and then choose <None> for options 2 and 3. and 3. In certain situations. LAW will do this automatically when creating new records via electronic discovery. LAW will also flag documents for indexing automatically when a new type of text is associated with a record. De-selecting this option will prevent LAW from re-flagging the document for indexing after the TIFF conversion and printed text is created. Records with text imported via load file will need to be manually flagged (see remainder of section). if the OCR text for a document was deemed unusable and deleted outside of LAW. one or more documents may need to be manually flagged for indexing. De-selecting this option will prevent LAW from re-flagging the document for indexing after the OCR process is performed. the document could be manually re-flagged for indexing so the printed text for that document would be indexed instead. Note: If the above index options are changed after the case has already been indexed. [OCR] Reset text index status . 2. To only include a particular type in the index. the new printed text will need to be indexed in order to become searchable in LAW.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. Flagging Documents for Indexing Documents must be in a "flagged" state in order to be included in the indexing process. 346 . choose OFF instead. This means the OCR text for affected records will not be searchable in LAW. LAW case. This behavior can be modified using the following options: 1. By default.This option is located in the OCR tab under Tools > Options and applies only to the individual and batch OCR processes. the case will need to be reindexed in order for the changes to be applied. if text is extracted from a document during the ED Loader import. Images created via scanning that are later run through the OCR process will be flagged as well. 2. For example. and raw image imports when the new record has associated text. highlight a record in the document list on the main form and choose Edit > Reset Fulltext Flags > ON.

347 . _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. 3: Record's text has been indexed. The entire case can be reindexed if needed by clicking Tools > Fulltext Index > Re-Index All Documents. If all of the documents are in one folder. 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. From the standalone grid. check the box beside Full text search. If the documents span multiple folders and can be logically grouped in a query. LAW will begin indexing automatically after the import process has been completed. Once the desired documents have been flagged. The possible values for this field are listed below: 0: No text is available for indexing. The Full Text Index Properties dialog will appear. 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). If the indexing is not performed immediately after the ED import. 2: Record was re-flagged for indexing but has not yet been re-indexed. See the "_FTIndex Field" section below to learn more about the text flag values stored in this field.Administration Resetting the text index flags for multiple documents can be done in one of two places. 1: Record's text is ready for indexing. or to reset all documents in a case. An auto-indexing feature is also available for indexing text as a background process. Indexing Documents After loading records via the Electronic Discovery Loader ("ED Loader"). launch the Query Builder (Tools > Search All Records). LAW will prompt to index once the import has been completed. This feature is located in the Indexing options in Tools > Options and is explained in the above "Indexing Options" section. Full Text Index Properties To view the index properties. utilize the grid display. This feature is useful in the event an indexing option needs to be changed or the index has somehow become corrupt. 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. and then click Index Properties. click Options. Click Yes to begin. If the option was enabled prior to import. they can be indexed by clicking Tools > Fulltext Index > Index New Documents (see next section for more information). select Tools > Reset Fulltext Flags > ON|OFF to reset the full text index flags for all documents in the current record set. allowing text to be indexed as records are being imported rather than waiting for an EDD import to complete. When records with associated text are imported via the LAW case import.

Verify Index .Compressing the index will remove obsolete records from the index. This feature will first scan the case and then return the duplicate count in a message box. 348 .This function will remove all records that were flagged as duplicate records in LAW (DupStatus=G or C) from the full text index. Compress 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. If any issues are discovered. If the "ObsoleteCount" value in this dialog is greater than zero. These obsolete documents will NOT be returned in searches. use the Ignore duplicate documents during indexing option. Three functions also exist in this screen: 1. 3. 2.LAW PreDiscovery User Guide This screen provides details about the full text index for the current LAW case. Purge Duplicates . an error will be returned after running the verify and the case will likely need to be re-indexed. Click Yes to remove the duplicates from the index or click No to cancel. use the Compress Index function. such as size and the number of indexed documents.This function will check the full text index for problems or corruption. To prevent these records from being included prior to indexing.

SQL Server Notes All testing has been performed internally using SQL Server 2000. and deselect the "Enable SQL Server/SQL Express Support" option. To disable the option. Note: This database type is enabled by default upon installation and may be disabled to remove this choice when creating a new case. click the Preferences tab. Global Default User The following user. When using the default user. See the SQL Server's instructions on how to do this. Create SQL Server LAW User Account(s) There are currently two methods of specifying user accounts for use with SQL Server. but SQL Server 7 or higher should be supported. 349 . the security mode for SQL Server must be set to SQL Server and Windows or mixedmode authentication. This allows SQL administrators to prevent LAW from accessing and modifying any other existing databases. check the Use Windows NT integrated security option when specifying the database backend for newly created cases. With this database engine type selected. 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. One of these methods must be used to allow LAW access to the LAW cases stored on the server. enter the name of the SQL Server located on the network (name of server running SQL Server). To enable this feature. This value is saved and must only be reentered if the server name changes. open any case in LAW and choose Tools > Options. with create/modify permissions. an additional database engine option of MSDE / SQL Server will be available when creating a new case. Integrated Security Windows integrated security may be used when accessing/creating SQL Server cases. choose Tools > Options > Preferences tab and check the box beside Enable SQL Server/MSDE support. When this option is used. Enable LAW SQL Server Support To enable SQL Server support with LAW. 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. Note: If using this method.Administration Configuring LAW and SQL Server Important: Please contact LexisNexis for instructions on configuring SQL Express. each individual user must be setup on the SQL Server to allow access to the case.

All information is publicly available for the customer to locate and determine the best possible configuration for its intended usage.LAW PreDiscovery User Guide LexisNexis does not provide any other SQL Server configuration recommendations or hardware recommendations. 350 .

The remainder of this topic will explain this feature in more detail. size.Administration Tracking Page Source. This page-level data is captured "real-time" for scanned pages. This data is stored in five page-level system fields (PageSource. Note: See the Page Properties Report topic to learn how to create a report containing the page-level information discussed in this topic. Images acquired via raw image or load file imports will receive only a source value. all five fields are populated as the pages are scanned into the case. in other words. Also.5x14 Double Letter (3) *11x17 Oversized (4) *Any pages outside the above 3 sizes 351 . Three of these fields are lookup fields and are listed differently within the actual database. A batch process is available to populate this missing information for TIFFed and imported images. PageHeight. Size. 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. and PageColor) in the LAW database and can be viewed in the main user interface Index display and in the two grid displays. PageHeight. PageWidth. The lookup field names as referenced in the database are shown in parentheses beside the field name displayed in the LAW interface. Field Names and Possible Values The five fields used to store these page-level properties are PageSource. PageWidth. Images created in LAW via TIFF Conversion or single document TIFFing will receive a PageSource and PageColor. and PageColor. PageSize. and can be queried using the Query Builder. and Color LAW can capture the source.5x11 Legal (2) *8. as well as images created via TIFF Conversion within LAW cases. and color at a page level for scanned and imported images. PageSize. Note: Images affected by the "Treat native TIFF images as image for record (bypass TIFF Conversion)" setting will not receive a PageColor value. Possible values contained in these fields are listed below this paragraph. the numeric values used in the database are listed in parentheses beside the textual value users will see in LAW.

352 . add PageSizeTolerance to the existing section.1.exe file).1 will still be considered a 'Letter' size page. add the section above the key value. PageSource is not affected during this process as the source can only be captured at the time the image is acquired. everything up to 8. As mentioned. The setting can be modified by editing the Law50. The default value of the tolerance is set to . Update Page Data Batch Process The Update Page Data batch process (Tools->Batch Process) can be used to populate the PageColor. and PageHeight fields for any images in the selected record set missing this information. PageWidth. for example.5) PageHeight Varies (Example: 11) Note: A page size tolerance ini setting currently exists at the application level.ini file in the application path (same folder as the Law50.6 x 11. if it does exist. The section is [Settings] and the key is PageSizeTolerance= <value>.LAW PreDiscovery User Guide PageWidth Varies (Example: 8. This setting can be used to set a margin for the page size values. If the [Settings] section does not already exist. 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. PageSize.

This reporting feature is available in both SQL and Access LAW cases.Administration Reporting Viewing Reports LAW provides several pre-defined reports that can be used to gather specific data related to electronic discovery imports. The report management screen can be accessed in one of two ways. contains reports that show ED Loader session data for the current case. See the individual report topics for more information. certain reports can be limited to the current record set loaded in the grid. The View Reports dialog will appear. The second group. If the View Reports dialog is launched from the grid. ED Loader Sessions. such as sort order. the left panel of the View Reports dialog contains two groups. General. only the Page Properties and Tally reports will be available in the report selection panel. The second method is to launch from within the standalone grid display. If a case is not enabled for electronic discovery. 353 . The first group. Generating Reports In ED-enabled cases. One method is to click File > Administration > View Reports from the main user interface. Click Tools > View Reports. A number of options. or if either grid is active when the tool is launched. are available for each report type as well as global settings that allow the inclusion of a personalized logo.

jpg. Logo Location . and a path is specified in the Logo Filename setting. Once the report has been selected and the options are set. will be removed. The two global settings are: 1. the changes persist to the other reports as well. The Global Settings apply to every type of report and when they are changed. Display Custom Logo . In order for the logo to appear. These group headers can be returned by clicking the "Categorized" button. or Bottom Right. browse to the desired image file (. Click on each report in the list to see a description in the Report Description section located at the bottom of the form. and then click Open. click the View Report button. Bottom Left. or . The path to the image will appear in the field. To remove the grouping in the options area. the logo will appear on the first page of the report. 354 . Select the desired report on the left before moving to the option selection area. The report will be generated and launched in the Report Preview screen.The logo can be placed in one of the following locations on the first page of the report: Top Left. . The group headers. click the "Alphabetical" button located above the options.If this setting is set to True. These options are discussed in the separate topics for each report (see the "Report Types" section below).To select a logo.gif). Top Right. Click the rows to view descriptions of each option directly below the options area in this panel. Global Settings and Options.bmp.LAW PreDiscovery User Guide contains the remaining reports that relate to other areas of the application. 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. 2. The second panel contains options for each report. Logo Filename . The first column lists the setting name while the second column allows editing of the setting value. the Display Custom Logo setting must also be set to True. 3. click the ellipsis button in the second column beside this setting.

and then click Save. The Save File button in the toolbar will launch the Save As dialog. browse to the desired location. 3. A Print button is also available in the toolbar for printing the report directly to paper or to a file. enter a file name. 5. Once the file type is chosen. From here. Report Types The following reports are available in the View Reports dialog: 1. 2. the file type for the report can be selected from the Save as type drop-down list. 4. ED Loader Session Exception Deduplication or Inter-Case Deduplication* Files By Type Files By Type Summary 355 . such as Adobe PDF.Administration From the Report Preview screen. the report can be previewed and then saved to file or printed.

LAW PreDiscovery User Guide 6. 356 . 7. Page Properties 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.

this option will be set to All Sessions. the following options are available for the ED Loader Session report: 1. 2. meaning all sessions in the current case will be included in the report. Sort Field .This option will sort the sessions based on the date and time the session was created in the ED Loader.Two fields are available for sorting the report: 1. Click the ellipsis button in the second column to launch the Select Sessions dialog and select specific sessions. 2. Included Sessions .By default. ED Loader Session Report Contents This section discusses the contents of the ED Loader Session report.The session label is specified in the ED Loader Sources tab prior to the start of each session. Date Created . This option will sort the report based on the session label values. Clicking on the Title or Created column header will sort the session list.Choose Ascending or Descending for the values in the selected sort field. Session Label .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. 3. Sort Order . 357 .

The above data is a summary of the Status field found in each session-level section of the report. embedded files.) and the total file size. and the approximate processing speed in records per hour. archives. process was cancelled by user). e-docs) in this section. The Session Contents section (above) shows counts for all e-docs.e. 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. commit errors. Below the header in the session summary. which displays the number of records written to the LAW case database (after full expansion). Session-level sections will contain the session label. the session summary. The above image shows the next area of the report. 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. The next three sections of the summary are also included in both the session summary and session-level areas. warnings. e-mails. indicates the number of sessions included in the report within the header (see above image). 358 . and archive attachments in the selected sessions (including files that received errors or warnings. The Errors/Warnings section (above) displays totals for processing errors. and start date and time for the session (see above image). the estimated time it took to process (or import) the data. session ID. and incomplete records for all selected sessions. The file counts and file sizes (post-process sizes) are also broken down by file type (i. as shown in the above image. e-mail attachments. These four items are available in both the session summary and session-level sections of the report. the report displays counts of recoverable and non-recoverable items for all selected sessions. The session-level section provides the session status and creator (user and machine name extracted when session is initialized) (see above image). the number of items processed (prior to expansion).e. etc.LAW PreDiscovery User Guide The first section of the report. filtered files.

Post-process file sizes are also included for the last three items mentioned. Click the ellipsis button in the second column to launch the Select Sessions dialog to select specific sessions. and Errors. Report Options In addition to the Global Settings. this option will be set to All Sessions. Exception Report Contents The Summary section of the Exception report provides three sets of information: Item Summary. The Item Summary displays a count of items processed (prior to expansion). 359 . filtering.). the following option is available for the Exception report: 1. items discovered (after expansion). Filters. This report focuses on records that were filtered or received errors or warnings during the ED Loader import process. meaning all sessions in the current case will be included in the report. errors. and records that were not written due to errors or filtering. Included Sessions . Clicking on the Title or Created column header will sort the session list. etc.By default. records written to the LAW case database (after expansion.Administration Exception Report The Exception report provides both a summary and a detailed overview of ED Loader session exception data.

360 . and file type) and provides a count and post-process file size for each. commit errors (errors that occurred during processing and prevented the record from being written to the case database).if no records matched a particular filter. a list of warnings and error messages. filter actions. NIST/NSRL. The Details section of the report provides a more detailed view of filtered records. deduplication. warnings.LAW PreDiscovery User Guide The Filters section displays a list of the ED Loader filters (conditional. and incomplete records (records that will be listed in the Incomplete tab in the ED Loader's Session Viewer). and a list of sessions included in the report. 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). 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 . the file count and file size for each scope and action setting is included in addition to the totals. For the filters that include scope and action settings (Duplicates and File Types). then that filter will not be shown.

Administration The next portion of the Details section. The sessions are referenced by their session labels. contains a list of sessions included in the report. The total number of included sessions is also displayed here. 361 . 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. shown above. The last portion of the Details section. Total error and warnings counts are also shown. shown above.

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

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

The term "supported" refers to files with a valid source application assigned for printing. A report generated using the All File Types option is shown in the below image. c. will be included in the report.Three filters for the report are available: a.This option includes unsupported file types only in the report. 364 . Supported File Types . such as Adobe Acrobat or Microsoft Word. Files By Type Summary Report Contents The contents of this report will vary depending on the selected options. Non-ED records may be included depending on the state of that setting (see #2). Report Options In addition to the Global Settings. This report does not include a listing of every native file path.This option includes both supported and unsupported file types in the report. Include Non-ED Records . Non-ED records may be included depending on the state of that setting (see #2).When set to True. the following option is available for the Files By Type report: 1. b. which is the key difference between the Files By Type Summary and the Files By Type report. File Type Filter . All File Types . 2.LAW PreDiscovery User Guide 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. Unsupported File Types . non-ED records such as scanned images or images imported via load file.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).

Administration This report shows a listing of each unique file type included in the case. the total number of pages. If the PgCount equals zero. The Pages value is pulled from the PgCount field in the LAW case. For each file type. 365 . LAW will check the EDPages field and use that value. and the total file size (post-process). the report provides a total file count.

followed by duplicate totals. All custodians in the case will be listed here and a duplicate summary will be included for each custodian. the "Deduplication Report" will be available in the View Reports dialog. If documents in the LAW case were deduplicated using the ED Loader or LAW's internal Deduplication Utility (or not deduplicated at all. the Group File List By option can be used to group the file list by parents or duplicate records.If the Parent/Duplicate File List is included in the report (see above option). This report does not list the case name at the top since the information may apply to more than one case. the following options are available for the two deduplication reports: 1. then the "Inter-Case Deduplication Report" will be displayed in the report list. 366 . Deduplication Report Contents Two sections exist below the Summary header in the deduplication report: Process Summary and Duplicates. 3. the report will contain a "Parent/Duplicate File List" section which lists every parent and duplicate record (minus attachments) in the case(s). This report includes the same information as the Deduplication report. Group File List By . but includes data from any cases the current case was deduplicated against.When set to True. Set this option to False to exclude the Custodians section from the report. the report will contain a "Custodians" section. 2. If the case was last deduplicated using the external Inter-Case Deduplication utility. Report Options In addition to the Global Settings. Display Custodian Details .LAW PreDiscovery User Guide Deduplication Reports The Deduplication report provides a summary and detailed view of deduplication information for the current case.When set to True. Display Parent/Dup File List .

If the Display Custodian Details option was set to True prior to creating the report. the following Custodians section will appear below the Summary. Atts section since those records have received a duplicate status based on their parent record.Administration In the Process Summary. 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).) section since it is the master duplicate of the family. while the Unprocessed count represents the number of records that have not been deduplicated (DupStatus = Null or U). The Custodians section contains the same information as the Summary.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 file sizes of the duplicate files in LAW are provided beside these totals in both MB and GB. then. but is the section is sorted by Custodian name and the data is broken down for each custodian in the associated LAW case(s). Files that are ineligible for deduplication (i. The "Dup. For example. The Processed count represents the number of records that have been deduplicated. If the Display Parent/Dup File List option was set to True prior to creating the report. The Total Duplicates count is the total number of records that have been flagged as duplicates (DupStatus=G or C). In the above example. 367 . an e-mail item containing two attachments would be counted as 1 record for the Dup. the Total Records count represents the number of records in the current LAW case (and member cases if the report spans multiple cases). (non-att. the following Parent/Duplicate File List section will appear next. The "Dup. (non-att.)" count is the number of records that are duplicates (DupStatus=G or C) and may or may not have attachments. Atts" count is the number of records that are duplicates (DupStatus=G or C) and are attachments. the two attachments would be counted as 2 records for the Dup.

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

Choose from one of the following options: Page Source. 3. Group By Field (Primary) . size. 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). the following options are available for the Page Properties report: 1. The values in the selected field will appear in the Y-axis.When the range is set to All Documents. Page Color was selected for the primary "group by" field and Page Size is in the Y-axis. or Page Color. and color information at a page level for images in a case. 369 .Choose from one of the following options: Page Source. The report will be grouped by the selected field. Group By Field (Y-Axis) . Document Range . In the following example. 2. 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. or Page Color. Page Size. Report Options In addition to the Global Settings. The same field cannot be selected for both the Primary and Y-Axis grouping options. Page Size. the report will span the entire LAW case. Page Properties Report Contents The report layout will vary depending on the fields selected for the primary and Y-axis grouping.Administration Page Properties Report LAW can capture the source.

as those were the colors found in this particular case. the Y-axis holds the various page sizes that were found in the LAW case. Color.e. and Color topic. Feeder) and totals are listed horizontally in each section. Within these sections. Size. what the fields mean. 370 . and how the data is populated. The Source data (i. the primary sections are listed as Black & White. Note: To learn where the Page Properties report data is pulled from. Totals for the page sizes or Y-axis fields are located at the end of the row (down the right side of the report).LAW PreDiscovery User Guide Since the above report is grouped by color. see the Tracking Page Source. and Unknown Color.

371 . If Totals is selected.Select the field to be tallied in the report from this drop-down list. the Tally report will be grouped by any custodians that exist in the current case.This option is used to sort the data in the "Sort Field" Ascending or Descending in the report. Sort Order . the data will be sorted based on the tally results for each field value.the following types of fields are excluded from this list: page-level fields. Field To Tally . Document Range . the report will span the entire LAW case. 5. Number of Columns . B. the following options are available for the Tally report: 1.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 userdefined index field followed by the total number of times that unique value exists in the selected index field. Sort Field . Choose None to avoid applying a specific sort order. the data will be sorted alphabetically based on the values located in the selected tally field. as indicated in the header below the LAW case name. 3. Display Custodian Details . 2. Field values containing delimited lists such as “A. Most system fields and user-defined fields will be listed here . If Field Values is selected. Tally Report Contents The following Tally report sample is set to display custodian details and the tally field is set to DocExt. 4. auto-increment fields. C” will be tallied as a single unique value rather than individual items. this option will not be available. Report Options In addition to the Global Settings.The following two options are available for sorting the data in the report: Field Value or Totals. fields with the Unique property applied.The data in the report can be displayed in 1. Note: If the current case is not ED-enabled. or 3 columns on each page of the report. the data will automatically be truncated to 255 characters in the report.When the range is set to All Documents. and any field starting with the character "_" (underscore). 6. 2. 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). Warning: While memo fields are included in the Field To Tally list.When set to True.

If the tally field does not contain a value for any of the selected documents. the report will appear as shown below: 372 . the report will include a <Null> entry. in the above report. The count of each unique value is displayed to the right of the value below the section heading. The number to the right in the heading indicates the total number of field values in the tally field for each custodian.LAW PreDiscovery User Guide The number beside the custodian indicates the number of unique field values for that custodian. For example. If the Display Custodian Details option is set to False. five records exist with a value of "CustodianA" in the Custodian field and a value of "doc" in the DocExt field.

373 . These include . 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. and other RFC822-format e-mails.msg files. E-mail includes both e-mail messages contained in mail stores and loose e-mail messages. DupStatus is a single character field and will contain one of the following values: U . Users can choose which of these is used in the deduplication process in the ED Loader options. if the key is regenerated in the future. and brief explanations of deduplication options and their resulting output. E-docs: The key value is generated using the entire file as the input. C . the value would match the original. E-mail: The key value is generated using an input value of certain metadata after processing of the metadata fields has been executed. 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.Indicates the record is a custodian-level duplicate.Indicates the record was not tested (not deduplicated).Indicates the record was tested and was not determined to be a duplicate at the selected scope (Global/Custodian-level).AttachmentContentHash (if the "Include attachment hashes in e-mail metadata hash" option is enabled in the ED Loader Deduplication setting. the ED Loader generates two output hashes in parallel: MD5 and SHA-1. This is the primary field used for differentiating duplicate items from non-duplicate items. 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) . Items discussed include: methods used to deduplicate e-mail and e-docs. G . DupStatus: Indicates the duplicate state of the document. N . file hashing and metadata hashing are the two primary methods used by the ED Loader for generating keys. a list of deduplication-related fields and possible values. . The purpose of using the post-processed metadata is to match the metadata that is stored in LAW.Indicates the record is a global-level duplicate. therefore.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.OR . Currently. 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).eml files.

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

Records without native files can still be flagged as duplicate parents or children. 375 .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.

csv)" in the "Save as type" drop-down list in the "Save Results As" dialog box. CaseLogistix . you must select "Unicode Text (Tab delimited)(*. Proper language packs must be installed on the computer in order for the associated Unicode characters to display within LAW’s user interface. While the rest of the case path can contain Unicode. These Unicode paths can be retained and displayed in the main folder view and any other applicable folder view in the application. Also ensure the export path does not contain Unicode. do not use the Mirror Original folder naming scheme if Unicode folders exist in the case. Unicode data can be retained when exporting field data from the two grid displays. Files with Unicode file names or residing in a Unicode path may be imported using the ED Loader. text. Unicode is only supported in Concordance versions 10 and above. The two grid displays in LAW do not support Unicode.Unicode is automatically included if present in the exported data. Index field names cannot contain Unicode characters. The "Text/RTF Printer" does not support Unicode text files.Unicode data will be included only if the "Allow Unicode data (UCS-2 format)" option is enabled in this format's configuration settings. Unicode is not supported in LAW case names. Delimited Text . To print Unicode text files. The ExperVision and TextBridge OCR engines do not currently support Unicode. Unicode paths and filenames may prevent the target applications from opening the associated image. when exporting to a format that does not support Unicode. if Unicode characters exist in a field they will be displayed in a pop-up text box when resting the pointer over the cell. Notepad supports shell prints. Unicode data is supported in the Export Utility in the following export formats: 1. 5. In order to retain this data in the output file. However.Unicode data will be included only if Concordance version 10 or above is installed on the machine and the "Create Concordance 10.Unicode is automatically included if present in the exported data.LAW PreDiscovery User Guide Unicode Support LAW versions 5. Concordance . Unicode existing in the metadata will be retained and can be displayed in the Index display. use either Microsoft Word or the Shell Printer as the source application. Supported languages can be found in the Language drop-down list located in the OCR tab in Tools > Options. 2. This is a limitation of the underlying component.0 database (supports Unicode) setting is enabled in the format's configuration settings. it is recommended the case paths do not contain Unicode characters to avoid potential issues with 3rd party applications. provided the proper language pack(s) are installed on the system. In the Export Utility.Unicode data will be included only if the "Allow Unicode data (UCS-2 format)" option is enabled in this format's configuration settings. you must ensure that the application registered on the system for text files supports shell prints For example.2 and higher will support the Unicode standard.0 . 3. 376 . 4. EDRM XML 1. Concordance Direct DCB . It will support RTF with Unicode. Note: If using the Shell Printer. Printed and extracted text will contain Unicode data if it exists in the original file and can be displayed. and/or native files.

Select All Pages (if thumbnails display has focus) <Ctrl+A> .OCR Document <Ctrl+P> .Page Size .5 x 11") F8 .Rotate Left (current or selected pages) <Ctrl+M> .Letter (8. Flatbed ** ** Scanner must support these modes to have any effect.Deskew Document F5 . Control Keys <Ctrl+A> .Page Size .Append Document F6 .Help File F3 .Hide All Fields (if Search Results window has focus) <Ctrl+E> .Show All Fields (if Search Results window has focus) <Ctrl+X> .Merge Documents <Ctrl+O> . Duplex ** F12 .Scan Mode &endash.Legal (8.Replace Pages F7 .Goto Page <Ctrl+L> .Split Document <Ctrl+Z> . and a grid display is currently active.Rotate Right (current or selected pages) <Ctrl+S> .5 x 14") F9 .Find Page ID <Ctrl+G> .Page Size . please ensure that Review Mode is disabled in the grid.Scan New Batch F4 .Simplex F11 . See the Tagging Records section for more information.Edit Page ID <Ctrl+F> .Scan Mode &endash. Function Keys F1 .Zoom Lock 377 .Save Image (saves image with current page orientation) <Ctrl+U> .Select All Documents (if document list has focus) <Ctrl+A> .Double Letter (11 x 17") F10 .Print <Ctrl+R> .Scan Mode .Appendix Shortcut Keys Note: If the shortcut keys are not functioning.

24-bit Color Scanning <Ctrl+F3> .Scan New Attachment <Shift+Ins> .Pan Up (moves image.Zoom Out <Ctrl+Left> .Decrease scan brightness (32pts) Document List Keys Note: The focus must be on the document list to use these shortcuts. if zoomed) <Ctrl+Right> .Clear current region (if main image has focus) <ESC> .Delete Document <Spacebar> . <Left> .Black and White Scanning <Ctrl+2> .First Page <End> . if zoomed) <Alt+UpArw> .Merge Annotations <ESC> .Next Document <Home> .Delete Pages <Ctrl+F12> .Previous Document <Down> .Clear selected pages (if thumbnails display has focus) <Ctrl+PgDn> .LAW PreDiscovery User Guide <Ctrl+1> . if zoomed) <Ctrl+Up> .Pan Down (moves image.Insert New Pages (from scanner) <Shift+Del> .Last Page <Delete> . if zoomed) <Ctrl+Down> .Next Page <Up> .Attach to Previous <Shift+Bksp> .Pan Right (moves image.Replace Document <Ctrl+Ins> .Pan Left (moves image.Detach All <Ctrl+F4> .Increase scan brightness (32pts) <Alt+DnArw> .Zoom In <Ctrl+PgUp> .Enhance Image menu <Ctrl+F6> .Previous Page <Right> .8-bit Grayscale Scanning <Ctrl+3> .Toggle Page Selection for Current Page 378 .

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

Sign up to vote on this title
UsefulNot useful