LAW PreDiscovery™ 6.0.05 Release Notes -...

67
LAW PreDiscovery™ 6.0.05 Release Notes Release Notes All rights reserv ed. No part of this w ork may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopy ing, recording, or by any information storage or retriev al sy stem, w ithout permission. While the information contained herein is believ ed to be accurate, this w ork is prov ided "as is," w ithout w arranty of any kind. The information contained in this w ork does not constitute, and is not intended as, legal adv ice. Lex isNex is and the Know ledge Burst logo are registered trademarks of Reed Elsev ier Properties Inc., used under license. LAW PreDiscov ery , is a registered trademark, Concordance is a registered trademark, and CaseMap is a trademark of Lex isNex is, a div ision of Reed Elsev ier Properties Inc. Other products or serv ices may be trademarks or registered trademarks of their respectiv e companies. © 2010 - 2011 Lex isNex is, a div ision of Reed Elsev ier Inc. All rights reserv ed. LAW PreDiscov ery ™ Concordance® CaseMap® Lex isNex is® Total Litigator Lex isNex is® Early Data Analy zer

Transcript of LAW PreDiscovery™ 6.0.05 Release Notes -...

Page 1: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

LAW PreDiscovery™ 6.0.05Release Notes

Release Notes

All rights reserv ed. No part of this w ork may be reproduced or transmitted in any form or by any means, electronic or mechanical, including

photocopy ing, recording, or by any information storage or retriev al sy stem, w ithout permission.

While the information contained herein is believ ed to be accurate, this w ork is prov ided "as is," w ithout w arranty of any kind. The information contained in

this w ork does not constitute, and is not intended as, legal adv ice.

Lex isNex is and the Know ledge Burst logo are registered trademarks of Reed Elsev ier Properties Inc., used under license. LAW PreDiscov ery , is a

registered trademark, Concordance is a registered trademark, and CaseMap is a trademark of Lex isNex is, a div ision of Reed Elsev ier Properties Inc.

Other products or serv ices may be trademarks or registered trademarks of their respectiv e companies. © 2010 - 2011 Lex isNex is, a div ision of Reed

Elsev ier Inc. All rights reserv ed.

LAW PreDiscov ery ™

Concordance®

CaseMap®

Lex isNex is® Total Litigator

Lex isNex is® Early Data Analy zer

Page 2: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

LAW PreDiscovery2

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

Table of Contents

Release Notes

................................................................................................................................... 31 Enhancements

................................................................................................................................... 372 Resolved Issues

................................................................................................................................... 643 Known Issues

................................................................................................................................... 654 Additional Information

Index 67

Page 3: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

Release Notes 3

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

This document provides release details for the current release and all previous releases.

Enhancements

This topic lists product enhancements introduced in the current and previous releases of LAWPreDiscovery.

Version 6.0.05

New Features

Administration

The ability to delete SQL databases from the server on case deletion may now bedisabled with an ini setting. See help file for details.

Batch Processing

The machine name of the station processing a document during batch processing is nowstored in the BatchStation field. Note: This is only supported in ED-enabled cases.

Early Data Analyzer

The Early Data Analyzer module is now available (http://www.lexisnexis.com/eda). Thismodule allows early culling and analysis to reduce data sets prior to processing withLAW. Note: This module requires an additional license.

ED Loader

A new setting was added to restrict language identification to the most commonlyencountered languages.

ED Loader

Metadata extraction capabilities have been enhanced for the ED Loader. Custommetadata fields may be extracted from PDF and MS Office Files (Word, Excel, andPowerPoint). EXIF metadata may be extracted from TIFF/JPEG files. Detection ofcomments and tracked changes is available for Word/Excel files. Detection of hiddensheets, rows and columns is available for Excel files. A new Metadata settings categorywas added to allow configuration of these settings. Note: None of these enhancedmetadata properties are stored in the main document table, they are stored asextended properties in an alternate storage schema. Because of this, they are notvisible in the grid displays in column format. They must be viewed in grids by enablingthe extended property view (View -> Extended Properties or new toolbar button).

ED Loader

The elapsed time taken to process an import session is now displayed in the sessionbrowser dialog.

ED Loader

The machine name of the station performing an import is now stored in theImportStation field.

Page 4: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

LAW PreDiscovery4

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

ED Loader

ThreadID field was added to the ED Template. This field can be used to group messagethreads together. Note: This field is currently only supported for MS Outlook.

Exports

Concordance exports now support the creation of load files for the Concordance NativeViewer (CNV). Support for CNV must be enabled from the configuration dialog.

Licensing

Undocked keys can now be created without an internet connection. Note: This requiresspecial authorization from LexisNexis to enable support for this functionality on themaster key. Keys with this functionality enabled are not backward compatible withprevious versions of the software.

Modifications

ED Loader

Accuracy and performance of language analysis has been significantly improved.

ED Loader

Modified logic used to detect embedded images in Outlook messages than cansignificantly improve import speed in certain situations.

ED Loader

The 'Preserve X.400 addresses' setting is now enabled by default.

ED Loader

The memo title header was removed from e-mails extracted from Lotus Notes stores.Note: This header was only present in version 5.9.

Grid Views

Second confirmation on grid view save was removed.

Version 5.9.25

New Features

ED Loader

Distributed processing is now available in the ED Loader. This feature can be enabledfrom the 'General' settings. Distributed processing is only available for SQL cases, andLMC must be properly configured to create a distributed import.

Embedded images in RTF content can now be extracted from Lotus Notes e-mails. Thisfeature can be enabled from the 'E-Mail' settings. Extracted images will be treated asnormal attachments (ie. Not rendered in the HTML output).

Hidden text can now be detected in Word, Excel, and Powerpoint documents during

Page 5: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

Release Notes 5

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

imports. This feature can be enabled from the 'Text Extraction' settings. If hidden text isdetected, the document will be flagged (HiddenText field), and the detected hidden textwill be inserted at the top of the extracted text for easy review.

Language detection is now available in the ED Loader. This feature can be enabled fromthe 'Text Extraction' settings.

Meeting items in Lotus Notes mail stores are now rendered with a customized templatespecific to meetings, instead of the standard e-mail template.

Support has been added for AOL, MSN, and Yahoo instant message archives. Thesesarchives will be rendered to HTML for display during the import process.

Support has been added for Outlook Express mail stores (*.dbx). Outlook Express is notrequired. Messages extracted from OE stores will respect the same output setting asOutlook messages.

Exports

A new option is available in the EDRM XML export settings to link to images and files intheir current location.

A new option is available in the Summation export to include an @EDOC token for e-mails extracted from mail stores.

Modifications

Deduplication

The Deduplication Utility was updated to handle connection drops for SQL cases.

Grid Views

If a user modifies the current view in a grid, and has not saved it before exiting the grid,the Manage Grid Views dialog will now appear instead of a simple save prompt. This willallow the user to see the active grid view before saving, and create new ones.

Management Console

Jobs in the management console (LMC) are now separated into two types, standard"Batches" and "ED Imports".

OCR

Several performance enhancements were made for the ABBYY OCR engine (30-50%faster).

System

Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

TIFF/E-Print

The eDrawings Viewer source application now references the 2011 version. It will nolonger work with previous versions.

User Interface

The Reports button is now disabled unless the user has an Admin license in the currentsession.

Version 5.8.14

Page 6: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

LAW PreDiscovery6

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

New Features

Administration

Implemented consistent database reconnect behavior for SQL cases in the followingareas of the application: batch processing, imports, exports, and several key manualoperations. This allows LAW to automatically reconnect when a SQL connection is lostduring a session. While performing automated processes (import, export, batch), if a SQLconnection is lost, LAW will wait indefinitely for the SQL connection to be restored beforeresuming processing.

Batch Update

The batch update process was modified to improve performance significantly on largeupdates.

ED Loader

dtSearch engine was updated to version 7.65. See http://www.dtsearch.com/ReleaseNotes765.html for details.

The default source application for MSG files (filetype=148) has been changed to the"Shell Printer" to allow for increased print speeds. This change applies when creatingnew file type management databases. If the database already exists, it must be editedmanually to apply this change.

Imports

Select All and Clear All buttons have been added to the Import Fields dialog forSummation and EDRM load file imports. Columns can now be sorted ascending ordescending by clicking the column header.

Log Viewer

Error logs for LAW case and load file imports are now stored in the case folder($Logs\Import) and will be displayed in the Log Viewer.

Management Console

Improved handling of stalled client machines during a distributed batch processing job.Client node names will turn red and will be restarted automatically if they are stalledlonger than the amount of time listed in the new "Auto Restart Client" LMC setting (Tools-> Options). A client can also be manually stopped and restarted using the End Processbutton located on the client details panel.

Client activity times are now reported in GMT for consistent logging regardless of clientstation's time zone. Note: The job start time is still displayed in the time zone of thestation that created job, but the actual job start time is based on GMT to allow clients tostart at the expected time for jobs scheduled to start in the future regardless of currenttime zone on the client station.

Reporting

Modified the ED Loader Session Report to more accurately summarize the record typesimported into the LAW case.

Run Command

Minor SQL server related performance improvements made to the TextPathExtractorcommand.

Searching

Page 7: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

Release Notes 7

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

The "Max Files to Retrieve" full text search setting default for new cases has been

changed from 500 to 0 (unlimited).

TIFF/E-Print

If documents have been processed in alternate time zones, or a time zone different thanthe current, the TIFF/E-Print process will prompt the user to synchronize the time zonesduring processing by changing the current time zone during processing. This is requiredin many cases to ensure that date/time fields within documents that may containdynamic date fields (ie. MSG e-mails, office documents, PDF files, etc.) match the desiredtime zone in the paper or TIFF output.

User Interface

A button to launch the View Reports dialog has been added to the toolbar on the main

form (to the right of the Export Utility button).

Modifications

Administration

Cases can now be deleted from SQL Server when removing cases from the case list. The

option to back up the case prior to deletion is available.

Top-level folders and all sub-folders below them can now be deleted from within LAW

using the folder deletion function.

ED Loader

A date range filter for e-mails has been added to the ED Loader Exclusion settings.

The ED Loader now supports MBOX e-mail archives.

The time zone used when importing electronic files can now be specified from the ED

Loader General settings ("Time Zone Selection" section). The "Translate date fields touniversal time (GMT)" setting will be disabled for new cases as the new time zonesetting replaces it. However, it will still be available for legacy cases for backwardcompatibility. The time zone chosen for processing will be stored in a "TimeZoneProc"field (created automatically in new cases only).

Exports

Native files can now be optionally included at the document level for image+native

exports based on a tag field. The "Include native for tagged documents only" setting onthe Advanced tab controls this functionality.

Page markers can now be specified and applied to OCR and Printed text (upper left

corner) during the export process. The "Insert page markers in text" setting is located inthe Text Options dialog.

Help

A new online help system has been added (requires Internet access). In addition to an

online version of the help file, it contains tutorials and information on training. To accessthis new help system, select Help -> Online Answer Center from the main form or theexport utility.

Imports

Existing images in a case can now be replaced using the Import -> Image Replacement

Load file feature. There is an option to rename the original instead of replacing itavailable. Supported load files are *.LFP, *.OPT, and *.LOG files.

Page 8: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

LAW PreDiscovery8

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

Numbering

Page-level numbering now suppports a "++" suffix syntax to auto-increment a documentat the page level using a document level index field as the seed (ie: "&[<FieldName>]++").

The "Allow parent/attachment families to span across sections" option has been addedto control whether rolling numeric sections span across document families.

Searching

In addition to the grid views, query results can now be sent directly to the BatchProcess, Export Utility, Batch Update, or Report Viewer using the "Send Results To"option on the Query Builder form.

TIFF/E-Print

Microsoft Office 2010 is now officially supported. Note: The use of ED Loader on amachine with Outlook 2010 (64-bit version) is not yet supported.

Version 5.7.05

New Features

Exports

Records for native files that do not have an associated file in LAW can now optionally beincluded in native exports by selecting the 'Include records without files' option underthe 'Include Native Files' setting on the Formats/Documents tab of the Export Utility.

Text files (or content if embedded) can now optionally be excluded during exports at therecord level by selecting the 'Omit text for tagged documents' option on the Text Optionsconfiguration dialog of the Export Utility.

Imports

A character encoding option is now available in the delimited text import. Auto-detectionof the selected load file will be performed when a file is selected for import. LAW canauto-detect between Unicode, UTF-8 (requires BOM), and standard ANSI (ISO-8859-1)automatically. If another encoding is used, it must be set manually.

OCR

Support for the ABBYY FineReader OCR engine is now available. The ABBYY engineincludes support for CJK (Asian) languages and PDF/A output. Note: This requires anadditional license. Please contact your sales representative for purchase information.

Reports

New reports were added to the new reporting engine (File -> Administration -> ViewReports). The following reports are now available: Deduplication Report, Page Properties(source, size, and color), and a Tally Report (on a selected field).

Run Command

A new custom command is included to capture the file sizes of text extracted during EDimports. The command will show up as "Capture Text File Sizes" in the Run Commandmenu.

Page 9: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

Release Notes 9

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

Modifications

ED Loader

dtSearch engine was updated to version 7.64, see http://www.dtsearch.com/ReleaseNotes764.html for details.

The file identification engine was updated to version 2.27.

Imports

The handling of attachments in EDRM imports was modified to force an attachment intothe same folder as the parent. EDRM files produced by Encase may place attachments inseparate folders than the parent document, which is not permitted in LAW.

Reports

The new reporting engine can now also be accessed from the external grid display(Tools -> View Reports).

The new reporting engine now persists all settings at the case level.

The new reporting engine now supports reports based on the current recordset if a griddisplay is active.

The new reporting engine now supports the ability to control the position of a reportlogo if specified.

Version 5.6.14

New Features

Batch Update

An "Auto-increment selected text/memo fields" option has been added to the BatchUpdate dialog in the standalone grid display. When enabled, the values entered for allselected text and memo fields in the Batch Update dialog will increment by one for eachdocument in the grid. The Batch Update feature has also been optimized for improvedperformance on SQL cases and can now be used to auto-number document sets in afraction of the time required by the document numbering batch process.

Deduplication

LAW cases can now be deduplicated against each other using the standalone Inter-Case Deduplication Utility. A link to this utility can be found in the LAW PreDiscoveryprogram group. This tool is intended for use after cases have been populated withdocuments via ED Loader imports. Documents may be deduplicated globally or on acustodian level using the MD5 or SHA-1 hash values calculated during the importprocess.

ED Loader

A "NIST" filter has been added to the ED Loader Settings tab and can be used to filter e-documents based on the collection of SHA-1 hash values published and maintained bythe National Institute of Standards and Technology ("NIST").

An "Export to Excel" function has been added to the File menu and toolbar in theSession Viewer and is used to save all tabs in the Session Viewer to a single Excel file atone time.

Two new tabs have been added to the Session Viewer: Overview and Settings. TheOverview tab contains a number of different totals for the selected session, such as total

Page 10: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

LAW PreDiscovery10

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

number of records written and error counts. The Settings tab lists all ED Loader settingsand the state of the settings for the selected session.

Exports

A "Truncate text values that exceed their field size" setting has been added to theConcordance Direct (DCB) export configuration settings. When enabled, records withtext values that exceed their field size will still be added, and have any offending textvalues truncated, with a warning logged. When disabled, records with text values thatexceed their field size will not be added and the previous behavior of listing offendingfields and their destination field sizes will apply.

Folders

Folders in the main folder navigation display can now be moved by clicking Folder ->Move and selecting the new location in the browse window.

Grid Views

Field delimiters can now be specified when saving record data from the grid displays. TheSave button or menu item in the grid displays (previously Save All Records and SaveSelected Records) will invoke a Save Options dialog to specify the document range (all orselected), output filename, text format, and delimiters.

Licensing

License keys for LAW now support the use of remote desktop sessions correctly withoutusing hard licenses of the key for every sublicense used. This requires an update to theSentinel system driver to version 7.5 or later, which is included in the installer and will beautomatically installed. NOTE: If the host system with the hardware key does not haveLAW installed, the driver will needed to be updated there as well or LAW will not runafter installing this update. The driver can be downloaded directly at http://www2.safenet-inc.com/support/tech/latestdriver.asp

Reporting

Additional functionality has been added to the Full Text Reports dialog in the QueryBuilder and the reporting capability has been revised. This feature can now be used toreport on and execute multiple search requests at once (as opposed to the singlerequest supported via the Query Builder). Document and hit counts are returned the FullText Reports dialog instead of the standalone grid, eliminating the wait time involvedwith loading a large number of records into the grid.

New reporting functionality has been added. Four new reports are available for ED-enabled cases: ED Loader Session Report, Exception Report, Files by Type, and Files byType Summary. These reports are available from the File -> Administration -> ViewReports menu. These new reports are intended to supplement the ED Reports availablefrom the grid display. The File by Type reports are similar to the grid-based reports, butadditionally contain file size information.

Text Indexing

A "Text Priority" setting has been added to the text index options (Tools -> Options ->Indexing tab) and can be used to set the priority of the text files used for the full textindexing process. The default priority order is OCR, Printed text, Extracted text.

A "Verify Index" function has been added to the "Full Text Index Properties" dialog. Thisfunction will validate the full text index for the current case.

A new function, Purge Duplicates, can be accessed from the full text index properties(enable text search from query builder, hit options button in text area, hit IndexProperties button). This function will scan the text index looking for any documents thatare flagged as duplicate in LAW. If any are found, the number will be reported to theuser and prompted with a confirmation to remove. Removing duplicates from the text

Page 11: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

Release Notes 11

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

index will improve the efficiency of text searches by eliminating any duplicates from beingsearched and returned.

A new setting has been added to the OCR and TIFF options to allow more control overthe text index flag (_FTIndex). The state of the "Reset text index status" setting willcontrol whether documents are re-flagged for full text indexing after OCR or printed texthas been added for a document. The default behavior (disabled) is to update the indexstatus whenever new text is added, or modified.

An "Ignore duplicate documents during indexing" setting has been added to the textindex options (Tools -> Options -> Indexing tab). When enabled, records flagged asduplicates in LAW (DupStatus=G or DupStatus=C) will be omitted from the full textindexing process.

Text Search

A new function, Tag Text Hits, has been added to the query builder. This function allowstagging of text hits without actually running the text search. This feature is optimized toconserve memory allowing results sets to be tagged that cannot run directly due tomemory constraints. This process is multithreaded so it will take advantage of multicoresystems distributing the search across multiple cores. NOTES: 1) This function is limitedto the text search term only, it does not incorporate database conditions, 2) Availablefields for tagging are unlocked, non-system TAG or NUMERIC fields. Selecting a TAG fieldwill tag each record that contains a hit while selecting a NUMERIC field will store thenumber of hits per document for the term.

