law prediscovery manual

law prediscovery manual

LINK 1 ENTER SITE >>> Download PDF
LINK 2 ENTER SITE >>> Download PDF

File Name:law prediscovery manual.pdf
Size: 1442 KB
Type: PDF, ePub, eBook

Category: Book
Uploaded: 25 May 2019, 20:52 PM
Rating: 4.6/5 from 645 votes.

Status: AVAILABLE

Last checked: 3 Minutes ago!

In order to read or download law prediscovery manual ebook, you need to create a FREE account.

Download Now!

eBook includes PDF, ePub and Kindle version

✔ Register a free 1 month Trial Account.

✔ Download as many books as you like (Personal use)

✔ Cancel the membership at any time if not satisfied.

✔ Join Over 80000 Happy Readers

law prediscovery manualAll rights reserved. No part of this work may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or by any information storage or retrieval system, without permission. The information contained in this work does not constitute, and is not intended as, legal advice. LexisNexis and the Knowledge Burst logo are registered trademarks of Reed Elsevier Inc., used under license. LAW PreDiscovery, is a registered trademark, Concordance is a registered trademark, and CaseMap is a trademark of LexisNexis, a division of Reed Elsevier Inc. Other products or services may be trademarks or registered trademarks of their respective companies. LAW PreDiscovery Concordance CaseMap LexisNexis Total Litigator LexisNexis Early Data Analyzer LAW PreDiscovery Version: LAW Prediscovery Release Date: February 29, 2012 Errors 18 3 Reorganizing. Documents 20 4 Scanning.Document Ranges 24 6 Extracting. Subsets 26 7 Run Commands Full-text. Indexing 28 9 Configuring. LAW and SQL Server Tracking. Page Source, Size, and Color Reporting Viewing Reports Case Summary. Report 51 Deduplication. Reports 53 ED Loader Session. Report 55 Exception Report Files By Type. Report 60 Files By Type. Summary Report 62 Folder Summary. Report 63 Page Properties. Report 65 Tally Report Using Grids for. Reporting 68 Chapter 4 Reference Information 71 1 Languages License. Matrix 73 3 Field. Descriptions 78 4 Unicode. Support Keyboard. Shortcuts Contacting. LexisNexis 106 Chapter 5 Glossary LexisNexis. All rights reserved. 3 All rights reserved.http://gurolmumcu.com/userfiles/fotometro-sekonic-l-308s-manual.xml

Tags:
• law prediscovery manual, law prediscovery user guide, law prediscovery manual, law prediscovery manual, law prediscovery manual pdf, law prediscovery manual 2020, law prediscovery manual 2019, law prediscovery manual 2018, law prediscovery manual.

