Keyword searchiing: https://youtu.be/n2Fj1SrYDAo  Culling the Collection with Keywords

Hi Karl,

Relativity has tested and approved the direct export functionality of Discovery Assistant as a plug-in tool for Relativity, where Discovery Assistant is used as an affordable and easy to use processing tool, and Relativity is used as a review tool.

Discovery Assistant offers a First Pass Coding and Review Module that is an interactive appliance that can do lightweight review triage on native collections prior to full-featured review.

Documents can quickly be deemed responsive or non-responsive by using 100's of search strings, in batch mode, where the appropriate search term can be captured in the metadata for that record.

There's no theoretical limit to the number of search strings used with Discovery Assistant.

The ability to identify and group Near-Duplicate Documents produces better results by eliminating redundancy in the eDiscovery review process and reduces overall review costs by as much as 30%.

Also, OCR collections (scanned documents) typically do not produce exact duplicates and Near-Duplicate Document Detection will identify duplicates and further reduce review time and costs.

The benefits of using email threading with Discovery Assistant can be summarized as follows:

• • Faster review - earlier emails in a thread can be skipped because their content is repeated in a later email in the thread.

  • Consistency - the reviewer has the option of treating all emails in the thread consistently.

  • Decision-making Quality - reviewers can understand the context of the entire email conversation and therefore make more informed decisions on things like relevance and privilege.

The following are production features not offered with most other review tools.

In summary, Discovery Assistant offers major features like:

• Support for Microsoft PST, MSG and Lotus NSF files

• RTF Extraction from Lotus Notes

• Extraction of OLE objects, embedded PDF attachments, zip contents

• Perform Optical Character Recognition (OCR) to text

• Native Text Extraction

• Metadata Extraction

• Search Filtering           

• Date Filtering

• Near Duplicate identification

• Email thread identification

• Create TIFF images (Distributed across multiple machines)

• Create text searchable PDF files (Distributed across multiple machines)

• Export to other leading case management products like Relativity (Distributed across multiple machines).

Discovery Assistant strengths:

• Excellent reliability processing NSF and PST files

• Distributed Processing scalable to 100's of systems

• Ease of use with a short learning curve enabling rapid deployment

• Low acquisition and support costs through simple, straight forward licensing

• Priority technical support with direct access to senior development staff

• Custom development with rapid response to customer’s specific needs

Unfortunately we are not quite familiar with Logikcull.

Feel free to get back to me if you have more questions.

Best regards,

Stan

Discovery Assistant works with Windows 10 and 11

You can always download the latest demo version from our web site http://www.discoveryassistant.com

Here are some general comments in regard to Hardware/Software requirements for a single installation

---------------------------------------------------

Windows 2010 or later (works with all shipping Microsoft operating systems).

8 Gig of memory (16 Gigs or more is better).

1 fast multi-core processor (4 processors preferable).

At least 10 Gigs of available hard disk space on a fast hard drive. (500+ Gigs is better)

Latest version of Office 365 (supports all past versions of Office).

Acrobat 11 Reader or later (supports Acrobat 6.0 or later).

Internet Explorer 9. [works with IE 11, 10, 8, 7, 6]

Simple rule of thumb is 10 Gigs of source data expands to 60 Gigs of project data.

(includes temp files, stamped and non-stamped TIFF files).

We've seen speed improvement with Dual processors, but no real difference going to Quad processors (unless you install and use Virtual machines).

Fast hard drive and lots of computer memory are ideal. Windows 10, Windows 7, XP and 2003 are good choices for the operating system (Vista / 2008 / can be slow with network security issues).

If you have the source documents on one drive (reading), and the project on a second drive (writing), that gives the best hard drive performance speed.

Discovery Assistant uses the Office 2007/2003 OCR engine (Omnipage) if it's available.

The native OCR that ships with Discovery Assistant has only a minimal feature set.

The OCR engine can be downloaded for free as part of the Office SharePoint installation.

Details: http://discoveryassistant.com/MODI.php

Memory seems to make the most difference if you are looking to improve conversion speed.

In 15 minutes of testing:

3.5 gigs ram - 390 jobs,

2 gig ram - 313 jobs

1 gig ram - 170 jobs

Next after that is hard drive speed. If your source documents are on a network, and your project is on a network, then those two conditions will slow down processing.

Discovery Assistant comfortably handles the conversion of up to 100,000 files per project.

For example, if you have one million files to convert, then our recommendation is to break them down into 10 separate projects.

For testing purposes, we suggest you install Discovery Assistant on its own physical machine with 8 Gigs of memory (machine cost of $1K), with a large hard drive (3 terabites for $150), and keep the data local while processing.

The problem with running Discovery Assistant within a VM is that all network traffic on that one machine is routed through the same one network card. There may be additional resource contention issues that may come up. (hard drive access, memory, SQL issues, etc.). Using a standard physical

machine for benchmark testing will help identify resource issues within the final operating environment.

Feel free to contact our technical team directly at 604-525-2108 or by e-mail: support@imgmaker.com to arrange for a walk through or if you need our assistance.

Best regards,

Stan