Modifications

ED Loader

Added support for Date/TimeAppStart and Date/TimeAppEnd metadata fields for LotusNotes appointment/meeting items.

ED Loader database reconnection behavior has been extended to cover time-out errorson SQL Server.

HTML and Text converted from Lotus Notes appointment items will now contain a Startand End time in the header if this data is available and considered valid.

HTML converted from mail stores is now saved as UTF-8 if the encoding specified in theHTML is explicitly declared as UTF-8. Previous implementations would save the HTML fileas UCS-2, potentially resulting in some Western-European characters not renderingcorrectly without changing the encoding in the web browser.

LAW will now respect the system's daylight savings setting for timestamps extractedfrom Outlook e-mails (previously, DST adjustments were universally applied to metadatadates regardless of system setting).

Text is no longer extracted for records marked as duplicates when using the "PartiallyExclude (Log record but do not copy file)" action is selected.

The case list and case selection panel has been removed from the Session Viewer. TheFile -> Open command has been modified to allow the selection of a different case orspecific session database (job.mdb).

The custodian assignment can now be modified when the ED Loader is launched in insertmode (Edit -> Insert -> E-Document(s) | E-Document Attachment(s)).

Endorse

LAW will no longer force JPEG compression on all non-binary (color/greyscale) imagesduring the endorse process. It will attempt to retain the original compression of non-binary images. Supported compressions are: None, Packbits, LZW, and JPEG. If the

Page 12: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

LAW PreDiscovery12

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

compression cannot be detected, or is not one of these, JPEG will be used as a default.An INI setting is available to revert to the previous behavior if desired.

Exports

The contents of the Control List created during exports no longer wraps data in quotes.

The specified image tag is now used instead of the ID field in LAW to populate theAttachmentRangeBegin and AttachmentRangeEnd fields in the BlueTrace load file.

Imports

Support for UCS-2 and UTF-8 Unicode files has been added to the Import Delimited Textfeature.

When a load file import is initiated, IPRO, Opticon and Summation (@I and @V) volumesare now automatically detected if the image volume is either the folder containing theload file or its parent. If the volume folder cannot be automatically detected, LAW willprompt to select the folder manually, which was the default behavior in previousversions.

Version 5.5.07

New Features

Batch/Export

An option to "Calculate total pages in batch/export dialogs" has been added to Tools >Options > Preferences. This option can be used to disable the calculation of page countswhen launching the Batch Process and Export Utility dialogs to avoid delays in caseswith a large number of pages. A "Calculate total documents" option has been added tothe Select Folders dialog for this purpose as well. The number of folders to be processedwill now be displayed when choosing folders from the Select Folders dialog.

Create Outlook PST

Outlook PST files can now be created (or appended) from LAW for messages in Outlookmail stores, loose Outlook messages (*.msg), and loose RFC-822 (*.eml) messages ondisk. The "Create Outlook PST" feature is located in the Tools menu in the standalonegrid. Note: When creating a mail store, only top-level messages and loose e-mail itemswill be added (any attachments will be part of the parent items). Also, the mail storesand any loose messages must be in their original locations from which they wereprocessed by the ED loader or they will not be found.

Deduplication

A new setting, "Include attachment hashes in e-mail metadata hash", has been addedto the ED Loader Deduplication settings. When enabled, e-mail attachment hashes willbe included in the hash for e-mail records as opposed to the attachment file namehashes only which is used in previous versions and when this setting is disabled.

ED Loader

Using the new archive option, "Include Embedded Archive" located in the Archivessettings, the ED Loader will now create a record for the archive file itself (in addition toits contents) when an archive attached to another file is encountered.

Improved support for digitally signed S/MIME e-mails and introduced support forencrypted S/MIME e-mails.

A "Preserve X.400 addresses" setting has been added to the E-Mail settings. When

Page 13: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

Release Notes 13

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

enabled, the ED Loader will not convert X.400 addresses to an auto-generated SMTPaddresses.

Exports

A "Link to images and files in current location" setting has been added to the Introspectconfiguration settings. When enabled, the images and files associated with exportedrecords will not be copied to the export path and the load file will reference the existingfiles in LAW. Note: When using this setting, images MUST be in multi-page format in theLAW case in order for Introspect to view all pages of the images. Also the IDX load filewill always be written to the image path of the case so relative paths to the documentscan be used (required by Introspect) and named according to the batch name asconfigured in the Introspect settings. A shortcut to the load file will be created in theexport path referencing the load file in the image directory of the case.

Grid Displays

A "Doc/Page Totals" setting has been added to the View menu in the standalone grid.When enabled, the total number of documents and pages will be displayed in the lowerright corner of the grid for the current record set. This setting also determines whetherthe document and page totals are displayed in the embedded grid.

Three options have been added to the grid displays: "Shrink Column toWindow" (shrinks column so the right edge is accessible in the window), "Send ColumnLeft-most" (moves current column to the first position in the grid), and "Send ColumnRight-most" (moves column to the last, or right-most, position in the grid).

Index Fields

Four new fields will now be created when a case is ED-enabled: DateAppStart,TimeAppStart, DateAppEnd, and TimeAppEnd. These fields will capture appointment startand end dates/times during ED Loader imports.

Log Viewer

Records can now be tagged directly from the Log Viewer in LAW. A drop-down list in theviewer will display existing tag fields. The "Tag All Records" and "Tag Selected Records"can then be used to tag desired records within the Log Viewer.

Management Console

The LAW Management Console ("LMC") will now support the use of more than oneinstance of SQL Server when managing and configuring distributed batch processingjobs.

Printing

When batch printing from LAW, the jobs sent to the print spooler will now be named inthe format of "LAW Batch 000000" followed by the DocID, BegDoc#, or ID for thedocument (whichever is found first in that order). Native files will be sent to the spoolerwith their original file names.

Review

Lotus Notes and Outlook top-level e-mail messages can now be launched in their nativeapplications by enabling the "Review Parent E-Mails Natively" setting (Open File menu)or by right-clicking the hyperlink above the image viewer and choosing "Open Source E-Mail Natively."

Searching

Hit highlighting for full text searches has been implemented. The highlighted hits aredisplayed automatically following a search in a new text pane attached to thestandalone grid. The position of the text pane may be changed by selecting Left, Right,

Page 14: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

LAW PreDiscovery14

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

or Bottom from the standalone grid View menu.

An option to "Include hits by word in search results" has been added to the full textsearch options. When enabled, a column (ft_HitsByWord) will be included in the gridcontaining the hit value(s) and the number of hits for each search term. This field isavailable during the current grid session only. To preserve the hits permanently, use thePersist Text Hits feature located under the Tools menu in the standalone grid. Thisfeature will place text hits into a user-defined memo field, separated by semi-colons. Hitcounts are not retained in this field. Unique values will be appended to existing entrieseach time the feature is used.

Separator Pages

A "Print separator pages only" setting has been added for the E-Print batch process.When enabled, LAW will print the separator pages for the selected records and will notprint the actual documents.

A "Show comments field" setting has been added to the Separator Page Options dialogto show or hide the Comments field that may appear on separator pages andplaceholders. The text that appears in this Comments field can also be modified byentering desired text in the "Unsupported file type message" text box. These newadditions apply only to the Custom template for the TIFF Conversion and E-Print batchprocesses.

Folder-level separator pages may now be included in standard print jobs (Print batchprocess) by enabling the "Print folder break separator pages" setting in the Batch PrintOptions dialog.

The "Selected Fields" area in the Separator Page Options dialog has been changed to agrid display and now contains a "Display As" column for specifying an alternate displayname for fields included on custom separator pages and placeholders.

Field names can be hidden on separator pages and placeholders when the field doesnot contain data for any given document. This behavior can be enabled by selecting the"Do not print field names for blank values" setting in the Separator Page Options dialog.

Text Indexing

An option to "Reset Fulltext Flags" has been added to the Tools menu in the standalonegrid. This option can be used to updated the full text indexing flag for the entire case orjust a record set.

TIFF Conversion

Documents that are converted to TIFF images manually (launching the native from LAWand printing to one of the supported image printers) will now receive a value of "ManualTIFF Conversion" in the PageSource field. Previously, these records would receive avalue of "TIFF Conversion", but that value is now reserved for records converted during a batch TIFF Conversion.

The "Reduce to optimal palette" and "Drop blank pages" settings are now supportedwhen manually converting files to TIFF images in LAW using the LexisNexis Image Driver5.0. In order to use these settings, be sure they are selected in the Batch Process TIFFOutput options prior to launching and converting native files.

TIFF/E-Print

A new Excel option has been added to "Limit output to <N> pages" when printing. Whenenabled, LAW will only print the number of pages specified in this field when a file isprinted or converted to TIFF with Excel. A warning message will be logged to theErrorMsg field when the pages are limited as a result of this setting or if the total pagecount happens to match the value set in the options.

Page 15: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

Release Notes 15

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

Modifications

ED Loader

The ED Loader will remain active when the connection to the SQL database has beenlost and a notification will be displayed in the Progress dialog when this loss ofconnectivity occurs. Processing will resume once the connection is reestablished; otherwise, the process can be manually cancelled by the user.

The "Filesize" for Lotus Notes e-mail will now match the size of the HTM file createdduring the import. In previous versions, the size value reported by the Lotus Notes APIwas being used which was typically larger than the file after the conversion to HTML.

Soft returns are now removed from the following fields during import: Author, Subject,Title, and ApplicationName.

Files identified as 1262 (Internet message MIME) with an MHT extension will now beassigned as file type 1910 (MHTML web archive) to prevent conversion to e-mail.

File engine

An updated version of the file engine is included with this release. After installing theupdate and launching ED Loader, a prompt will appear to update the file type database.

Grid Display

Copying and pasting from column to column is now supported in the embedded gridview.

Licensing

Added license reconnect attempts for the batch, import, and export processes in theevent the connection to the license key is dropped due to connectivity or other issues.

Numbering

Page-level batch numbering process was modified to significantly increase performancefor SQL cases.

Searching

Null values are now returned when utilizing the "Does Not Contain" or "Does Not Equal"operator in a database search. The "Tag (Boolean)" field type was not included in thismodification.

Full text only searches can now be saved in the Query Builder.

Separator Pages

The 'Use same fields for all placeholders' option has been renamed to 'Synchronize fieldsettings for all types' and the behavior has changed to include all settings in the fieldssection.

Text Extraction

Updated dtSearch engine to version 7.62. Release notes for this version may be viewedhere: http://www.dtsearch.com/ReleaseNotes762.html.

TIFF Conversion

Documents receiving a placeholder due to being "unsupported" for conversion or due toan error occurring will now receive a "P" value in the TiffStatus field. If placeholders werenot enabled, these documents would receive the traditional TiffStatus values.

Page 16: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

LAW PreDiscovery16

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

Version 5.4.13

New Features

Compound Documents

Extraction of embedded files is now supported for Office 2007 files.

Extraction of attachments/embedded files is now supported for PDF files.

Document Numbering

A new option, "Allow page level numbering to span across sections", has been added tothe Numbering tab in Tools>Options. When this sub-option of "Use rolling numericsections" is disabled, LAW will not allow the page-level section of a number to spanacross one or more sections. Please see the Coding>Numbering Documents/Pages Helptopic for more information.

Exports

Login information can be specified when exporting to a secure Concordance database.The "Security" button is located in the Concordance Direct DCB configuration options inthe Export Utility and is used to enter a user name and password. This feature will bedisabled if the version of Concordance installed does not support this feature (i.e.version 7.3).

An "Allow Unicode data" setting has been added to the Concordance exportconfiguration settings. This setting will create Unicode load files that can only be loadedcorrectly with Concordance 10. Support for version 10 of Concordance has also beenapplied to the Concordance Direct DCB export. In order to create a version 10 databasewhen multiple versions of Concordance are installed, enable the new option "CreateConcordance 10.0 database" in the export configuration settings. Note: This setting willonly be available if Concordance 10 is installed.

An INI setting is now available to allow users to change the @MEDIA Summation tokenvalue from the default "Attachment" to "eMail" for e-mails attached to e-mails. See theExporting > Format-Specific Settings > Summation Help topic for more information.

An error counter and error details grid have been added to the Export Utility statusdialog. Errors can now be viewed during the export process instead of waiting untilcompleting and viewing the log.

Folders

Expand and Collapse commands have been added to the Folder menu.

Index Fields

The ED Loader will now extract the "last accessed" date and time for documents andstore the results in the DateAccessed and TimeAccessed fields. These two fields areautomatically created in new ED cases, but must be manually created in existing cases ifthese fields are required. Note: This timestamp is updated in Windows with mostoperations (ie. dragging a file into ED loader source list, viewing file properties, etc.), soit is generally useless UNLESS the use of this field by the Windows shell is disabled. Aregistry script (DisableLastAccessUpdate.reg) is included in the application path that willdisable updates to this field by Windows (requires reboot after running) and should berun prior to running any new ED sessions if this metadata is required.

Licensing

LAW license modules may now be released or acquired from the Help > About > Licensesform, eliminating the need to first close LAW, launch the Profile Manager, and re-select

Page 17: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

Release Notes 17

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

licenses.

Management Console

A Licenses node has been added to the LAW Management Console ("LMC") to allowtracking of license usage for machines connected to the same SQL Server and the LMC.All attached LAW server keys will be displayed along with license details including totallicenses, available licenses, licenses in use, and machine and user names using thoselicenses.

Printing

A "Reveal Hidden Text" option has been added to the Word options. When enabled, thisfeature will reveal text in the output TIFF or hard copy that is not otherwise visible dueto the text matching the background color (i.e., white text on a white background) ortext matching the highlight color in the source document.

Profiles

The location for global profiles, currently the \Law50\Shared folder, may be changed byentering a new path on the Preferences tab in Tools>Options. This preference is labeled"Global storage path for index field profiles, grid views, and saved filters."

Run Command

A new run command, "Populate RecordType Values", is included in the Commands folderand can be executed from Tools>Run Command. This command can be used to populatean existing field in an ED-enabled LAW case with values to indicate the type of record,such as E-MAIL or E-DOC. These values will match the values used for the <RecordType>field available only in the Export Utility, so running this command is only necessary if youwish to have the field populated in the case for reasons other than exporting.