By integrating production-level scanning with robust e-discovery and data processing features, LAW PreDiscovery is optimized to enable scalable execution of even the largest discovery projects, from running multiple computers to batch scan boxes of paper documents to importing millions of s and attachments from mail stores, to full text indexing, querying, and exporting to many other popular litigation support applications. In practice, LAW PreDiscovery supports these key discovery processes: Prefilter large document sets The Early Data Analyzer module is a standalone prefiltering module available with the LAW PreDiscovery 6.0 suite. Use it to implement high volume electronic discovery productions. Early Data Analyzer indexes, filters, and produces export sets. Culled documents are passed directly to LAW for full expansion and production. Creating and managing cases LAW PreDiscovery centers all activities, including data collection, processing, and export on the case. Each case corresponds to a database file, which tracks all source files and production files, including graphics and text. In the process of creating a new case, you select a database engine, create and name the database file, establish a folder structure for documents, and define any additional database fields you will need later for coding. Optionally, to simplify future case creation, you can create case templates that specify pre-defined options. Acquiring documents In this step you may do any of the following activities that bring documents into the case: Import electronic discovery using ED Loader to extract text and to record document metadata in the case database. Scan paper documents to electronic format. Import items and metadata from existing cases and load files. Import existing TIFFs or other kinds of image files. Assign custodians at the batch or source level. Code documents with data fields.http://emehck.com/upload/fluke-networks-intellitone-200-probe-manual(1).xml Performing quality control The exact nature and timing of quality control activities vary greatly, depending on the type and quality of source documents. Quality control typically involves multiple activities spread 2015 LexisNexis, a division of Reed Elsevier Inc. All rights reserved. Tag documents that contain specific text or metadata attributes for the purpose of narrowing consideration to pertinent documents or pages. Deduplicate files that were imported during electronic discovery. Fix problems with TIFF files using built-in image cleanup tools. Batch processing Batch processing functionality helps to automate various processor-intensive jobs, including: document numbering, image cleanup, endorsing, conversion to TIFF, printing, and optical character recognition (OCR). LAW PreDiscovery lets you take batch processing to a new level by combining the processing power of multiple computers to join distributed batch processing of large jobs. Exporting LAW PreDiscovery provides a wide range of options for exporting to litigation support applications in a variety of standard formats, including: native files, images, coded data, and OCR text. For information on LAW PreDiscovery and other litigation support products by LexisNexis, please visit the LexisNexis PreDiscovery website LexisNexis. All rights reserved. External deduplication databases can now be created as Microsoft SQL Server databases for better scalability. For more information, see: Inter-Case Deduplication Full-Text Report Full-text search reports now include custodian summary, grouping, and document family information. The Search Request Summary (by Custodian) section is added to the full-text search reports. Family Size (GB). Total file size for the documents, including child documents, returned in the search queries. For more information about full-text search reports, see: Full Text Searching. Imports and Exports Electronic Discovery imports now support Microsoft Outlook OST files.http://stroyzona.com.ua/companynews/electrolux-iron-aid-manual For more information, see: Importing Files. Load File imports and exports now support EDRM 2.0 XML load files. For more information about importing EDRM 2.0 XML load files, see: Importing Cases and Load Files. For more information about exporting EDRM 2.0 XML load files, see: EDRM XML LexisNexis. All rights reserved. The field will contain the contents of the Path field in LAW PreDiscovery. For more information, see: Fields Tab TIFF Conversions and E-printing Microsoft Project is now supported as a source application for TIFF conversions and e- printing. You can modify Microsoft Project settings for TIFF conversions and e-printing by selecting Project from the Categories list in the TIFF Conversion Options dialog box or the e- Print Options dialog box. For more information, see: Output Settings for E-Print and TIFF Conversion and Project. Early Data Analyzer Case Settings The Maximum Agents field is added to the Analysis tab in the New Case Setting and Edit Case Settings dialog boxes. The Maximum Agents field determines the maximum number of agents (computer processors) that can process data for a case at any given time. For more information, see: Cases in Early Data Analyzer. Exceptions The Re-Analyze button is added to the Exceptions tab. The Re-Analyze button provides the ability to re-analyze individual files from the Exceptions tab. When you click the Re-Analyze button for a file, the file is removed from the exceptions list and added back into the analysis queue. Once the file is added to the analysis queue, it is automatically re-analyzed and re-indexed. For more information, see: Reviewing Exceptions. Exports Export sets can now be created and exported by tags, providing more precise control of export sets compared with just the core filtering mechanisms. When an export set is created by tags, the export will only include the files that contain the selected tags. All tags associated with a document are written to LAW during exports from Early Data Analyzer regardless of the selection method. Both group and individual tags in Early Data Analyzer are created as document-level tags in LAW PreDiscovery LexisNexis, a division of Reed Elsevier Inc. All rights reserved.Filters The Language Filter is added to Early Data Analyzer and is now available for selection from the filter list on the Filters tab. The Language Filter identifies the languages in each of the case files, and allows you to filter and tag individual and groups of documents based on the languages selected in the Language Filter. The Date Range Filter now supports filtering by multiple date ranges. The Content Filter (Text) is now removed from the filter list on the Filters tab. The Content Filter functionality is now incorporated into the new search feature in Early Data Analyzer. For more information, see: About Searching. For more information about filtering in Early Data Analyzer, see: Filtering. Global Dashboard The functionality for modifying the processing and analysis priority order for cases has been modified. You can now quickly change the processing order from the new Modify Case Priorities dialog box. The Modify Case Priorities dialog box is accessed by clicking the new Modify the order in which cases are processed link on the Working Cases tab on the Global Dashboard. For more information, see: Using the Global Dashboard. Indexing The 64-bit version of the text indexing process is added to Early Data Analyzer to improve speed and scalability on 64-bit operating systems. The Compact Index button is added to the Full Text Index section on the Dashboard tab. Clicking the Compact Index button compacts the index to reduce the indexing space on the disk and removes fragmentation from the index. The index can only be compacted when the indexer state is idle. OCR The OCR tab and the OCR Document button are now added to Early Data Analyzer for performing OCR (optical character recognition) on image-based documents, such as TIFF, JPEG, GIF, BMP, PNG, and Adobe Acrobat PDF files, at the document level so that the documents' content can be read, filtered, and searched before exporting the documents to 2015 LexisNexis. All rights reserved. OCR can now be performed on groups of image-based documents by file type on the OCR tab, or can be performed on individual image-based documents using the OCR Document button on the Filters, OCR, Search, Export and Exceptions tab in Early Data Analyzer. The purpose for performing OCR on documents is to help identify the documents you want to export to LAW PreDiscovery. When you export image-based documents on which OCR was performed in Early Data Analyzer, if an image-based document included image-based attachments, only the OCR from the parent document is exported to LAW PreDiscovery. The OCR for the child documents is not exported. In this scenario, OCR needs to be performed again on the child documents in this document family in LAW PreDiscovery once the documents are exported into LAW PreDiscovery. For more information about performing OCR in LAW PreDiscovery, see OCR Overview. Password Management The Passwords tab is now added to the New Case Settings and Edit Case Settings dialog boxes for managing passwords and extracting content from password-protected Adobe Acrobat PDF files. When the password for a password-protected PDF or PST file is added to the Password tab, the document content will be visible in the content viewer in Early Data Analyzer. Passwords can be manually added or imported from a line-delimited.txt file. For more information, see: Cases in Early Data Analyzer. Two new reports and two new log files are added to the Reports tab in Early Data Analyzer: Export Report. Provides a summary of the documents exported to LAW PreDiscovery across all export sessions from Early Data Analyzer for the current case grouped by custodian. Export Exclusion Log. A text-based log file containing a list of all documents not included in the export set provided to LAW PreDiscovery. Export Inclusion Log. A text-based log file containing a list of all documents included in the export set provided to LAW PreDiscovery. Search Report. Provides a summary of the search results for all defined searches by 2015 LexisNexis, a division of Reed Elsevier Inc. All rights reserved. The report includes hit counts by search term and family, and sizes by search term and family. The Search Report replaces the Full Text Report introduced in Early Data Analyzer version 1.0. For more information about reports, see: Creating Reports. Searching The Search tab is now added to Early Data Analyzer for performing searches in Early Data Analyzer. The Search tab provides enhanced search capabilities, including: metadata search (searches by field and field values), searches by dictionary words, saving and editing search terms, and viewing search results by metadata-based clustering on custodian, file type, sender, and sender domain on the Guided Search tab. In Early Data Analyzer, search is only performed on the filtered records for a case. For example, if a case contains 3,000 records, but after filtering the records there are only 500 records, a search query is only run against the 500 remaining case records. Tagging Tags can now be created and applied to individual files or files in a group, such as files in a filter, search query, or exception category, in Early Data Analyzer. Tags are applied to individual files in the Document Tagging section at the bottom of the document preview pane on the Filters, OCR, Search, Export and Exceptions tabs in Early Data Analyzer. Tags are applied to files in a group in the Group Tagging pane on the Filters, Search, and Exceptions tabs. For more information about applying tags, see: Tagging. Tags are added to a case, maintained, and can be exported on the new Tags tab in the New Case Settings and Edit Case Settings dialog box. User Interface Sort functionality is now added to columns on the Filters, Search, and Export tabs in Early Data Analyzer. On the Filters tab, you can now change the sort order of the the Name, Start Date, End Date, Count, and Tags columns. On the Searches tab on the Search tab, you can now change the sort order of the ID, Tags, and Count columns. On the Export tab, you can now change the sort order of the Name, Total, and Filtered columns. By clicking a column header, you can sort items by the selected column in ascending or descending order LexisNexis. All rights reserved. All rights reserved. In this section Compacting the Database Describes a rationale and provides procedures for compacting the case database. Reviewing Errors Provides instructions for using the Log Viewer to review errors and warnings that may occur during various operations. Reorganizing Documents Provides procedures for using range files to help reorganize documents. Scanning for Errors Describes procedures for scanning the case database for errors. Validating Document Ranges Describes the process of validating document ranges and describes methods of validation. Extracting Subsets Provides procedures for extracting data and images from one folder to a selected output folder. Run Commands Explains how to access the command prompt directly from LAW PreDiscovery for the purpose of starting external programs or running scripts. Full Text Indexing Explains what is required in order to do full-text indexing. Configuring LAW and SQL Server Describes installation and configuration options for SQL Server that enable it to work with LAW PreDiscovery. Tracking Page Source, Size, and Color Provides procedures to gather statistics on page source, size and color. Reporting Provides a detailed listing of the reports available to you LexisNexis, a division of Reed Elsevier Inc. All rights reserved. However, if multiple users are performing extensive coding and scanning in a case, consider compacting the database daily. Reasons to compact a database Compacting databases is an essential part of database maintenance. Compacting the database can provide the following benefits: Consolidate unused disk space. Rebuild indexes. Decrease the size of the database. Increase performance. Reduce the incidence of failed database operations. Reduce problems related to network latency associated with running queries on very large databases. Database files tend to increases in size as information is added and removed. The space used by records is not reclaimed when records are deleted, causing the size of the database to grow over time. This unused space is removed during the compact operation, reducing the size of the database. The size of the database before and after the compact operation will be reported, so users can see how much space was recovered (Access only). To compact the current database On the File menu, click Administration, and then click Compact Database. The Compact Database feature is not supported for SQL Server-based cases LexisNexis. All rights reserved. You may choose to open the viewer at this time. 1. From the main window, on the Tools menu, click Log Viewer. The Open Error Log dialog box appears LexisNexis, a division of Reed Elsevier Inc. Click a different tab and then select a log. 3. Click Open. The Log Viewer dialog box appears. The table lists fields is log files and the title bar shows the filename of the error log. This action can be useful for creating custom reports, reviews, and selecting items for further processing, etc. 1. Create a Tag (Boolean) field. For more information on creating tag fields, see Creating Tag Fields. 2. On the Tools menu, click Log Viewer LexisNexis.Tagged records will appear checked in the grid displays and set to in the Index display. Tag values cannot be toggled using this feature. Related Topics Viewing Reports Batch Processing Overview Creating Tag Fields Reorganizing Documents You can reorganize your documents based on the ranges specified in a selected range file. Note the following facts when considering when to reorganize documents: The best time to run the reorganize documents function is prior to OCR operations. The reorganize function is capable of reorganizing text extracted from documents by OCR. However, information not associated with the leading document for a range will be discarded. If an error does occur you might see a message stating that the image and OCR text are not synchronized. In such cases, the reorganize process will stop and the OCR data will have to be removed or corrected for the image. This issue can occur any time the OCR process stops before it completes. For example, the issue could result if the OCR engine crashes, if you attempt to insert new pages into a document after the OCR process ends, or if you try to merge documents with incomplete OCR. To reorganize documents 1. Click File, click Administration, and then click Reorganize Documents LexisNexis, a division of Reed Elsevier Inc. All rights reserved.LAW PreDiscovery will begin rebuilding documents based on the specified ranges. Related Topics OCR Overview Scanning for Errors As cases increase in size, you will want to detect and eliminate certain types of problems in the database. The Scan For Errors feature provides a means to automatically search the database 2015 LexisNexis. All rights reserved. 22 22 LAW PreDiscovery for some common problems. Note the following facts about the Scan For Errors feature: Errors that are detected are logged in a file named scandb.log that is kept in the temp folder (temp\law50\log). When the scan is complete, if errors were found LAW PreDiscovery will present the option to view the log file. To scan for errors 1. On the File menu, click Administration, and then click Scan For Errors. 2. Select options to customize the scan and then click Begin. Options to customize the scan are described in the following table: Option All Documents Current Folder Include subfolders Ignore Native Documents When you want to Scan all documents for errors. Scan only documents in the current folder for errors. Scan documents in all folders within the current folder for errors. Prevent native documents (records without images) from being repeatedly scanned and logged as errors LexisNexis, a division of Reed Elsevier Inc. All rights reserved. 23 Administrating LAW PreDiscovery 23 Find invalid records (missing images) Verify that each record in the database has a corresponding image. Remove if found Remove invalid records. This option is useful if you have used Windows or some other program outside of LAW to delete or move files. These actions could cause LAW to contain records that do not point to valid images. These extra records can affect processing and summary functions, so users should remove them. Whether intentional or simply operator errors, certain export formats require non-blank Page ID entries for renaming or linking purposes. This option provides a way to find the documents with blank entries so users can take the appropriate measures to correct them. To add page IDs to pages that have blank or empty Page ID entries after they are found: 1. Open the standalone grid display. 2. On the Query menu, click Blank Page IDs. A 'missing' Page ID is defined as being a document record with an incorrect number of page-level records. Since each document should have the same number of page-level records as the document's page count, this check ensures (for example) that a 5- page document has exactly 5 records in LAW's page table. If any missing page records are found, LAW will automatically sequentially number the PageID values of the missing page level records if Auto-number missing pages is selected. Find gaps in Page IDs Find gaps or breaks in the numbering sequence. Pages in a case are typically numbered sequentially. Sometimes, however, there may be breaks in the numbering sequence. This option allows users to find these breaks to ensure that all pages are accounted for and to confirm these breaks, if any, are intentional and correspond to the original documents. Since there can only be one 'page 3', this record is safe to remove. Duplicate records can be detected while numbering a range of documents as it causes a duplicate PageID to be detected during this process. An orphan page record is a page level record that no longer belongs to an existing document. This may have occurred after a document was deleted, but a failure occurred deleting the page records for the deleted document. These records are also safe to remove from the database LexisNexis. All rights reserved. 24 24 LAW PreDiscovery Verify Page Counts Validate the page count of every image in the case that has a record. LAW PreDiscovery opens every image and compares the actual page count with the page count stored in the database. If the page count in the database is incorrect, it is updated, provided the Correct invalid database page counts option is selected. Because every image has to be opened, this option can be very time consuming for large cases. However, this option has several benefits. First of all, it ensures that the total page count displayed in the Case Summary is accurate for billing purposes. Second, by opening every image file, it ensures that none of the images have become corrupted (if they are, it will be logged). Third, it ensures that there are no excess Page ID entries (entries for pages greater than the actual page count) that can affect the export process. Related Topics Importing Electronic Discovery Launching the Grids Validating Document Ranges The process of validating document ranges is composed of the following steps: 1. Before scanning, inspect the documents to determine document breaks. 2. Create a range file that describes document breaks. If errors are found after scanning, you can manually correct document breaks by using a combination of the Merge Documents and Split Documents functions. To validate ranges 2015 LexisNexis, a division of Reed Elsevier Inc. All rights reserved. 25 Administrating LAW PreDiscovery On the File menu, click Administration, and then click Validate Ranges. 2. Enter the path to a range file. After a range file is identified, documents are compared against the range file in two passes. The first pass ensures that all pages fall within the specified ranges. This pass is only useful if the documents and ranges are numbered sequentially with few or no gaps. Otherwise, LAW may report an excessive amount of errors. Any pages that do not fall within one of the specified ranges will be reported in the error log. The second pass validates all of the specified ranges against the documents in the case. Any ranges that are not found is reported. 3. To display the error log, click Yes. Related Topics Merge Documents Split Documents Reorganize Documents 2015 LexisNexis. All rights reserved. 26 26 LAW PreDiscovery Extracting Subsets This feature extracts data and images of the current folder to a selected output folder. This feature has been designed to be useful for creating partial backups and re-importing. Not all indexes and field properties are retained, so the output is not suitable for a standalone working case. To extract subsets On the Folder menu, click Extract as Subset. This function works with either ADS or Access databases and always produces a project.mdb file. This feature is not supported with SQL Server cases. Related Topics Export Utility Overview Launching the Grids Run Commands This topic covers integration of LAW PreDiscovery with custom applications and scripts. This topic assumes you have intermediate to advanced programming skills. LexisNexis assumes no responsibility for any damage done when you the LAW PreDiscovery run command to start external applications, scripts, commands or other active content. LAW allows you to run executable files, commands, and scripts on LAW cases. Note the following facts when you run external commands from within LAW: The connection string to the current database is passed to the executable or script. Only programs located within the \Commands folder can be executed from within LAW. If the external program contains a file description, this value will be used in the menu name. If no file description is found, the menu name is populated by the filename without the extension. For a listing of index fields existing in LAW for both ED and non-ed-enabled cases, please 2015 LexisNexis, a division of Reed Elsevier Inc. All rights reserved. 27 Administrating LAW PreDiscovery 27 see the Field Descriptions topic. To run an external command Click Tools, and then click Run Command. Create a connection string using code The following code creates a connection string using Visual Basic. The VBA.Command property will return the connection strings for both an Access database and an ADS database. This command is useful when you want to work with RecordType data without having to export first. This command is intended only to be used with LAW cases that are enabled for electronic discovery. Populate RecordType Values In this command, represents the field available only in the export utility. This field is used to classify exported records as e-docs,, etc. The command can be used to populate this field within the LAW case database thereby Using the RecordType command The following procedure describes how to use a command to populate RecordType values in a LAW case: 1. Create an index field to store the values. Note the following requirements for the field: The field type must be restricted to Text or Memo. You can name the index field anything you like as long as the field is applicable at the document-level. 2. Click Tools, click Run Command, and then click Populate RecordType Values. 3. Type the name of the target field and then click Begin. The possible values for target field are: LOOSE ATTACHMENT ATTACHMENT E-DOC ATTACHMENT 2015 LexisNexis. All rights reserved. 28 28 LAW PreDiscovery LOOSE E-DOC IMAGE ATTACHMENT IMAGE 4. When the process has completed, a Success message box indicates the number of records successfully updated. Related Topics Administration Full-text Indexing To perform full-text searches, the text for the records must first be indexed. The following indexing capabilities are offered by LAW PreDiscovery: Allow automatic indexing occur after you: Use ED Loader to create new records. Import a case. Import raw images if the new record has associated text. Create scanned images and then OCR them. Manually start the indexing process as necessary. You can re-index documents, for example when you import a load file that contains records with text; or after you add text to previously indexed documents, as when you perform OCR or TIFF conversion after import. You can also disable automatic indexing as a post import action in ED Loader. To configure indexing options Before you perform any action that involves indexing, consider configuring indexing options. Indexing options provide you with control over how certain words, punctuation, and other text elements are handled during indexing. Auto-indexing can also be enabled from this form. 1.