A new run command, "Text Path Extractor", is included in the Commands folder and canbe executed from Tools>Run Command. This command can be used to populate anexisting field in an ED-enabled LAW case with the path to the active text file (extracted,printed, or OCR), as specified in the utility. This command can be used in conjunction withEquivio to offer near duplicate detection in a LAW case.

Separator Pages

A "Separator Page Options" dialog has been added for the E-Print and Print processesand contains field selection and other options to customize separator pages. Thisfeature is also available in the batch TIFF Conversion options to allow customplaceholders for excluded/unsupported documents and documents that received anerror during the conversion. Please see the Help file topic Batch Processing > SeparatorPages for information on this feature.

A "Print separator pages only" setting has been added for the Print batch process(standard image print only). When enabled, LAW will print the separator pages for theselected records and will not print the actual documents.

Text Indexing

The indexing process can now be run in the background, referred to as auto-indexmode. When running the indexer in this mode, the indexer will continue to poll thedatabase for new documents to index until it is cancelled. This allows you to indexdocuments during the import process, so that when an ED loader session is complete,the documents are indexed and ready to be searched. Auto-index mode can be enabledon the new index options tab.

An "Indexing" tab has been added to Tools > Options and contains a number of optionsfor handling of words and punctuation during the full text indexing process.

Page 18: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

LAW PreDiscovery18

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

Modifications

Administration

SQL connection retry was added to account for dropped connections that may occurwhen deleting a large number of records.

ED Loader

Outlook "out of office" replies will now be saved as HTML files instead of MSG if the e-mail output format is set to HTML in the ED Loader e-mail settings.

Metadata extraction for PDF files has been optimized to increase speed and extractcertain types of encrypted metadata that were previously not supported.

LAW's main interface is now hidden when the ED Loader is launched.

Exports

The default delimiters, when launching LAW for the first time on a machine, forConcordance exports are now set to the Concordance default delimiters rather than thecomma (,) and quote (") characters.

Records exported to a path or with a file name that exceeds 255 characters will beplaced in an $Invalid_Paths folder in the root of the volume folder.

The "Create as new database" and "Append to existing database" options have beenremoved from the Concordance Direct (DCB) configuration settings as they areredundant. LAW will create as new if the export path does not contain an existing DCBand will append if the export path does contain an existing DCB.

The BlueTrace export format now uses the DocID field values for the ControlBegin andControlEnd values.

Imports

Both single-page and multi-page image files imported into LAW via load file will be storedin <case root>\$Image Archive. This applies to all load file imports except Z-Print.

Page Count Extraction

Accuracy on PDF page count summaries has been improved.

Printing

Improved performance when printing electronic documents using Microsoft Word (allversions).

Text Indexing

The full text indexing process has been modified to greatly enhance speed and stability.

Obsolete document detection and compression have been added for the full textdictionary. When documents are deleted from the index, or re-indexed, obsoletedocuments remain in the index until the index is compressed. These documents do notcome back in searches but do remain in the full text dictionary. When obsoletedocuments are detected, a banner will appear in the full text dictionary to notify andprovide a compress option.

The full text indexing process is now supported for all case types (no longer limited to EDcases).

TIFF Conversion

Page 19: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

Release Notes 19

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

PageColor is now populated automatically for images affected by the "Treat native TIFF

images as image for record" setting. The Update Page Data was needed previously inorder to populate the field for these types of records.

Watermarks

Watermarks applied during the endorse and print processes now support non-binary

images without loss of content when applied to B&W images.

Version 5.3.14

New Features

Exports

A "JPEG subsampling" option has been added to the Options tab in the Export Utility toallow potential improvement of the image quality for JPEG files. Values include: 1:1:1 (nosubsampling, 2:1:1 (2 to 1 horz), 4:1:1 (4 to 1 horz and vert, and 2:1:1 (2 to 1 vert).Note: These values may be referred to differently in other applications when viewing theimage properties. For example, 2:1:1 (2 to 1 horz) may be listed as 4:2:2 outside ofLAW.

Log Viewer

A "Save As" button has been added to the Log Viewer (Tools menu) to allow saving oferror logs to a *.CSV file directly from the viewer.

Management Console

The LAW Management Console ("LMC") is now included with LAW PreDiscovery. The LMCcan be used to manage distributed batch processing jobs and to automatically join LAWworkstations to those shared jobs. During processing, stations will report their progresson the batches and users can view this information from a single location. The consolecan be launched and added to Windows startup, if desired, by launching the Optionsdialog within LAW (Tools>Options), viewing the Preferences tab, and checking the box to"Start the Management Console on Windows startup." Please see the Help file or UserGuide for more information.

Profile Manager

The two system profiles in the Profile Manager, <Any Available Licenses> and <Custom>,can now be hidden to assist with easier management of license usage. Users must be inadministrative mode in order to hide or restore these profiles.

Profiles

Global profiles and search filters may now be created for the grid displays, Index display,and Query Builder. Shared profile support has also been added for index profiles. A"Field Profiles" button has been added to the Modify Fields dialog (Index menu) whichallows the selection and management of the profiles. Also, the "Add New Profile" buttonhas been removed and replaced by "Save" and "Save As" buttons. Global profiles andsearches can be created, saved, and used across all LAW cases; commonly used profilesand queries will no longer need to be created in each case. Please see the Help file orUser Guide for more information.

Modifications

Page 20: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

LAW PreDiscovery20

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

Exports

Color pages can now be resaved during the export process as JPEG files when exportinga serialized image containing color pages to a single-page format using "Default" as theOutput Format. In order for this to occur, the PageColor field must be populated. This isnow automatically set for documents converted to TIFF in LAW 5.3.14 or later. If theimages were imported from another application, the 'Update Page Data' batch processwill need to be run on the images to populate the PageColor field.

Printing

If LAW is unable to locate the notes.ini file in the Lotus Notes installation path, LAW willnow look for the notes.ini file location in the registry. This change will prevent thefollowing error from occurring when attempting to initialize a batch process with the"Print Lotus Notes e-mails natively from Lotus" option enabled: <Error> = The LotusNotes configuration file (notes.ini) was not found, unable to verify recipient expansion(ErrCode=53, Line=170) (-1)

LAW will now only support version 2009 of E-Drawings for use as a print sourceapplication. If 2008 is installed, an error will be logged for any records with E-Drawingsas a source application (An installation of eDrawings 2009 was not found.). Werecommend uninstalling 2008 prior to installing version 2009 to avoid potentialcomplications with this application when printing in LAW.

Version 5.3.08

New Features

Document Numbering

The "Use rolling numeric sections" option has been added to the Numbering tab in Tools->Options. This feature may be used to alter the way LAW increments when a particularvalue in a numbering scheme has been reached (i.e. 001.9999 increments to 002.0001).Please see the Help topic Coding->Numbering Documents/Pages for more information.

Exports

The "EDRM XML 1.0" format has been added to the list of available export formats in theExport Utility.

New Ringtail configuration setting, "Include reference to native file in Pages table", hasbeen added. The state of this setting will determine how files are viewed upon importinto Ringtail.

Two new settings have been added to the "Custom" folder naming dialog in the ExportUtility: "Split folder(s) on custom delimiter" and "Drop last folder level." These settingsallow additional configuration when using index field values to build the folder structureupon exporting.

Imports

The setting, Link to source files in place when importing load files, has been added tothe Preferences tab in Tools->Options. When enabled, LAW will link to the source filesoutside of LAW when importing load files rather than copying the files to case folderstructure.

Page 21: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

Release Notes 21

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

LAW will now retain images in single-page format when importing load files. Note: All

imported images, regardless of page format, are now saved to the $Image Archive folderduring the import process. In previous versions, the images were merged into multi-page files (if serialized) and stored in the folder structure displayed in LAW's maininterface.

An additional image printer, "LexisNexis Image Driver 5.0 (300 DPI)", is now included in

the full installation. This image printer will create 300 DPI images ONLY to account for theDPI changing when certain Microsoft Excel files are encountered. If a different DPIsetting is required, please use the original LexisNexis Image Driver.

Modifications

Exports

The "BCC" field is now included in the Parties table in the Ringtail MDB load file rather

than the Export_Extras table when chosen as a selected field.

Image Manipulation

The Insert Existing Page feature now supports the combining of mixed image formats in

a single serialized scanned document. For example, a two-page document could containone TIF page and one JPG page.

Import Tag List

LAW will now prompt to apply the "Indexed" property to the selected Document ID field

if not already indexed. Applying this property can significantly increase import speeds inlarger cases.

Installer

The warning message to remove dongles (hardware keys) during the Sentinel install

portion of the LAW full installation process has been removed. The vendor providingthese keys has confirmed no issues will occur when installing this service while a key isattached to the system.

LAW will now perform a check during updates to ensure the version being installed is

supported under the maintenance contract linked to the dongle (hardware key). If thekey cannot be reached during the install, LAW will prompt for the key number (i.e. N10-XXXX). A warning message will appear if the version should not be installed. This check isto prevent users from installing a version they will not be able to run due to an expiredcontract.

OCR

The setting, "Create web optimized PDF", has been added to the OCR tab in Tools->Options.

A new version of the Expervision OCR engine (7.1.157.1124) is included. This version

resolves issues with the "web optimized PDF" setting causing corrupt PDFs to becreated, improves OCR accuracy on complex images, and addresses several conditionsthat could cause the OCR engine to hang or crash.

Text Extraction

A new version of dtSearch, 7.60.7728.1, is included. This version resolves the following

two issues: 1) The "*" (asterisk) character was being converted to a UTF-8 version ofthe character in some cases, and 2) The words "true" and "false" were not being

Page 22: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

LAW PreDiscovery22

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

included in the text extracted from Excel files.

TIFF Conversion

The option to bypass TIFF conversion on native images has been changed to "Treatnative TIFF images as image for record (bypass TIFF Conversion)" and only applies toTIFF images (file IDs 321, 298, and 146) by default to account for issues when endorsingextremely small image files, such as 2x2 JPGs. An INI setting is available to addadditional image file types. Please see the Help section Batch Processing->E-Print/TIFFConversion->E-Print/TIFF Output Settings for more information.

User Interface

A "Numbering" tab has been added to the Options form under the Tools menu. Thefollowing options have been moved from Preferences to this tab: Use document/levelseparator for Page IDs, Use alpha-numeric bates numbering, and Use document levelattachment numbering.

Version 5.2.42

New Features

ED Loader

A new output setting, HTML/MHTML, has been added for Outlook e-mail conversions. Thissetting will force MHTML output for any e-mails with RTF content, HTML messages withembedded images, or non-email items. Standard text or HTML messages will be savedas HTML.

Imports

The EDRM XML 1.0 specification has been added to list of available imports. This providessupport for import of electronic discovery that has already been processed outside ofLAW.

TIFF Conversion

Native images can now be skipped during TIFF conversion so that the original TIFF imagefile becomes the working image in LAW. This behavior can be toggled from the TIFFOutput options. If desired, the TIFF conversion settings can still be forced on the nativeimage bypassing the TIFF print process for improved performance.

Modifications

Admin

Error message returned on SQL case creation failures has been updated with additionalinformation.

ED Loader

Attachment extraction was enhanced to support office documents with attachmentssaved as e-mail attachment streams.

Caching on folder table lookups was improved to reduce SQL traffic during imports.

Page 23: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

Release Notes 23

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

OCR

Web optimization for PDF output has been disabled due to potential corruption on largeimages. Web optimization can now be enabled with an ini setting if desired.

User Interface

Folder view control was updated to improve performance on folder refreshes. Theupdated folder view also respects Vista folder themes.

Version 5.2.37

New Features

ED Loader

The dtSearch engine is now used to extract metadata for PDF files.

Scan for Errors

Automatic retries have been added to a number of areas when scanning for invalidimages in an attempt to address high traffic networks that suffer from unusually highnumbers of dropped SQL Server connections.

Modifications

Run Command

A new run command (Tools -> Run Command) is included to re-extract all PDF metadatafor a case using the dtSearch engine. The command is named 'PDF Metadata Extractor'.It will re-extract metadata for all PDF files in the current case logging any changes itmakes to a field.

Version 5.2.36

New Features

Document Numbering

Field codes, such as &[DocID] may now be used in the Starting # field when numbering adocument- or page-level index field. This applies to Edit->Auto Number as well as theDocument Numbering batch process. For example, "&[Page] of &[Pages]" (without thequotes) would result in the text "1 of 20" in the selected target field. Please see theCoding->Numbering Documents/Pages topic in the Help file for a list of possible values.This feature is not currently supported when the "Use document level attachmentnumbering" setting is enabled (see #2 in New Features for a description).

A new setting, "Use document level attachment numbering", has been added to theTools->Options->Preferences tab. When enabled, LAW will append a suffix in the formatof [<attach number>-<total # of attachments>] to the specified Starting # whennumbering a document level index field. This applies to Edit->Auto Number as well as theDocument Numbering batch process. Please see the Coding->Numbering Documents/Pages topic in the Help file for more information.

ED Loader

Page 24: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

LAW PreDiscovery24

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

Metadata extraction is now fully supported for Office 2007 (binary and OpenXML only)

and OpenOffice documents.

Exports

Native file exports are now supported for the Delimited Text export format. The *.CSVload file will now include a "NativeFile" field for ED records and will contain a path to theexported native file.

Page Count Extraction

LAW now 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 ED Loader. Thisfeature may be accessed in the standalone grid by clicking Tools->Extract ED PageCounts). Page count estimates will be stored in the EDPages field for each record.Please see the Working with Native Documents->Extracting Page Counts topic in theHelp file for more information. Also, these estimates will now be displayed in the fourtypes of reports LAW generates for ED records (Tools->ED Reports in the standalonegrid display).

Query Builder

A new setting, "Use NOLOCK setting to improve performance (SQL only/read-only)", has

been added to the Advanced tab in the Database Query Builder. This setting was addedto prevent locking of records in SQL cases while a query is being executed. This shouldnot be a concern in smaller LAW cases. Please see the Searching->Query Builder topic inthe Help file for a complete description.

Modifications

Annotations

Annotations may now be merged to serialized image files.

Control List

The Build Control List feature in the standalone grid will now include printed text when

available.

ED Loader

To prevent misidentification and therefore mishandling of e-mail, EML and MSG files will

always be sent through LAW's e-mail processor. If the file is truly not an e-mail, awarning will be logged and the file will be handled as an e-document.

Exports

CC and BCC have been added to the list of available eDii tokens in the Summationexport settings.

Image Manipulation

ED image records (records imported via ED Loader and converted to TIFF in LAW) may

now be split and merged. When splitting, the user can choose from three differentmetadata retention options and will have the ability to apply an auto-incrementing suffixto DocID's for records created as a result of the split. Please see the ManipulatingDocuments->Splitting Documents topic in the Help file for more information.

OCR

Page 25: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

Release Notes 25

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

New version of the Expervision OCR engine is included. The new version should be listed

as 7.1.135.515 in the OCR tab in Tools->Options. This version of Expervision will createweb-optimized PDF files when the OCR output format is set to one of the Adobe PDFoptions.

Version 5.2.27

New Features

ED Loader

Additional archive formats are now supported which include: TAR (*.tar), GZIP (*.gz; *.gzip; *.__z), and Z (*.z).

Outlook messages can now be converted to HTML, MHTML, MSG, or RTF during import.The format can be specified with the 'Save Outlook messages as' setting in the E-mailsettings section of the ED Loader.

Embedded files/attachments will now be extracted from PowerPoint files in addition toother Office documents if the 'Enable Compound Document Extraction' setting is enabledduring imports.

Unicode metadata extraction is now supported for PDF files.

TIFF/E-Print

The source application "eDrawings Viewer" is now supported to provide improvedsupport for printing CAD files (*.dwg, *.dwf, *.dxf, plus many more). See http://www.edrawingsviewer.com/pages/products/eDrawingsViewerpage.html for details. **Note:The "Image Printer" source application now supports printing DWG/DWF files natively,and is the recommended and new default source for these file types.

The source application "AutoVue Suite" is now supported as an alternative sourceapplication to Quick View Plus and supports over 450 file types. See http://www.cimmetry.com/_products/autovue_office.html for details. AutoVue can be set as thedefault native viewer if desired by checking the "AutoVue Suite Review Mode" menu itemfrom the "Open File" button above the main document viewer.

Modifications

Import

Significant performance enhancements have been made to the LAW 5.x case importfunction.

Index Fields

The following fields have been added to the ED case template: LastAuthor,ApplicationName, and Template.

OCR Flags

Performance improvements have been made to reduce the amount of time required toreset OCR flags in large cases.

TIFF/E-Print

Page 26: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

LAW PreDiscovery26

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

The "Image Printer" source application now supports printing DWG/DWF files natively,

and is the recommended and new default source for these file types.

Version 5.2.13

New Features

ED Loader

The ED Loader has been modified to support the import of folders and files containingUnicode in the path(s) and the viewing of Unicode characters in the interface. This issupported in new LAW cases only (created in this version or later). Please see the Helpfile topic Appendix->Unicode Support for more information regarding Unicode in LAW.

Exports

Additional text option, Printed, has been added to the text options (Formats/Documentstab) in the Export Utility to allow this type to be exported. This type of text may beoptionally created during a batch TIFF Conversion or single document TIFF conversionwhen using the LexisNexis Image Driver. In addition to OCR, printed text may beexported single-page. Please note, not all export formats support single-page text.

If Unicode data exists in any exported index fields, it will now be included in theCaseLogistix load file when this export format is selected. Optionally, Unicode data mayalso be included when exporting to the Delimited Text export. The setting, Allow Unicodedata, is located in the Configuration settings for Delimited Text.

Grid Displays

While viewing data in either of the grid displays, any Unicode data existing in a field maybe viewed within the grid by floating the mouse pointer above the cell. The Unicode datawill appear in a pop-up text box beside the cell.

Unicode data in index fields can be included when saving records from the grid displaysby selecting the "Unicode Text" option in the "Save as type" drop-down.

Licensing

LAWtsi licenses may now be undocked from the LAW server key.

Pixel Image Library

Pixel Image Library version 8.0 (Build 4727) is now shipped with the full install forversions 5.2.05 and later of LAW PreDiscovery. This version will prevent an issue withimages appearing pink after imports into LAW.

Printers

The LexisNexis Image Driver 5.0, based on the Zan Image Printer, is now included ininstallations of LAW. This image printer may be used to convert native files to TIFFimages using the batch TIFF Conversion process and single document TIFF conversionfeature.

Scanning

Scanned images may now be stored in serialized (single-page) format. When using thisstorage schema, resulting images will be stored in the $Image Archive folder located inthe root of the case folder. To choose between serialized and multi-page, click Tools->Options and select the desired "Storage Schema" on the Imaging tab.

Text Display

Page 27: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

Release Notes 27

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

When more than one type of text exists for a record, the type of text displayed in the

viewer on the main form may be selected by right-clicking in the viewer and choosingone of the three new options: Open Text (OCR), Open Text (Extracted), Open Text(Printed). All available text states will be enabled. Once a text state has been manuallyselected by the user, it will be checked and become the default text state.

Text Extraction

Text may now be extracted during the batch TIFF Conversion process and single

document TIFF conversion feature when using the LexisNexis Image Driver (installedwith versions 5.2 and later). The option to enable this feature, "Save text with images",is located in TIFF Options->TIFF Output in the Batch Processing dialog. This type of text,referred to as 'Printed' text, will be stored with the TIFF output below the <caseroot>\$Image Archive folder.

User Interface

The LAW PreDiscovery interface has been modified to support the viewing of Unicode

data within the application. The standalone and embedded grid displays do not currentlysupport Unicode, but a pop-up text box to display this type of data will appear when themouse pointer is positioned over a cell containing Unicode. This is supported in new LAWcases only (created in 5.2 or later). Please see the Help file topic Appendix->UnicodeSupport for more information regarding Unicode in LAW.

Windows Vista

Windows Vista has been added as a supported operating system for LAW. Please see

the notes regarding Vista support in the System Requirements topic in the Help file.

Modifications

Documentation

Help->Quick Start Guide has been changed to Help->User Guide. This menu item will

launch the new user guide included with LAW installations and will be located in \Law50\LAW PreDiscovery User Guide.pdf. The Quick Start Guide has been removed due tooutdated content.

ED Loader

New version of the file recognition engine, used to identify file types during ED Loader

imports, has been implemented. A prompt to update the file type database with changeswill appear when the ED Loader is initially launched after installing this version. Thisupdated version will correct a number of e-mail recognition issues.

The menu item, Tools->Open Summary Database, has been moved and changed to File-

>Open Summary. Additional menu items and button labels have changed in the EDLoader interface, but all items perform the same functions as previous versions.

Exports

The default image component used to manipulate images during the export process has

changed to use Pegasus image libraries. This change was made to prevent common'Assertion failures' from occurring and causing problems with the export process. A newoption, 'Use Pegasus Image Library', has been added to the Options tab of the ExportUtility to control which image component is used. To revert back to the older PixelTranslations libraries for any reason, uncheck this new setting. NOTE: If performingmultipage PDF exports, the Pegasus setting will be ignored.

Page 28: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

LAW PreDiscovery28

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

The NativeFile field will now only appear in Concordance DAT load files once to avoid

issues when loading into Concordance. This field appears by default in the DAT andwould previously appear twice when the field was also selected manually in the Fieldstab.

Summation export has been modified to force the @T to appear below @PST and@StoreID tokens in the DII load file to avoid potential problems when loading intoSummation.

User-defined page-level fields may now be selected as the File Naming Scheme and

Image Tag when exporting.

Grid Displays

Page-level fields set as visible in the grid view will now reappear as visible columns thenext time a page-level query is executed.

Index Display

Page-level fields are now locked on the main form Index Display. The only way to

populate these fields currently is using the Import Tag List and Bates Numbering/Auto-numbering features.

OCR

New version of the Expervision OCR engine is included. The new version should be listed

as 7.1.120.309 in the OCR tab in Tools->Options.

The OCRStatus field value is now set to 'Y' after a document has been re-converted to

TIFF provided the previous status was not 'N'. This will help users determine whichdocuments are in need of OCR if using this feature.

Printers

The Informatik Image Driver is no longer packaged in the full installation file; however,

this image printer may still be used for TIFF conversion in LAW.

TIFF Conversion

When utilizing the single document TIFF conversion feature, documents may now be

converted to serialized format and will be saved to the $Image Archive folder to remainconsistent with batch TIFF conversions. Printed text is also now supported with thisfeature by enabling the option prior to the conversion. The desired image format andtext options should be set in the Batch Processing TIFF Output options prior to using thisfeature.

Version 5.2.19

New Features

ED Loader

An error/warning will now be logged by default when importing Lotus e-mails if an e-mailcontains an RTF body. These warnings can be disabled if user decides they do not wantthem. The logging is enabled by default, so it will require manual user intervention todisable them. To do this, a new setting has been added to the E-Mail section of the EDLoader. To disable the warnings, uncheck the 'Log warning messages for e-mailscontaining RTF body content'.

Index Fields

Page 29: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

Release Notes 29

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

New page-level system fields have been added to track the source, color, and size of

scanned or imported images and images created during TIFF conversions in LAW:PageColor, PageSource, PageSize, PageWidth, PageHeight. A new batch process,Update Page Data, has also been added to populate the color and size of importedimages, as this information is not pulled during the actual import. All 5 fields arepopulated for scanned pages at the time they are scanned.

TIFF Conversion

Support for the Zan Image Printer (http://www.zan1011.com) for TIFF conversion hasbeen added. If this printer is installed, it will be available in the list of available driversfor TIFF conversion in the TIFF Output options. **Note: The retail version of this driverwill install 2 different printers, one for B&W and one for color. Either printer can beselected as the active driver. LAW will set the color format automatically based on thesettings configured in the TIFF Output settings.

Modifications

ED Loader

The text extraction process has been modified to produce cleaner text extraction results

during ED imports. Text from embedded files/attachments is no longer included in thetext of the parent for MS Office documents. The extracted text is also screened againstknown binary formats that would typically result in large amounts of binary data or"garbage" text, and if these one of these types is detected, the text will be ignored anda warning logged. **Note: Screening for known binary formats is disabled if the 'Enablebinary scanning in text extraction' setting is enabled.

Exports

When exporting to Concordance DCB, a new DCB will be created in each partition to

address an issue with linking to native files in the Concordance database. A new optionhas been added to the Concordance DCB export options, 'Concatenate DCB's acrossseparate partitions', to allow users to treat all DCB's in the partitions as one DCB.

Full text Search

Full text searches have been optimized to reduce the amount of time required to return

results.

Version 5.1.11

New Features

There are no new features in this release.

Modifications

Z-Print Import

Z-Print load files may now be imported into an end-enabled case. The Custodian field willbe mapped to the existing Custodian lookup field and RecordType values will be mapped

Page 30: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

LAW PreDiscovery30

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

to the existing _DocCat field. Imported records may use LAW's EDD features, such asTIFF Conversion and native file exports.

Version 5.1.05

New Features

Batch Process

Pause button added to Batch Process status dialog.

Deduplication

Addition of deduplication utility accessible via Tools->Deduplication Utility from the mainform. This utility is intended to replace deduplication as a batch process. Thededuplication utility offers a status for viewing deduplication information in the currentcase as well as built in filters for deduplicating only untested items and selectedcustodian(s). The deduplication utility is intended to optimize the deduplication processproviding greater control, faster speed, and increased flexibility for futureenhancements.

ED Loader

Pre-process summary function has been added to the ED Loader. This feature is used tocollect a high level inventory of sources placed in the queue for reporting and reviewingpurposes. The new options are located under the Tools menu in the ED Loader(Summarize Queue and Open Summary Database).

Three new insert modes for e-documents have been added: Edit->Insert->E-Document(s)->After Current, Edit->Insert->E-Document Attachment(s)->Before Current and AfterCurrent. The Before/After current items allow for precise control over the placement ofthe newly inserted documents. The attachment inserts allow for the direct insertion ofnew documents as attachments.

Added support for Exchange public folders and delegate mailboxes in the 'Select OutlookFolder' option.

Exports

Export formats for iCONECT and CaseLogistix are now available.

Predefined system field has been added for ID field in LAW (displayed as "<ID>" in fieldlist).

Summation export now allows customization of included eDii tokens. To configure whichtokens are included, open the Summation export configuration dialog, ensure the optionto 'Allow advanced (iBlaze) dii features' is enabled, and press the [eDii Tokens] button.

The UNICODE text format (UTF8) used for text extracted from e-docs/attachments(UTF16 is used for parent e-mails) can be forced to ANSI during the export process ifdesired. To force this conversion, select the 'Decode UTF8 to ANSI' setting from the textoptions dialog. Because this setting will force all output text to ANSI, it cannot beselected in conjunction with the 'Allow UNICODE in text' setting. **NOTE: This setting isprocessor intensive and will slow down the export process slightly.

UNICODE text can now be retained in exports. To allow UNICODE text output, select the'Allow UNICODE text' setting from the text options dialog.

Grid Display

Page 31: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

Release Notes 31

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

An advanced sort function is now available in the external grid which enables the user to

sort by up to 4 fields with a different sort direction per field. The advanced sort can beaccessed via the Tools->Sort Records->Advanced menu item or a new toolbar buttonlocated directly to the right of the 'Sort Descending' button.

Import LAW Case

File->Import->LAW Case->3.x | 4.x has been changed to File->Import->LAW Case. This

feature has been expanded to support EDD cases and linked images. Please see thehelp file for a list of known issues with this feature.

Online Help

Online help file is now complete and available.

Query Builder

A report can now be generated by custodian for full text hits. The report (HTML) will

display the number of document hits and total hits by custodian for all current full textsearch terms and provide totals by term and by custodian. To generate the report, enterthe search terms to use and select the 'Custodian Report' button.

Full text search terms can now be loaded from file. To do so, select the 'Load Terms'

button.

TIFF Conversion

Printing of TIFF placeholders for documents that error during conversion is now optional

and can be controlled via the 'Print placeholders for documents that error duringconversion' setting.

Support for the latest Peernet TIFF driver (TIFF Image Printer 7.0) has been added. This

driver does not ship with LAW, it must be purchased retail from Peernet (http://www.peernet.com/tiff/index.html).

The Informatik Image Driver now contains color reduction settings to optimize color TIFFs

or reduce to greyscale. Both of new settings will detect pure black and white pages andsave those to Group 4 TIFFs, while allowing further control via the color compressionsetting to choose alternate compression formats for those pages determined to actuallycontain color (JPEG, LZW, Packbits).

"Reduce to black & white' setting has been added to the list of color reduction settings

for the Informatik image printer. NOTE: The use of this setting and other color reductionsettings no longer require any settings on the printer itself to be modified. LAW willautomatically adjust the printer output settings based on the selected color reductionsetting.

TIFF/e-Print

New Excel options are available to print as black & white, remove repeating rows, and

remove repeating columns.

Microsoft Visio has been added as a supported source application for TIFF Conversionand e-Print processes. Supported versions: MS Visio 2003 and higher.

VCF (vCard) files can now use Internet Explorer as a source application when printing to

TIFF or paper.

New source application, Shell Printer, has been added to the SourceApp field in LAW.

When assigned to this source app, files will print through the application assigned tothat particular file type in Windows, provided the application supports command lineprinting.

User Interface

Total Litigator button has been added to the main toolbar in LAW.

Page 32: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

LAW PreDiscovery32

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

Modifications

Batch Process

The watermark endorse/print settings are now retained at the case-level. The recentwatermark list is still shared globally to allow for easy selection of a common watermarkin new cases, but the settings must be manually set for all cases to prevent inadvertentwatermark branding of images.

Document/page counts for each category are no longer calculated until the option isselected to prevent unnecessary delays with extremely large cases.

Control List

The 'Build Control List' feature, located in the standalone grid's Tools menu, has beenmodified to support extracted text in addition to OCR text.

Deduplication

Deduplication is no longer available as a batch process, it must be performed using thenew deduplication available from the main form (Tools -> Deduplication Utility).

ED Loader

Added configuration setting to deactivate generation of .ver files created during imports(File=<App Path>\EDLoader\edloader.app.config.ini, Section=GENERAL_SETTINGS,Key=GENERAL_GenerateVersionStamps, Value=0 or 1 (0=disabled)).

Modified compound document processing to not generate empty records for files thatfailed to be extracted. Instead, the warning is logged on the parent record.

File/folder selection view now displays UNICODE filenames correctly.

Modified 'Session Viewer' to display and give access to all sessions associated with thecase via the 'Show all sessions' option located at the bottom of the dialog. Thispreviously was limited to only sessions initialized by the current workstation to preventinvalid session restarts. The Resume command will only be enabled when a session thatwas initialized by the current workstation is selected.

Read-only attribute on PST files are now automatically cleared (if possible) to allowOutlook to open them.

Embedded Grid

Save menu items in embedded grid have been renamed to match the buttons in thestandalone grid ('Save Selected Records' and 'Save All Records').

Exports

CaseLogistix: SourceType field added to the CLXdata section in the XML load file. Also,the 'datetime' field definition was modified to 'dateTime'.

Exported text for parents and attachments is now merged when exporting using the'Combine Parents/Attachments' option. Previously, only the text of the parent would beexported in this scenario.

When exporting images created in LAW as single page from electronic documents to asingle page format, the re-saving of images is now bypassed if the output format is setto 'Default' and merging of annotations is not enabled. This significantly improves thespeed and stability of exports if these conditions are met.

Page 33: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

Release Notes 33

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

Records for native files skipped during the export process because the native file does

not exist are now logged as warnings. If export logging is enabled, such records will belogged with a status of 'N'.

The single page text setting has been moved to the text options dialog.

Concordance Direct (*.dcb) export now sets the Keyed property to true for all created

TEXT/NUMERIC/DATE fields, and sets the Indexed property to true for all OCR/Full textfields.

DateSent/DateRcvd fields exported to a Summation eDii file are now formatted with thecurrent regional date format.

Inclusion of file extensions for all naming schemes is now enabled by default with all

formats (image, text, native).

Native file paths in Concordance exports now respect the relative/hard/UNC path

options (previously only applied to images and text). If a relative path is used, the pathof the create-hyperlinks.cpl/cpt will be prepended to the path when the hyperlinks arecreated.

The prompt to overwrite or append an existing Opticon load file will now use the same

result that was set for Concordance to prevent prompts in the middle of the exportprocess (when the first image-based record is encountered).

Full text Dictionary

Both Hit Count and Doc Count are now displayed for each term. UNICODE support for

terms was also added.

Image Merge

Merging images that have been imported and linked in place (rather than copied) no

longer modifies the original images on disk. Merging will now create a new image inLAW's default structure. The merge function also now allows the merging of text filesassociated with linked images (also stored in LAW's default structure).

Import Tag List

Default range delimiter has been changed from a '-' (hyphen) to a ':' (colon).

Licensing

Users can now access licenses from more than license key rather than only the 'active'

key. Note: Keys must be hosted on the same machine. Previously, only one key could beset as the active key at any given time and accessed for license checkout.

OCR

Splitting/deskewing of images for the OCR process has been updated to use new imagelibraries. In addition to increasing stability and eliminating assertion failures, it will nowoptimize color images for the OCR process, which can increase the OCR speed for colorimages by 500-600%.

Online Help

Online help can now be viewed from a network share without requiring a patch for

Windows.

Query Builder

Queries on the ‘DupStatus’ field now return NULL values when the ‘Does Not Equal’ or

‘Does Not Contain’ operator is used. For example, if you execute the query, DupStatusDoes Not Equal G, fields with a DupStatus of NULL will now be included in the search.

UNICODE values can now be specified as query conditions for standard database fields.

Page 34: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

LAW PreDiscovery34

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

Added case-wide full text report. This report is accessed the same way as the custodian

full text report that was added in build (h). The output file dialog has been modified toselect the report type, and the query builder has had the command to invoke the reportgenerator changed from 'Custodian Report' to 'Full Text Report'.

The combo box selection for list fields now allows typed text or selecting existing entries.

Scanning

Insert->New Page(s), Insert->Scanned Document, and all Replace options have been

disabled for native records that happen to be images.

Summarize Images

The Summarize Images function has been modified to skip e-docs converted to TIFF toprevent a 'Can't open file' error message that aborts the summary.

TIFF Conversion

Using color reduction settings for Informatik printer no longer requires manually

adjusting the default printer preferences. LAW now automatically matches up the printeroutput format for the specified reduction setting.

Support for the ICE TIFFWriter 6.0 driver has been removed. Support for this printer was

only temporary for testing purposes. The only benefit to using this driver was for theOptimal Palette output setting, which is now available with the Informatik driver thatships with LAW, and is approximately twice as fast as the TIFFWriter in this mode.

User Interface

The thumbnail tab on the main form is no longer present. Thumbnails will now be viewed

by default as part of the main image control with a splitter interface. The image view canbe configured (from the View menu) to display a single page, just thumbnails, or a page/thumbnail combination (default).

The Log Viewer, formerly located in File->Administration, has been moved to the Tools

menu in the main interface.

Using the Edit->Insert->E-Documents functions will now automatically refresh the

current folder after the import.

Administration

The custom command functionality has been extended to allow running of scripts

(VBScript, Javascript), in addition to actual executables.

Version 5.0.31

New Features

There are no new features in this release.

Modifications

ED Loader

Added special handling for e-mails that contain an HTML body, but no corresponding

Page 35: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

Release Notes 35

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

plain text body, which resulted in extracted text without a body.

Compound document extraction (embedded file support) now uses native extraction bydefault.

Empty folders are no longer created in LAW during imports.

Improved e-mail address capture for FROM,CC, and BCC fields. Previously the CC/BCCfields may have only contained names without bracketed e-mail addresses.

Rules for extracting and loading text for 'File Filters' and 'Duplicates' have changed. Thenew rule dictates that if a record is generated in law, then normal text extraction rulesapply, and text will be extracted and loaded even if the native file is not copied. This isapplicable to the 'Include' and 'Partially Exclude' actions associated with 'File Filters' and'Deduplication'.

Exports

Documents in excess of 3600 pages may fail to export if using a single page exportformat with a naming scheme that does not preserve file extensions (i.e.'abc00001.001').

Native and exported text file naming now checks to ensure an existing file is neveroverwritten. This is necessary to prevent output filename conflicts that could be createdby the user during the export, and in the event that the extracted text file name is thesame as the native file name. If a file name conflict is detected, the latter file to bewritten will be named with a copy sequence (i.e. "abc001.txt", "abc001 (Copy 2).txt",etc.)

Summation export will now remove soft returns from the Subject and Headers fields (E-Mail), and any other user-defined fields to prevent problems loading the DII file.

Grid Display

Removed grid position check when loading, as this prohibits setting grid position ondual-monitor systems to a monitor left of the default monitor. If the grid is placed off ofthe screen due to the removal of a monitor from the display, the window must berepositioned from the taskbar to bring it back into view.

TIFF Conversion

Output image resolution for images printed with Excel will now match the specifiedprinter resolution.

Save speeds for single page TIFF conversions have been dramatically improved for largedocuments (500+ pages).

Single document TIFF capture is now available with the TIFF, QC/Edit, or Scan (Unlimitedonly) licenses.

User Interface

Document per folder limit of 32,767 has been removed. **NOTE: This does not indicatean endorsement of putting that many documents in a single folder. Extremely long waitsopening folders may occur when placing that many documents in a single folder.

The DocID/DocExt columns in main document list are no longer visible if the case doesnot contain these fields.

Version 5.0.30

New Features

Page 36: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

LAW PreDiscovery36

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

Exports

New default field, RecordType, has been added for ED enabled cases. This field willidentify the type of record being exported.

Modifications

Administration

Deleting records is now optimized for both image-only and ED-enabled cases.

ED Loader

Modified file extraction behavior to recognize if a file was removed by another process (inmost cases, resident anti-virus software). If a file is otherwise successfully extracted, butis not present then a "[Native File Copy] E: (copy failure) (Virus Warning) The fileappears to have been removed by another process" message will be logged. Theprevious implementation logged anywhere from 4 to 6 separate warnings when a filethat otherwise successfully extracted, was removed from the system.

Exports

The direct Concordance export has been modified to always use DDE for populatingdata, which should improve stability on large paragraph (i.e. OCR/extracted text) fields.Support for embedded text over the field size limit (~8MB in Concordance 7.0 and ~12MBin 8.0) has also been added. Text over the field size limit will be broken up intosequential fields.

TIFF Conversion

TIFF speeds should be greatly improved for record sets with mostly 1-2 page documents.Print speeds in some cases will be twice as fast or more.

TIFF/E-Print

Auto-restarts that may occur during TIFF conversion or E-Print batch processes will nolonger fail to restart if no concurrent user licenses are available. LAW will now wait andcontinue to retry until a license becomes available. This should only take 1 minute at themaximum, unless another user happens to claim that license during this interval, inwhich case it will continue to wait indefinitely for the next available license.

Exports

Introspect now supports the version 5.0 format. To produce a 5.0 version load file, openthe Introspect configuration settings and check the 'Use IDX version 5 format' option.

Related Topics

Resolved Issues

Known Issues

Additional Information

Page 37: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

Release Notes 37

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

Resolved Issues

This topic lists resolved issues in the current release and in previous releases of LAWPreDiscovery.

Version 6.0.05

ED Loader

Applying a time zone override during the import process on Windows Vista/7/2008 maycause metadata timestamps to be off by 1 hour due to invalid Daylight Savings timeshifts. Note: Windows XP was not affected.

ED Loader

Calendar items or emails that have been replied to that are imported from Lotus Notesstores contain "Error Reply" in the header of the extracted file.

ED Loader

Corrected document specific issue in which e-mail body failed to be extracted from anOutlook message when output format was set to HTML/MHTML.

ED Loader

Corrected document specific issue in which some attachments failed to be extracted froman Outlook message when output format was set to HTML/MHTML.

ED Loader

Corrected document specific issue in which the sender may receive the SMTP address ofthe recipient for an Outlook message due to a non-standard internet message header.

ED Loader

MBOX stores with Unicode filenames fail to extract messages.

ED Loader

Resuming a standard (non-distributed) import session manually after a cancel orautomatically after a crash results in an empty EDSource field for all documents importedafter the import is resumed.

ED Loader

Signed or encrypted Outlook messages may fail to render the message body in theextracted native document if the output format is set to MHTML. Note: The extracted textwas not affected by this issue.

ED Loader

Summarize queue report contains demo watermark.

ED Loader

The Insert E-Doc functions fail if distributed processing is enabled.

Endorse

Page 38: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

LAW PreDiscovery38

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

Multipage TIFF images imported into LAW without a ".TIF" file extension lose all pages

but the last during the endorse process.

Exports

Setting the export text priority to "Printed, OCR, Extracted" will favor extracted text overOCR when no printed text is available. No other text priority combinations were affected.

Imports

Corrected issue with special character preventing the import of an EDRM load file.

Management Console

The LAW Management Console crashes regularly when running on Windows 7 SP1.

TIFF Conversion

A native Outlook message (*.msg) that hangs for an unusually long amount of time and

forces a timeout when converted to TIFF using the Shell Printer may be appended to theoutput of another document.

Version 5.9.25

Deduplication

The Deduplication Utility was updated to handle connection drops for SQL cases.

Grid Views

If a user modifies the current view in a grid, and has not saved it before exiting the grid,the Manage Grid Views dialog will now appear instead of a simple save prompt. This willallow the user to see the active grid view before saving, and create new ones.

Management Console

Jobs in the management console (LMC) are now separated into two types, standard"Batches" and "ED Imports".

OCR

Several performance enhancements were made for the ABBYY OCR engine (30-50%faster).

System

Microsoft .NET 4.0 is now required to run LAW.

TIFF/E-Print

The eDrawings Viewer source application now references the 2011 version. It will nolonger work with previous versions.

User Interface

The Reports button is now disabled unless the user has an Admin license in the currentsession.

Version 5.8.14

Administration

Resolved errors that were occurring when deactivating or reactivating cases.

Page 39: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

Release Notes 39

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

ED Loader

An extra file was being added to the queue if files were added via the File(s) button anda sort was being performed in the Select File(s) dialog.

If the system date/time setting to 'Automatically adjust clock for daylight saving changes'is disabled, Outlook messages that occur between 12-1 AM receive an invalid TimeSentvalue in the metadata as a result of an invalid DST adjustment. This did not affect theactual MSG native file or the DateSent field, only the TimeSent field in LAW's metadatawas affected. This issue only occurred in versions 5.6.14 - 5.7.05.

Implemented fix for specific e-mails that were missing the body when converted to HTMLduring import.

Exports

Delimiters for records without native files were not being included in the ConcordanceDAT file when exporting with the "Include reocords without files" setting enabled.

Greyscale images for documents stored in serialized format (1 image per page) were notbeing converted to JPG files when exporting to the single-page format with the "Default"Output setting selected.

LAW would crash if the number of export warnings and/or errors exceeded 32,767.

When exporting using the "Export as single page text" option, certain Unicode text fileswere missing the content in the exported file.

Grid Views

A "not a valid bookmark" error was occurring when attempting to use the Batch Updatefeature in the embedded grid while one or more fields were in the grouping area.

Clicking the Save button in the standalone grid view would case LAW to hang if the gridwas pinned on top of other windows.

Imports

Extremely large EDRM load files (~ 400+ MB) were failing to import due to memorylimitations.

Volume table entries were being read incorrectly in certain cases which could result innative files being imported to the wrong location and not appearing in the case.

LAWtsi

A "Failed to retrieve date from the internet" error was occurring if LAWtsi was openedafter LAW on a machine with no Internet connection.

An "Item cannot be found in the collection corresponding to the requested name orordinal" error was occurring when attempting to scan a document in a case with user-defined page-level fields present.

Management Console

An overflow error was occurring when launching the LMC if certain system fields (i.e.Elapsed) contained extremely large values.

The LMC was not recognizing the ABBYY OCR Engine license.

OCR

A "bad file name or number" error would occur when attemping to OCR records in aUnicode path with the ABBYY OCR engine.

Page markers were not being inserted in text when using the Xerox TextBridge OCRengine for single page serialized images. The OCRStatus and OCRFlag fields were not

Page 40: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

LAW PreDiscovery40

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

updated in this case either.

The "Create PDF thumbnails" option was not functioning as expected for the Expervisionengine.

Reports

When running a Tally report on certain fields in a SQL case, the report would show "<"instead of "<Null>" if the field did not contain values.

Searching

The wildcard characters available for database searching were not working.

TIFF Conversion

In very rare situations, Outlook may produce printed output after a timeout has beenlogged for the document being printed, resulting in the merging of the images with anunrelated document. To prevent this from occurring, Outlook is now forced closed if atimeout is logged while printing to this source application.

TIFF/E-Print

Hidden text was not detected and revealed on some documents.

Revisions were not being displayed in the printed output if "Show Revisions" wasenabled and "Show Comments" was disabled in LAW's Word settings.

Version 5.7.05

Deduplication

Duplicate documents existing in the same custodian across two cases may end up with adupstatus of 'G' instead of 'C' during Inter-case Deduplication.

Using the 'Only test untested records' setting in the Deduplication Utility forces thededuplication of all untested records in the case and ignores selected custodians.

ED Loader

Browse for Outlook Folder continues to populate folders when <ESC> is pressed.Support for <ESC> key has been removed, the Cancel button can now be used to cancelthe loading of the folder structure.

Contacts that are Distribution Lists in Outlook were being unexpectedly deduped.

Corrected incorrect file identification on specific text files as a Tape Archive File (*.tar).

Date/TimeAppStart and Date/TimeAppEnd info is not extracted for calendar items withdates in the future.

DupStatus value is not set to N for items with empty hashes when deduping during animport.

Metadata is not extracted from Office 2007 files (i.e. *.docx) if the import is run on aworkstation with a 64-bit OS.

Session Reports are transposing "Partially Exclude" and "Exclude" for the deduplicationaction on the Deduplication and FileType Exclusion tabs.

E-Print

"Object variable or with block variable not set (91)" error occurs when e-printing with e-printing and tiff conversion slipsheet options disabled.

Exports

Page 41: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

Release Notes 41

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

Concordance Image 5.1 and above is not recognized preventing the creation of the

Opticon database during Concordance Direct (DCB) exports.

Grid Views

An error occurs if attempting to use the spell check feature from the embedded grid onthe main form.

Imports

Files with extended ANSI characters (ASCII > 123) are not parsed correctly during

Delimited Text imports.

If the "RootFilePath" attribute is specified in the <Root> node of an EDRM load file, the

import fails to start and reports the following error, "The filename, directory name, orvolume label syntax is incorrect."

IPRO/Opticon imports may import documents into an unexpected folder when hard paths

are used.

The <Folders> node in an EDRM load file produced by Encase with multiple nested

subfolders is incorrectly interpeted during the import, resulting in an incorrect outputfolder structure in LAW. This may result in a path too long to store that will prevent theimport of a document.

Licensing

Document deletion is permitted via Delete key from main form without an active Scan or

QC license.

Reports

An invalid session database will not refresh the selected sessions value correctly for the

Exception Report.

Files by Type Summary report does not display a summary count if 'Display Custom Logo'

is set to False.

Pressing the <ESC> key before a report begins to render will display a blank preview

pane.

Unable to select reports across report categories when using the keyboard.

TIFF/E-Print

Field code replacement excludes fields found in text boxes.

Field replacement for Excel files does not detect chart-only sheets in workbooks.

Version 5.6.16

ED Loader

Outlook PST output is saved as HTML regardless of output setting (only present in5.6.15).

Archives processed increment the "Incomplete" status count in session log (only presentin 5.6.15).

Batch Update

Batch update fails if query was specified with 'Retain parent/attachment groups' settingenabled.

ED Loader

A record is created for archives and the archive is copied into LAW's file system

Page 42: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

LAW PreDiscovery42

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

regardless of any archive settings. This behavior was inadvertently changed as of the5.5.07 release.

Links to embedded images in HTML e-mails (Outlook) are lost and cause an error duringexports if the original filename is Unicode.

Grid Views

A copy/paste operation in the embedded grid will copy the source data twice.

If the grid is closed while an edit is in progress LAW closes unexpectedly.

User Interface

The folder menu is completely disabled unless the Scan, Edit, or Admin license is active inthe session.

The CaseMap, TimeMap, TextMap links on TotalLitigator menu link to invalid web page ifproducts are not installed.

Version 5.6.14

Batch/Export

Initiating batch/export utilities reports an error if a page-level recordset is active in Accesscases, or the 'Un-endorsed Images' query is run. This does not affect the operation ofthese processes, but fails to calculate the document count correctly prior to the process.

Case Creation

An "invalid authorization specification" error occurs on Windows 7 machines whenattempting to create SQL cases. This operating system is now fully supported.

Modifying the image path of an existing case was causing the "$Image Archive" directoryto become invalid.

ED Loader

A "Type Mismatch" error was occurring when attempting to group by a field in theIncomplete tab in the Session Viewer.

A run-time error was occurring when viewing tabs or grouping in the Session Viewer incertain situations.

ED Loader is unable to initiate a new session for loading if the regional date settings areset to 'English (United Kingdom)' or any locale with a short date format of DD/MM insteadof MM/DD, and the day of the month is greater than 12.

Hash values were not being assigned to the "embedded" archive record when using the"Include embedded archives" ED Loader Archive setting.

Implemented fix for DateAccessed and TimeAccessed being incorrectly mapped by EDLoader to fields DateLastAccessed and TimeLastAccessed in LAW which are not presentin the standard Electronic Discovery case template.

Implemented fix for extracted e-mail body sometimes being truncated from ANSI formatPST files (Outlook 97-2002).

Implemented fix for incorrect From/sender address being extracted from MIME emailswith malformed headers or headers that contain the full multi-part MIME message withno sender present in the top-level header (in which case a reply-to address could beextracted).

Implemented fix for specific e-mails that showed HTML code after processing, caused bysoft returns being present in the HTML elements.

The Conversation index field values for Lotus Notes were not being calculated correctly.

Page 43: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

Release Notes 43

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

The prefixes Re: and Fw: were not being removed from the subject unless they were allCAPS.

The ED Loader was failing to inventory and process input file paths exceeding 260characters. It will now copy these files to a temporary directory for processing and log a"Long Path" warning.

The e-mail bodies in a specific set of Lotus Notes e-mails were not being extracted.

When an e-mail containing an empty (zero byte) attachment file is imported via EDLoader, and the 'Include attachment hashes in e-mail metadata hash' deduplicationsetting is enabled, the e-mail and its attachment records will fail to import and thefollowing processing error will be logged, "Error Src:MMailGenerateAttachmentContentHash - Error Desc: No valid hash content".

Endorse

Endorsing a serialized document containing mixed file types (TIFFs and JPG for example)would force the compression of page one to the rest of the document.

Exports

Using Concordance 10.03 or later to perform a Concordance Direct (DCB) export causesTEXT fields to appear as gibberish (random Unicode characters).

After performing View -> Refresh Grid, the first record in the grid was becoming activebut did not synchronize with the active document if "Synchronize Image" was enabled.

The "group row" (row that shows the value and number of records when the grid isgrouped) was being included in the selected record or all records count. A fix was alsoimplemented for an error that was occurring while saving the grid to file with a grouprow selected.

The legacy ED reports were not respecting the current result set, and would not accountfor records imported from an EDRM load file. Performance was also enhanced, and a limitwas placed on the reports to 3,500 pages. Reports in excess of this would quitrendering due to resource issues and cause all data to that point to be lost. Saving areport over 3,500 pages is still possible if an output of HTML is specified. The pagecounts reported will now default to the PgCount field, since this should always be themost accurate. If not specified, the EDPages field will be used.

Imports

Errors updating image links during imports were not being logged, and you could end upwith records in LAW with empty image links, or missing random pages. Logging duringimports has been improved, and the import process was optimized to improveperformance, especially for SQL cases when using the 'Link to source files in place whenimporting load files' setting (Tools -> Options -> Preferences tab).

The PgCount field would display "1" for the last record in a multi-page Opticon load fileimport when the record contained more than one page. The image viewer would displayall pages but only one page record was added to the database.

Two copies of the same document were sometimes being added during a load file importwith SQL cases if an error occurred logging the record.

Index Fields

After adding a new index field to a case, the currently loaded document would fail torefresh the index fields tab until the document is manually reloaded.

Licensing

Specifying languages other than English (i.e. "Chinese (Hong Kong S.A.R.)") in RegionalSettings -> Advanced Tab -> "Language for non-Unicode programs" prevents LAW fromdetecting the license key.

Page 44: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

LAW PreDiscovery44

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

The license key was not being recognized on a machine with the language setting set to

Chinese.

Using regional settings that use a system date format of d/m/yyyy (e.g. "English (United

Kingdom)") can block LAW from running on machines without Internet access, reportingan "Invalid system time detected" error.

Using regional settings that use a system date format of d/m/yyyy (e.g. "English (United

Kingdom)") can cause license keys to fail on certain days of the month, incorrectlyreporting an expired subscription date.

Management Console

The LAW Management Console (LMC) is unable to function correctly if the regional date

settings are set to 'English (United Kingdom)' or any locale with a short date format ofDD/MM instead of MM/DD, and the day of the month is greater than 12.

OCR

OCRing a document with existing OCR text that is marked read-only fails to update the

text and reports an error of "Error saving text to output file - Path/File access error(75)".

Printing

Batch printing images to paper fails under certain conditions in non-ED cases in version

5.5.07.

Query Builder

Non-numeric values could not be specified for Auto-Number fields in the Query Builder.

Text Search

Text searches that return an extremely large number of document/text hits (~ 300K)

may report no results found due to a memory resource issue with the dtSearch engine. Acritical error will now be returned in this case. The new feature Tag Text Hits may beused as a workaround if this situation occurs to tag records that match a text searchterm.

Text searches would fail with a type mismatch or out of memory error when returning a

large number of document hits (around 200K or more). This limitation has been improvedbut not completely resolved and is still under investigation.

Performing a manual TIFF conversion with the output format set to Serialized and Drop

blank pages enabled in the TIFF Output options fails to display in the preview windowand fails to import any pages of the document after the first blank page in the document.No errors are displayed or logged when this issue occurs.

When Multipage is set as the output format while performing a manual TIFF conversion,some Excel files may fail to display the entire document in the preview window and willfail to correctly save the image. This issue occurs if Excel breaks the document up in thespooler as a result of worksheets containing different page layout settings.

TIFF/E-Print

An "Invalid property value (380)" error was occurring when launching the E-Print dialog

when no printers or only the LexisNexis Image Driver was installed. The same errorwould occur when launching the TIFF Options dialog if no printers were installed.

An error was occurring after pressing the Cancel button while adding a new password inthe Passwords category.

The <Remove> buttons in the Passwords category may display as enabled with an

empty password list.

Page 45: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

Release Notes 45

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

The field codes for the "CREATEDATE" and "SAVEDATE" fields in Word documents were

not being displayed in the output when using the option to "Show field codes" whenprinting.

Version 5.5.07

Compound Documents

Excel files embedded as icon in office 2007 or office 2003 parents have their mainwindow hidden after they are extracted.

ED Loader

Certain PDF files were failing to import and receiving commit errors referencing'ClawWriter30.InsertNewIdentity'.

Files within *.ZIP files containing a folder path greater than 255 characters were failingto import.

Some embedded files in Word 2007 files (*.docx) will not extract correctly and report aname of 'oleObject2.bin'.

Certain file types were being identified as "Internet Message" or "XML" file types insteadof HTML.

The last folder in the path was not being created when importing a file list and mirroringthe original path. The documents were being placed in the folder one level above themissing folder.

The "Platforms" section in the File Type Manager was reflecting inaccurate file counttotals in the grid. Also applied fixes for issues with the file counts in the Include andExclude lists.

Changes were implemented to improve extraction of plain text from a specific problem e-mail.

Exports

Soft returns (CR or LF only) are now removed from load files to prevent unexpectedrecord breaks.

An invalid procedure call error was occurring if the BegDoc# or EndDoc# fields wereselected or if no fields at all were selected for the Custom folder naming feature. Amessage will now appear prior to export if no fields have been chosen and prevent theexport from starting.

Exports

Images stored in serialized format and exported single-page were not receiving thecorrect image color value (i.e. 1 for binary, 2 for color) in the OLL load file created forTrialDirector.

LAW becomes unresponsive and the connection to the license key may be lost whenexporting a record with an extremely large number of attachments (i.e. over 20,000attachments).

Unicode text was not being properly retained when exporting printed text and using thesingle-page text option.

Index Fields

The EDSource values were not being removed from LAW when all records tied to thatsource had been deleted from the case.

Licensing

Checking out the Full Text Indexing license in LAW and then checking it back in will not

Page 46: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

LAW PreDiscovery46

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

restore the Index options tab.

Reorganize Documents

An invalid procedure call error would occur when reorganizing documents with serializedimages and text.

Reports

Fixed two type-o's in the full text report.

Scanning

The Turnover Mode feature was not functioning when the storage schema was set toserialized.

Searching

Images with a header applied by LAW were returned when running the Query > Un-Endorsed Images query from the standalone grid.

Browsing to a Unicode file name when loading full text search terms was not working.Also, Unicode characters included in imported full text search terms were not beingretained.

Records with a null value in the DupStatus field were not being returned after running asaved filter containing the "Does Not Contain" or "Does Not Equal" operator withDupStatus as the target field.

The "Full text search" section in the Query Builder was not being disabled when a saveddatabase filter was applied.

Text Indexing

The _FTIndex values were not being set for records imported via load file or raw imageimports in cases that were not enabled for electronic discovery.

TIFF Conversion

An error would occur and the image would be dropped for a record if one computer hadthe record selected in LAW while another computer was attempting to convert thatrecord's image to TIFF (and replace the existing image). LAW will now log an error in thissituation stating the file was locked by another process or machine.

The paper size would not always stick when changing the setting in the image driversettings outside of LAW.

TIFF/E-Print

Printing a shared Excel workbook with field replacements enabled results in only the firstworksheet being printed.

In extremely rare case, printing an Excel workbook with comments enabled at end ofsheet results in only the first worksheet being printed if the first worksheet does notcontain any comments (file specific issue).

With Show Comments or Show Revisions enabled in the Word printing options, theprinted page(s) or converted image would be shifted down if the file before it hadcomments or revisions. This issue only occurred with Word 2007.

Printing with Internet Explorer 8.0 was extremely slow.

The e-mail header will not wrap properly when printing an e-mail saved as HTML if themessage contains a long attachment string with no spaces in any of the filenames.

Fixed a file-specific issue that caused a "No pages were printed for the specifieddocument" error to occur during the print process.

Page 47: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

Release Notes 47

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

User Interface

Pressing the spacebar while the "One Page" view was active would crash theapplication.

The ability to view records by clicking on them in the document list was sometimesgetting lost after attempting to navigate beyond the first or last record in the case,prompting the message stating you are at the first or last document.

Version 5.4.18

ED Loader

.NET Framework detection does not function correctly on some systems, and blocks EDLoader from starting.

If the ED Loader has not responded for 5 minutes, a new warning message will appearevery second until all have been closed or LAW crashes.

Summary reports show a demo message at the bottom of the page.

Endorse

Endorsing 8-bit grayscale images fails.

Export

Export initialization fails and causes LAW to crash if the number of duplicates detectedexceeds 32,767.

Concordance Direct export to an existing DCB file fails to add records if any of the targetfields are not large enough for the incoming data and logs an error of 'Unable to updatefield from file data'. Such records will still fail to be added, but field level errors are nowlogged to identify the offending fields, their actual size, and the size of the incomingdata.

Concordance Direct export freezes if Concordance crashes and requires userintervention to close the error message from Concordance or Windows. Upon closure ofcrash dialog, all remaining records in the export fail. LAW will now close all such dialogsand automatically reconnect to Concordance to resume the export without any loss ofdata.

Imaging

The Replace Image from existing file function loses the link to the selected image if itdoes not have a TIF extension.

Licensing

Demo licenses do not allow scan functionality.

New case functionality is not available if the Admin license was acquired during theactive session before the first case is opened.

Removing all fields from separator page setup for standard image printing results in noseparator page being printed.

Version 5.4.13

Case Templates

EDD lookup fields (i.e. Custodian) were causing an error when saved to a case templateand then applied in a different case. These field types are now ignored when apply auser-defined case template.

Page 48: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

LAW PreDiscovery48

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

Compound Documents

Implemented fix to correctly extract PDF documents from PowerPoint documents whenPDF documents are not embedded as an "OLE Package."

Document Numbering

Numbering at page level using the &[<field name>] notation was incurring a significantdelay when processing large documents.

ED Loader

E-mails with Unix-style line breaks (LF only) in the message header may cause additionaldata on the end of the sender address.

Implemented fix for SQL deadlocks occurring when loading documents with deduplicationenabled.

Outlook mail stores with Unicode in the file name were receiving processing errors andfailing to import.

The _PS_OLEX system field was not being populated correctly for the parent records.

When "Treat archive items as attachments" is disabled, and an e-mail with attachmentswas encountered in the ZIP, all subsequent records in that archive would get importedas attachments to the initial e-mail.

Letters in the image key of Opticon files (*.OPT) created by LAW were sometimes forcedto upper-case. LAW will now match the case used in LAW.

Printed text would not export if attempting to export text only ("Include Full Text" optionis the only selected in the Formats/Documents tab).

The @PSTFile and @StoreID Summation DII tokens would appearing in the DII at thesame time if both were selected. The @PSTFile will now take precedence if both areselected. According to the load file specifications, both token should not appear in thesame DII file.

Imports

For XML load file imports, Boolean fields now have their input values of "true", "false","0", or "1" translated to "Y" or "N" so they are mapped correctly for text fields that maybe limited to 1 character.

The page-level Header and Footer field values were not being imported when importinga LAW case into another LAW case.

When importing XML load files, the OCRStatus field was not getting a value of "P" whenthe incoming image has associated text.

Management Console

Implemented fix for client-to-client messaging (screenshots and Leave Job requests) inLAW Management Console failing on SQL Server 2000

OCR

OCR for electronic documents that are converted to TIFF does not get moved with thedocument during move operations.

Reorganize Documents

The Reorganize Documents process was failing with "can't open file" errors when single-page images stored in $Image Archive were encountered. These errors were onlyoccurring in cases that were not enabled for electronic discovery.

Templates

Page 49: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

Release Notes 49

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

Page-level fields in case templates were being created as document-level when applying

a template at case creation.

Text Extraction

The body of read receipt and delivery receipt e-mails was not appearing in the extractedtext. Also, format conversion warnings will no longer appear for these types ofmessages. They will be treated in the same manner as Contacts, etc. as they cannot beconverted to HTML.

Text Indexing

Printed text was not being removed from the index when a document was deleted or re-

indexed.

Version 5.3.14

Batch Process

LAW would crash if a user deletes a shared batch while another machine is stillprocessing the job.

Exports

The DocID field could not be included in the Summation DII file unless native files wereincluded.

When exporting records based on a recordset using the field used to track exportstatus, and using the Export Logging feature on the same field again, arbitrary recordswere being skipped during the export with SQL cases.

ED Loader

A sample e-mail was discovered that would receive a DateRcvd of the current date as itdid not have a "Received" field defined in the message properties. In 5.3.12 and later, ifthe field's timestamp is determined to have been created by processing the e-mail, it isconsidered invalid and the value is cleared.

Grid Displays

When running a batch or export from the main form grid, all records were beingprocessed instead of the current record set. This would only occur if the Query Builderwas launched from the standalone grid, followed by records being sent to the main formgrid.

The hotkey for "Row color odd" is now Alt+D. It was previously set to Alt+O which wasalso for the OK button.

If the grid view is pinned to stay on top of other windows, and then closes and reopensthe grid view, the window will no longer be pinned.

Save dialogs were getting trapped behind the standalone grid view if the grid waspinned and changes were made to the profile.

After exporting with the standalone grid view active, an empty grid would pop up if thegrid was closed prior to the "Open Export Folder" prompt appearing.

Imports

When attempting to import a load file containing no records, LAW was failing to presenta status message stating no records were imported.

The AttachPID was being set incorrectly for IPRO load file imports. The invalidattachments could be resolved by validating attachments, but is now corrected for loadfile imports in 5.3.12 and later.

Page 50: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

LAW PreDiscovery50

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

Subscript out of range error was occurring during an EDRM XML load file import if the file

engine was unable to identify the native source file being imported.

Printing

LAW's print server was crashing and displaying an error when any attempting to useMicrosoft Word as a source application when MS Word XP (2002) was installed.

Templates

Page-level fields were not being saved in case templates.

The folder structure saved in a case template was not being created when applying a

template.

TIFF Conversion

The TiffStatus value remained as Y instead of E when placeholders were not enabled

and the document received an error during a TIFF Conversion process.

User Interface

The Retain Color setting was misplaced in the Options tab in the Export Utility. It has

been moved to its original location, below the Merge Annotations setting.

Version 5.3.08

Annotations

Annotations would disappear on a multi-page document stored serialized if a page ofthe document was rotated and then resaved.

ED Loader

The post import timeout was being activated in Access cases when no post importactions were set in the ED Loader settings.

Abnormal termination of an import would result in duplicate DocIDs.

Using the Outlook Fldr. option to import folders from an OST file was not working.

Pressing Cancel had no effect during the scan for mail stores.

The import process would stall when importing e-mails with a large number ofattachments.

Exports

When appending to an existing load file and a control list is present, LAW was notappending the control list. The file was being overwritten.

Only the text of the first document was being included when exporting to IPRO,Concordance (DAT), or Summation, embedding text directly in the load file, andcombining parents and attachments.

If a large number of duplicate values existed in the Image Tag field or field used as a filenaming scheme, LAW would hang for a significant amount of time prior to exporting.

Overflow error was occurring when attempting to export extremely large images (2GB+)from LAW.

Grid Displays

The feature to allow synchronizing of the grid and document list becomes unusablewhen a folder contains a large number of documents (i.e. 30,000+ documents).

Selecting multiple fields and attempting to sort would result in an "Object variable…"

Page 51: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

Release Notes 51

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

error message.

Imports

The state of the "Include" setting was being ignored when importing DII files into LAWand including fields.

If a single document was made up of single-page images and different file formats (i.e.first page is a JPG and second page is a TIF), only some of the pages would bedisplayed. This issue applied to load file imports only.

In Access cases, records created during a load file import were missing images whenstored as single-page. This applied to version 5.2.42 only.

Index Fields

Deselecting the Indexed property for a field does not remove the index from thedatabase.

Open Case

The Cancel button does not work when LAW prompts for a new name when attemptingto open a case with a name already in the case list.

Scanning

LAW would freeze when attempting to scan with PDF as the selected file format.

TIFF Conversion

A Login Failure error would occur when TIFFing in a SQL case on a Windows Vistamachine when not using integrated security.

Version 5.2.42

ED Loader

Corrupt or invalid TAR or TAR.GZ files can result in an error situation that preventsloading any further sources until LAW is restarted.

In rare cases, an Outlook mail store may fail to load. Improved error handling andreporting has been added if this occurs.

Office documents with invalid dates may fail to import in SQL cases if the date(s) fallsoutside an acceptable range.

Office template files (*.oft) are now properly handled during imports and attachmentscan be extracted.

Imports

Doculex import fails if a range file is selected for re-unitizing documents.

OCR

OCRing mixed color images to PDF may result in pink output images if auto-deskew is notenabled during the OCR process.

User Interface

Deselecting and reselecting scale to grey fails to refresh the image as expected.

Version 5.2.37

There are no resolved issues in this release.

Page 52: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

LAW PreDiscovery52

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

Version 5.2.36

Auto-number

The "Number Document" dialog (Edit->Auto Number) was not closing after completion if ablank starting value was used.

ED Loader

When Deduplication is enabled and an ED Loader session is paused and restarted, theremaining records may fail and an error logged for each: "The connection cannot be usedto perform this operation. It is either closed or invalid in this context."

When loose calendar items are imported via ED Loader, the new copy of the calendaritem copied to LAW's folder structure may lose the original date, while the extracted textdid have the correct date.

In rare circumstances, the full SMTP address was not being pulled for the sender of an e-mail imported via ED Loader.

When selecting a drive as a source, the colon and slash was not being removedautomatically. The user was forced to manually remove the invalid characters per thewarning message.

Endorse

The DPI for certain images was being reduced dramatically after endorsing in LAW.

Endorsement was being truncated when attempting to endorse with Unicode data.

Images may receive double endorsements if endorsed multiple times in ED cases if oneor more documents are reconverted to TIFF in a batch process.

Exports

With a specific combination of options selected, exported records may fail with an"Object variable or With block variable not set (91)" error message when Delimited Textis the selected format.

Color images exported to single-page PDF Conversion were resulting in black and whitePDF files when the "Use Pegasus" setting was enabled.

When exporting serialized images with a large number of pages to multi-page PDFConversion, the resulting PDF was occasionally missing pages.

Switching tabs in the Export Utility in a certain manner would cause LAW to crash.

Import LAW Case

Values in PageSource, PageColor, PageSize, PageHeight, and PageWidth were not beingretained when importing a LAW case into another LAW case. Printed text was also notbeing imported.

Summarize Images

The Summarize Images function in the Folder menu was failing with an "Object variableor With block variable not set (91)" error when attempting to use this feature in a non-ED LAW case.

TIFF Conversion

Initializing a TIFF Conversion batch process would sometimes fail with a "Failure occurredsetting default system printer" error.

TIFF/E-Print

Meeting requests fail with a "Method of object failed" error message when attempting to

Page 53: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

Release Notes 53

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

print to paper or convert to TIFF. Printing of these items is not supported via automationif the item is not in the calendar. As a workaround, these items will now be rendered toRTF for printing.

Version 5.2.27

Batch Process

Applying an endorsement using the "First page only" setting is not applied if connectedto a batch using the distributed processing feature.

Running the Endorse Image batch process and the Update Page Data batch process atthe same time causes the page level image data to be deleted.

Deduplication

Type mismatch error when selecting a custodian in the Deduplication Utility.

ED Loader

Attachment text appears in parent text for certain e-mail messages.

Certain types of loose Outlook messages (*.msg) fail to be detected and handled as e-mails resulting in no e-mail metadata or extracted attachments.

Duplicate DocID's may be generated if an import is canceled or if the EDLoader processcrashes mid import.

Received date for Outlook messages is left blank if no sent date is found.

The Date Received field for Outlook e-mails would not be populated if the Date Sent fieldcontained a blank or invalid date value.

Unicode filenames in RAR archives are not retained when imported into LAW.

Exports

"Bad file name or number" error when exporting a native-only record to Summation.

Exporting a BlueTrace load file may fail to generate the OPT and Create-hyperlink.CPTfiles.

Exporting the BegDoc# and EndDoc# index fields to a Concordance DCB producesparagraph field types for both fields. The new default field type for BegDoc# andEndDoc# will create a Text field with a length of 50 characters.

Exporting with logging enabled causes extremely slow export speeds and fails to updatethe export status.

If a UNC export path is specified for the following export formats, the path is actuallyexported as a hard path: CaseLogistix, CaseMap, Concordance, Concordance Direct(DCB), Delimited Text, iconic, and In magic's DB/Text Works.

Specifying a user-created page-level index field for endorsing fails to endorse the fieldvalue onto the image.

Version 5.2.17

ED Loader

The default file type definition file incorrectly set the SourceApp for "AutoCAD Drawing"files (FileType=26) to the "Binary/Hex Printer" instead of "VoloView Express". This onlyaffected new installations of LAW that did not have an existing file type definitiondatabase. The defaults file was also updated to account for the updated file engineincluded with the 5.2.15 Hotfix.

Grid Display

Page 54: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

LAW PreDiscovery54

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

Attempting to set page-level tags for multiple records (eg. Tag All Rows as Yes) in the

standalone grid causes a run time error (Type mismatch) that causes the application toclose. Note: This bug only occurred in the 5.2.15 Hotfix, and only applied to thestandalone grid.

Image Import

The Raw Image Import function would not correctly mirror source folders for selected

folders using recursion in which the top-level checked folder did not contain any images.Note: This issue only exists in the 5.2.13/15 builds.

Installer

The full installer has been updated with a newer version of PSAPI.dll and now performs a

version check on this file. In some cases, the installer could overwrite this file with anolder version and prevent some applications that rely on it from running (includingInternet Explorer).

LAWtsi

LAWtsi could not access a SQL case using integrated security unless the LAW_User

existed on the server.

Version 5.2.15

Batch Processing

Passwords for Acrobat specified in the TIFF/E-Print options were not being appliedcorrectly for Acrobat 8.0. Note: If Acrobat 7.0 is used for printing, passwords containingampersands ("&") cannot be set by LAW due to a limitation in Acrobat. If this characterexists in the password, the file will have to be opened and printed manually.

Batch process initialization for non-distributed batches generated from query results inSQL cases has been optimized to significantly decrease the load time.

ED Loader

Custodians cannot be assigned in the ED loader in certain instances if the short dateformat in the regional settings is set to something other than "m/d/yyyy".

Files with a leading space in their filenames were not being extracted from archives.

OLE-embedded attachments in Outlook e-mail were not being extracted from certainmessages.

E-mails with corrupt or malformed timestamp data cause an "invalid argument to dateencode" error and prevent attachment extraction.

Filenames without extensions were not being extracted from archives if the "Use nestedfilename for items extracted from archives" was enabled. If this option was enabled and"Auto-assign suspect extensions" was also enabled, the files would get extracted asexpected.

In certain message types, attachments were being recognized as embedded images andrecords were not created for the attachments in LAW.

Metadata was not being captured for PDF files extracted with 5.2.13 due to a bug in thefile recognition engine. An updated file engine (2.19) is included that corrects the issue.A custom command is also included that will re-extract metadata for PDF files in an EDcase if needed. It will update and flag all documents that get modified at the time of thescan. The command requires a TAG field to be created prior to running named'PDFMetadataMod'. This field can be used to track which documents have been scannedand modified. To run this scan, select Tools -> Run Command -> PDF Metadata Scanner.

Exports

Page 55: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

Release Notes 55

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

The export process aborts with "The filename, directory name, or volume label syntax is

incorrect. (Errcode=123, Line=800, ProcName=CShell)" when it encounters a multipageTIFF that was created from single document TIFF conversion (printed directly from sourceapplication after launching a native file from its hyperlink). Note: This does not affectimages created from a batch TIFF conversion or serialized images.

Grid Displays

List field values composed of multiple list items (separated by delimiter specified in

preferences) do not display in the grid views.

Licensing

The "Force Reclaim" link for reclaiming expired undocked keys in the profile manager has

been renamed to "Reclaim Undocked Key(s)" and will now serve the same purpose asthe menu item under the Server menu. The link will now always appear rather than onlywhen a key has expired. This feature will work as it did in previous versions with oneexception. If no undocked keys are attached to the machine, but an undocked key hasexpired for the server key, the user now has the ability to force the reclaim of all expiredkeys. Note: Expired keys reclaimed in this manner must be physically attached and havea reclaim run on them before they can be used again to undock a license.

Version 5.2.13

Batch Process

A run-time error and crash may occur if attempting to select a folder in the Batch processthat was previously processed in a batch and later deleted.

ED Loader

After setting the 'Application' to 'Shell Printer' in the File Type Manager for one or morefile types and then importing that file type via ED Loader, the SourceApp was being setto 'No Source Specified' for that file type instead of 'Shell Printer.'

In certain situations, the following error would occur when attempting to restart an EDLoader: The field is too small to accept the amount of data you attempted to add. Tryinserting or pasting less data. (3163).

Exports

Attachment records were failing with an 'Object variable or with block variable not set'error when exporting to Ringtail CaseBook.

Creation of a new partition may fail with the following error if the partition was createdaround a set of EDD records: The system cannot find the file specified.

Date format in iCONECT load file was not being set correctly based on the selectedsetting in the Export Utility.

If an oversized text file was created during an Introspect export, it was being placed inthe wrong location in the export output location (version 5 Introspect exports only).

Object variable or with block variable not set error would occur prior to export whencertain options were enabled in the Summation configuration options.

Parents and attachments were potentially being split across volumes when exporting toIntrospect.

The multi-entry field delimiter specified in the Introspect options was not being appliedto any fields listed after the image tag field in the Selected Fields list.

The number "9" character was not being included for Concordance DCB exports if thecharacter existed in any exported fields.

When multiple volumes were created during Introspect exports, the Batch Name was not

Page 56: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

LAW PreDiscovery56

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

being incremented properly for each volume.

Grid Displays

In certain situations, page-level fields were not set as visible columns in the grid after apage-level query and had to be manually selected from the field list.

The PageSize field was not sorting properly in the grid displays. The values were beingsorted based on their associated numeric values in the database rather than theirtextual values.

View->Attachment fields was not displaying all four fields if the query had already beenrun in the current grid session and the one or more of the fields had been set as hiddenusing the Field List.

Index Display

Long index field names were not displaying properly in the Index Display. Tooltip willnow appear when floating the mouse pointer over the field name in the display if not allcharacters in the name can be displayed.

Index Display

System field values no longer appear to be removed after clicking the Clear button onthe Index display. Only editable field values will be cleared when using this feature.

Index Fields

An error would occur when attempting to rename a user-defined page-level index field inIndex->Modify Fields.

OCR

If 'Auto deskew' is enabled for OCR, in rare cases, an image may cause an automationerror to occur. This error will be followed by a check constraint error message whenupdating the record, and all subsequent OCR operations will fail.

Profile Manager

LAW would not accept a license server name less than 6 characters in length.

Reports

EDD reports were being created with an "evaluation version" footer.

Text Indexing

A document was not being flagged for re-indexing after OCRing that documentindividually. Documents OCR'd via batch process were being properly flagged.

TIFF/E-Print

Due to a bug in Microsoft Visio, only the first page of Visio documents were being printedduring a TIFF Conversion or e-Print process when the SourceApp was set to MicrosoftVisio.

The "Empty Excel workbook encountered" placeholder was being displayed along withactual data in the printed output when certain types of text boxes were contained onthe worksheet.

The setting in Lotus Notes to expand recipient names was being ignored when printingin LAW using the option to print e-mails natively from Lotus, resulting in the To, CC, andBCC fields being limited to 3 lines.

User Interface

Page 57: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

Release Notes 57

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

The Thumbnail and Image viewers were not being displayed properly when running LAW

for the first time on a machine.

Version 5.1.19

ED Loader

Shell Printer was not available in the Application drop-down in the File Type Manager.

Records were failing to import if the regional settings on the processing stations wereset to 'English (United Kingdom)' or the short date format was set to 'dd/mm/yyyy'.

UNICODE metadata (e.g. Author, Subject, Title, etc.) captured during import was beingconverted to ANSI.

DateLastPrnt values were not being extracted from files imported via ED Loader.

Exports

TrialDirector load file was displaying '0' for records instead of '1' or '2' to indicate blackand white or color images.

Import Load File

Load files with extensions in all caps were causing errors to occur upon import.

Text Indexing

Unicode characters in e-mail text were not being indexed.

TIFF Conversion

Batch TIFFing using Peernet driver with 'Drop blank pages' enabled would causeresulting tiff images to be uncompressed.

When converting Excel files to TIFF, the DPI setting was being pulled from Excel PageSetup instead of the image printer resolution setting.

Version 5.1.11

ED Loader

AttachPID values were being set incorrectly when archive items with attachments areimported and the 'Treat archive items as attachments' option is disabled.

In certain situations, LAW was not properly translating the PR_SMTP_ADDRESS whenprocessing e-mail via ED Loader.

An error would occur if the Session Label exceeded 255 characters. The UI now limits thevalue to 255 characters. If the variables exceed 255 characters when expanded, LAWwill notify you and truncate the value to 255.

Exports

Hard returns were appearing in the IPRO OCR LFP file in certain situations.

Certain attachment fields, when exported, were using the wrong Image Tag field valuewhen using the format-specific override option in the Fields tab.

Grid Display

Application may crash when the space bar is pressed while a grid display is the activewindow.

Data was possibly truncated (even if 255 characters or less) when performing a memo totext field column copy in the grid in SQL cases. Note: Truncation is expected when thesource memo field is over 255 characters. A warning message will occur in this situation,

Page 58: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

LAW PreDiscovery58

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

prior to copying the data.

Scanning

The ledger/tabloid scan page size did not work for the Canon DR-7080C scanner.

TIFF Conversion

Comments in Word documents were appearing in certain docs, even when the optionwas set to hide them.

Version 5.1.05

Administration

Editing case properties from the open case dialog causes the database engine value toget cleared.

Batch Process

Invalid procedure call error occurs when attempting to run the Image Cleanup batchprocess with no filters selected.

ED Loader

Fixed improper validation of source names in the ED Loader queue that would previouslyallow \ and / characters to be present in source names. If the 'Use source names as toplevel folder' option was set, this would result in invalid paths being loaded into law.

Fix for errors updating attachment information on records written to LAW if the sessionwas paused, then subsequently un-paused. In this scenario, the records would havestill been written to LAW, but the attachment information would have failed to havebeen applied.

Loading file lists produces invalid paths in LAW when items in the file list are mapped toand reside on another drive or reside above the lowest common directory in the file listin the input directory structure. NOTE: When a file list is loaded with the 'RelativePathing' option set, the ED Loader will attempt to resolve the input paths using thelocation of the file list. If the location of the file list is not related to the paths in the filelist, mirrored output paths may be produced in LAW.

"Type mismatch Error Code 5013' error occurs processing Lotus Notes mail stores withthe GMT option enabled for e-mails without received dates.

ED Loader sessions may not resume properly if the original source name contains invalidcharacters.

Inserting an e-document into an existing attachment range causes the e-document toimport as a parent doc with its viewable children belonging to the previous parent.

Object variable or With block variable not set' error may occur when attempting to importa large number of Outlook mail stores at one time.

Embedded Grid

The Modify Fields dialog could be opened while the embedded grid was loaded. Addedprompt to close the grid prior to launching the field editor.

E-Print

Placeholders do not print for mail store items set to 'No Source Specified'.

Folder breaks were not printing when specified.

Slip sheets for e-mail attachments used an eDoc template instead of an e-mailattachment template.

Page 59: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

Release Notes 59

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

Slip sheets for e-mails may contain invalid numbering (i.e. 15 of 10) as part of the folder

information.

Exports

Updated LAW export utility to locate associated extracted text from Z-Print when a Z-Print case was imported with the 'Link to images in place' option is selected, allowing thetext to be exported properly.

Updated the CaseLogistix format to encode all full text as UTF-8 before writing out to

XML. This problem also exists in the iCONECT format and was addressed in the samemanner.

Added additional checks to prevent issues with folder/filename paths exceeding the

Windows limit of 255 characters.

DateCreated field also contains time stamps when exporting from the grid or ExportUtility, under certain conditions.

Exporting images and text for electronic documents to Summation causes a 'Bad file

name or number (52)' error to be logged for records without images if the set containssome records with images and some without. These records should not be logged if'Include Native Files' is not selected, and are now logged as a warning that no imagewas found.

Merging of parents and attachments during PDF export does not use searchable PDF

(OCR) if available for images that were TIFFed from electronic documents.

'Overflow' error occurs when the Summation DII's record number exceeded 32,767.

ParentID value calculated incorrectly when exporting attachments without their parents.

The XML tags for embedded text in the CaseLogistix export are incorrect (closing tag

does not match opening).

Checking the 'Exts' setting in the file naming scheme can cause the output text filename

not to match the image filename in some situations.

Concordance Direct (DCB) exports truncate field values if the field in LAW is TEXT

(instead of MEMO) and the field value is over 60 characters. Text fields in LAW with amaximum length over 60 characters are now created as paragraph fields in Concordanceto prevent truncation.

Use of alternate image libraries (specified via ini setting) for splitting images during the

export process to eliminate assertion failures does not function correctly. If this settinghas been specified, the user is now alerted of success or failure when the export utilityis loaded.

Attempting to merge parents and attachments into a PDF during an export may cause an

"Automation error, Catastrophic failure" error in certain conditions.

UNC paths for native file paths in Concordance receive a trailing backslash after filenamethat prevents them from opening via hyperlink in Concordance.

Fulltext Search

'Stop statement encountered' error occurs after executing a full text search and

attempting to save the results to a file from the standalone grid display.

Fix for error $0120 occurring when the 'Abort Search After' full text setting is set to anon-zero value and the search returns more documents than the specified value.

Grid Display

Attempting to view attachments from the grid may cause a row size error and fail to

complete building the attachment table.

Fix for row-length error sometimes occurring when using the 'View->Attachment Fields'

Page 60: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

LAW PreDiscovery60

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

function when using a SQL Server database.

Sort and filter-by functions do not work correctly for 'PageFilename' field.

Summary function yields inconsistent results if the grid is not fully loaded into memory.

Summary function yields incorrect page counts for queries where page level recordswere returned.

Find operations did not work correctly for empty lookup values.

Saving the grid results to file causes a 'Subscript out of range' error in some cases.

Import Tag List

Once all the Target Fields are added in Import Tag List window, the application will closeif the Delete button is clicked.

Image Manipulation

Attempting to rotate an image causes a run-time error if the image is an e-doc that hasbeen imported via the ED Loader and has not been converted to TIFF in LAW. Suchimages may now be rotated for display purposes in the viewer, but the orientationcannot be saved until the e-doc has been converted to TIFF.

Under certain circumstances, an image will no longer display in the main image viewerafter inserting an image into an existing image.

Index Display

The 'Default Field' points to incorrect index field after specifying the desired field, thenopening and closing the field editor.

Index Fields

List type fields do not append new values entered into the list field unless there is atleast one value already in the list. Unable to add new values to the field if the list isempty.

Licensing

In rare cases, the profile manager fails to detect the internet connection and LAW 5.0upgrades are not allowed.

In some cases, the LAW 4.0 upgrade process will fail and return an invalid status of UP.

Temporary licenses may not work in some cases if internet access is controlled by aproxy server.

In rare cases, the profile manager fails to detect the internet connection and LAW 5.0upgrades are not allowed.

OCR

The OCR server does not recover as expected from certain errors (PRTKClient) resultingin errors for all documents after the point of failure.

Scanned/imported single page images may fail to OCR under certain conditions with a'File Write Error' in version 5.0.31 (g).

The OCR server does not recover as expected from certain errors (PRTKClient) resultingin errors for all documents after the point of failure.

Query Builder

Selecting combo drop-down on lookup fields (Custodian, EDSession, EDFolder, EDSource)causes a 'Type mismatch' run time error in version 5.0.31 (g).

Page 61: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

Release Notes 61

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

Scanning

Hot keys for changing scan color settings were not working (CTRL +1 CTRL +2 CTRL +3).

The legal scan page size does not work for the Canon DR-7080C scanner.

Performing a Replace Pages scan operation on a single page document with multiplepages causes an 'Object variable or With block variable not set' error for every pageafter the first and loses the first page.

Show OCR Flags

When the thumbnails are not displayed and Page->Show OCR Flags is clicked, LAWjumps to the embedded grid instead of the thumbnails.

TIFF/E-Print

TIFF/e-Print settings may not be applied for new cases unless they are first displayedand accepted by the user. In some cases, this behavior will result in an error messagethat the default printer cannot be set and the TIFF/e-Print processes cannot be started.

TIFF Conversion

Attempting to TIFF a color document with the Informatik printer set to 24-bit color mayfail with a 'Subscript out of range' error.

Printing blank placeholders for e-docs is not possible if 'Drop blank pages' is enabled, nopages will be saved.

Printing with Excel 2000 causes a crash in the print server.

In some cases, Excel documents printed in 24-bit color may not capture all pages duringmanual prints.

User Interface

Deleting pages from an image in an Access case may fail with a 'Key column informationis insufficient or incorrect. Too many rows were affected by update.' error message.

In rare cases, a long sequence of error messages pertaining to grid updates may occurwhen closing LAW.

Replace pages function causes 'Item cannot be found in the collection corresponding tothe requested name or ordinal' error if the case was created in an older version of LAW4.0 and does not contain a PageFilename field.

Version 5.0.31

ED Loader

Categories field was not being populated for E-Docs (now mapped from Category field).

Embedded e-mail (Outlook only) attachments sometimes lose UNICODE metadata whenextracted from their parent and saved in their native format (*.msg).

Embedded file extraction may fail in certain rare instances (missing CompObj stream)and fail to log a warning.

Fix for EOF error that occurs in rare cases during processing of Lotus mail stores (*.nsf).

Office 2007 documents were being processed as archives, producing unnecessaryoutput. **NOTE: Native compound document processing (embedded file extraction) doesnot currently support the Office 2007 format.

Office documents with missing or invalid 'Last Saved Date' fields may use the creationtime of the file itself for the last modification time instead of the last modification timefrom the file system itself.

Page 62: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

LAW PreDiscovery62

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

Outlook mail stores (*.pst) names or source names containing leading or trailing spaces

generate invalid path entries in LAW.

Overflow error occurs on folders containing more than 32,767 items. In order to account

for folders with this many items, the case must be created with LAW 5.0.31 or higher (orthe DocOrder field in tblDoc must be manually updated and changed to a long integer forolder cases).

Revision field was not being populated.

Some Excel sheets have their workbooks hidden when extracted from anotherdocument. This applies to e-docs with embedded files only. It does not apply to e-mailattachments. **NOTE: This may still occur on Excel files with certain types of protectionand is still being investigated.

UNICODE data in recipient fields (To;CC;BCC) is lost on e-mail imports.

ZIP file extraction may fail on files with extremely long filenames

Exports

Assertion failures that occur during exports when splitting to single-page imagesshould be greatly reduced, if not entirely corrected. If they do still occur in anysituation, there is now an alternate image engine available (enabled via ini setting)

that can be used to perform the image manipulation during the export process.

Embedding text directly in fields in Concordance exports (DAT or DCB) can cause LAW to

hang under certain conditions if the size of the text exceeds the maximum size of a fieldin Concordance.

Numeric values are used instead of the corresponding text value for lookup fields

(Custodian, EDSession, EDSource, EDFolder) if used in a custom folder outputscheme.

Merge annotation functionality does not work with E-Docs converted to TIFF in LAW.

The export process may fail to begin for native exports if the selected documents

contained unnumbered images, and images are not included due to unnecessary fieldvalidation that may not be apparent to the user.

Various other export fixes have been incorporated into this release.

Grid Display

Error occurs executing 'Filter by' on empty lookup fields (Custodian,EDFolder,

EDSession,EDSource).

Image synchronization does not work on a result set with one record.

When saving the results of the grid to file, lookup fields (Custodian, EDSource,EDSession, EDFolder) get saved as their numeric values and not their actual lookupvalues (text), as displayed in the grid.

Licensing

Licensing did not work if using Windows with regional settings/default language set to

Japanese.

User may receive an error when starting LAW that the 'CD Publishing' license has

expired even if this license is not present on the key.

OCR

Batch OCR may cause transaction limit exceeded errors in SQL cases under certainconditions.

Page 63: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

Release Notes 63

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

Scanning

Scanning a document, and then immediately rotating and saving pages may causepages to be deleted if the document is not re-opened first. Similarly, attempting toenhance pages (deskew, etc.) immediately after a scan may fail until the documentis re-opened.

Text Indexing

Index process may fail and exit early if a record is flagged for indexing that does notcontain a text file.

Index process may fail and exit early if a record update fails due to network connectivity

issues or the server (SQL) is too busy to complete the update.

TIFF Conversion

Converting a 10,000+ page text file to a multi-page TIFF causes the first 9,999 pages toget lost. The number of pages actually captured depends on how many total pages areprinted. The job is broken into chunks for text files of that size and only the last portionis captured and saved. LAW will now break the job (text files only printed with the Text/RTF printer) into multiple parts with a default "chunk" size of 2,500 pages, and save allparts correctly.

Reconverting large documents to TIFF may fail while updating the database informationin SQL cases with general network errors due to network connectivity issues.

Timeouts may occur converting extremely large text files (3000+ pages) to TIFF and insome cases, LAW will be prematurely restarted.

User Interface

Changing the visibility of the SourceApp field causes it to become locked.

Version 5.0.30

Administration

Deleting records is now optimized for both image-only and ED-enabled cases.

ED Loader

Modified file extraction behavior to recognize if a file was removed by another process (inmost cases, resident anti-virus software). If a file is otherwise successfully extracted, butis not present then a "[Native File Copy] E: (copy failure) (Virus Warning) The fileappears to have been removed by another process" message will be logged. Theprevious implementation logged anywhere from 4 to 6 separate warnings when a filethat otherwise successfully extracted, was removed from the system.

Exports

The direct Concordance export has been modified to always use DDE for populatingdata, which should improve stability on large paragraph (i.e. OCR/extracted text) fields.Support for embedded text over the field size limit (~8MB in Concordance 7.0 and ~12MBin 8.0) has also been added. Text over the field size limit will be broken up intosequential fields.

TIFF Conversion

TIFF speeds should be greatly improved for record sets with mostly 1-2 page documents.Print speeds in some cases will be twice as fast or more.

Page 64: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

LAW PreDiscovery64

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

TIFF/E-Print

Auto-restarts that may occur during TIFF conversion or E-Print batch processes will nolonger fail to restart if no concurrent user licenses are available. LAW will now wait andcontinue to retry until a license becomes available. This should only take 1 minute at themaximum, unless another user happens to claim that license during this interval, inwhich case it will continue to wait indefinitely for the next available license.

Related Topics

Enhancements

Known Issues

Additional Information

Known Issues

LAW PreDiscovery 5.9.25 Known Issue

ED Loader: Unable to import data using “Coordinated Universal Time” (UTC/GMT) as theprocessing time zone unless the “Override system time zone during processing” option isused. Initiating an import session with a system time zone configured to UTC/GMT andunchecking the override time zone setting forces the processing time zone to “InternationalDate Line West”. The TimeZoneProc field will reflect the correct time zone used for processingin this case, it is just not the expected time zone. In this scenario, an error will occur at theend of the import and the current system time zone will fail to be reset to UTC/GMT asexpected.

LAW PreDiscovery 6.0.05 Known Issues

Early Data Analyzer: Symbol characters appear in metadata fields for imported mailstore items. Extra symbol characters sometimes appear in the metadata fields of importedmail store items. These characters often appear as rectangular symbols. They representsystem characters that are present in the original files but are normally filtered from displayin user interfaces.

Early Data Analyzer: The text NaN is displayed in some fields in reports when no sourceis imported. If reports are generated before having imported items in a newly created case,the characters NaN appear in some of the percentage calculation fields in the reports. NaNstands for not a number and is a placeholder for mathematical operations that do not yield anumerical result.

Early Data Analyzer: Compound document support. Early Data Analyzer does not supportlisting of attachments in compound documents. These document types include PDF files andfiles created with Microsoft Office. In most cases, the content of such attachments will still beavailable within the content of the parent document so that it is possible to search thecontent of the parent and any attachments as a single document. During the export processto LAW PreDiscovery, such embedded attachments can be fully extracted and listed by usingthe compound document extraction capabilities of the Electronic Discovery Loader.

Early Data Analyzer: Content extraction with Lotus Notes 8 multi-user install. The content

Page 65: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

Release Notes 65

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

from Lotus Notes files is not extracted if Lotus Notes is installed in its multi-user mode.

Early Data Analyzer: Export exclusions list. Race conditions can cause the languages list inthe export exclusions list to refresh slowly. Switching tabs can help the language list torefresh more quickly.

ED Loader: Unable to import data using “Coordinated Universal Time” (UTC/GMT) as theprocessing time zone unless the “Override system time zone during processing” option isused. Initiating an import session with a system time zone configured to UTC/GMT andunchecking the override time zone setting forces the processing time zone to “InternationalDate Line West”. The TimeZoneProc field will reflect the correct time zone used for processingin this case, it is just not the expected time zone. In this scenario, an error will occur at theend of the import and the current system time zone will fail to be reset to UTC/GMT asexpected.

ED Loader: Track Changes detection. Track Changes detection does not work on MicrosoftWord and Excel documents embedded within other documents.

ED Loader: Microsoft Publisher and Microsoft Access not supported for ED Loadermetadata extraction. ED Loader does not support extraction of custom metadata fromMicrosoft Publisher files or from Microsoft Access files.

Installation: Folder name is LAW50. The name of the installation folder has been leftLAW50 to simplify the upgrade process.

ED Loader: Import from Early Data Analyzer. Under certain circumstances, whenexporting 2 documents from Early Data Analyzer to ED Loader, only 1 of 2 documents isrecognized by ED Loader. This situation results when in Early Data Analyzer 2 files areadded for import from the same source folder using the multiple custodian drag and droparea of adding sources. A message in ED Loader is visible that reads: "The item you haveselected is already in the queue and w ill be ignored."

Defect Notification - LAW PreDiscovery 5.9.25

Related Topics

Enhancements

Resolved Issues

Additional Information

Additional Information

The following table provides a version history of LAW PreDiscovery:

Version Release Date

Version 6.0.05 August 30, 2011

Version 5.9.25 April 15, 2011

Version 5.8.16 December 22, 2010

Page 66: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

LAW PreDiscovery66

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

Version 5.7.05 June 10, 2010

Version 5.6.16 March 31, 2010

Version 5.6.15 March 10, 2010

Version 5.6.14 February 11, 2010

Version 5.5.07 September 2, 2009

Version 5.4.18 May 20, 2009

Version 5.3.14 February 4, 2009

Version 5.3.08 December 10, 2008

Version 5.2.42 September 6, 2008

Version 5.2.37 September 9, 2008

Version 5.2.36 August 26, 2008

Version 5.2.27 June 30, 2008

Version 5.2.17 June 9, 2008

Version 5.2.13 May 12, 2008

Version 5.1.19 January 14, 2008

Version 5.1.11 November 14, 2007

Version 5.1.05 October 12, 2007

Version 5.0.31 April 3, 2007

Version 5.0.30 Feb 26, 2007

Related Topics

Enhancements

Resolved Issues

Known Issues

What's New in LAW PreDiscovery

Page 67: LAW PreDiscovery™ 6.0.05 Release Notes - LexisNexishelp.lexisnexis.com/litigation/ac/law_docs/law6.9/LAW PreDiscovery...Microsoft .NET Framework 4.0 is now required to run LAW PreDiscovery.

Index 67

© 2011 LexisNexis

Index- L -LAW PreDiscovery

enhancements 3

known issues 64

release history 65

resolved issues 37