Tag Archives: eCapture

Ipro Announces Major Performance and Productivity Gains to its Best-In-Class Processing Engine, eCapture

eCapture by Ipro

Over the last four years, Ipro has been updating its industry-leading processing capabilities based on the foundation of eCapture. It is the backbone processing engine of the Ipro for enterprise solution. Ipro’s new streaming technology has automated the entire eDiscovery process from the upload of data through Production into ECA or Review. Integrating with Ipro for enterprise’s self-service module allows custodians to upload documents without needing direct access to the controller or job queue. The automation allows customers to kick off a job and leave the office knowing that the case is rapidly moving forward.

The quality and the amount of processing options to handle complex data types truly sets eCapture apart from all other competition. This includes the QC Module, which is a feature-rich quality control module allowing customers to filter and find flagged documents, validate processed data, and easily correct issues.

While already hailed as best-in-class by industry analysts and users for its ability to take control over large, complex data sets with outstanding speed and unparalleled quality, Ipro continues to innovate and dramatically improve eCapture, creating major performance and productivity gains in the software, including:

  • Unlimited extraction of meta-data fields
  • Increases in overall processing speed, up to 40%
  • Report generation speed performance gains of up to 95% on SSDs
  • Up to 70% efficiencies in CPU usage
  • Improved processing of new and complex file types
  • Superior image and production quality, including the latest MS Office file types

In addition, several improvements were made in the latest version of eCapture (2019.6.2) including 1) the ability to auto-publish all documents to review, even those held back due to errors, 2) extracting additional metadata from photographs and PDF files, 3) the ability to convert standard discovery to streaming discovery jobs to take advantage of the speed and more efficient workflow, 4) improved handling of documents with passwords, while driving down installation and upgrade times, making it possible to move to the latest version with minimal interruptions to business and down-time.

Finally, eCapture, the engine of Ipro for enterprise, has a robust roadmap, including work with our partners to continue developing secure public API’s—allowing partners full access to customize their workflows and take advantage of the power of eCapture.

Visit us here to learn more about eCapture by Ipro or Ipro for enterprise

 

About Ipro Tech, LLC

Ipro is a global leader in eDiscovery technology used by legal professionals to streamline discovery of electronic data through presentation at trial. Ipro draws upon decades of innovation to deliver high-performance software, services, and support, bundled as a solution and deployed the way you want it—Desktop, On-prem or Cloud—significantly reducing the cost and complexity of eDiscovery.

Tech Tip Tuesday: Pausing Jobs and How This Could Affect Deduplication in eCapture

Here’s a common situation that could cause problems when pausing jobs and a tip to prevent it.

When it comes to pausing jobs you should know the possible impact this could create with deduplication. In general, pausing a job will not impact anything with the job, but this can change depending on other jobs that are running or will be run. Here is an example of something that can happen:

We start a job called Job A. Then we pause Job A and start another job (Job B) in the same custodian.

We are de-duplicating at the custodian level.

Let’s say Job A has processed 10 files before it was paused, one of those files was found in Job B > Job B will list the item as a duplicate of the item in Job A.

Let’s let Job B finish and unpause Job A and let it finish

The last item in Job A was a duplicate of an item in Job B > Job A will deduplicate it out, keeping the item from Job B

In this case, both jobs have an item that was deduplicated from the other. Whichever job discovers the item first will be the reference, and all other jobs will mark their items as duplicates, even if one job finishes before the other or if a job is paused.

Starting jobs

 

Let’s go over another scenario:

Let’s start Job A and let it get through the same 10 documents again, then pause it

Now we will start Job B and let it finish. One of Job B’s items is a duplicate of one of the items in Job A that is done with processing and gets deduplicated

Now we delete Job A. What happens to the item in Job B? It still is marked as a duplicate, and will still be deduplicated.

Now we are in a problem where an item is getting marked as a duplicate despite the original job being deleted. Normally if we delete Job A before starting Job B, this wouldn’t cause a problem, but because the jobs were active at the same time, the jobs are now “linked” by their duplicate items, and deleting one job means potentially re-running the other.

Knowing this ahead of time in the event you need to pause a job will ensure nothing important to your review gets missed.

For more tips be sure to check out the Ipro Community page or visit Iprotech.com.

Tech Tip Tuesday: eCapture

eCapture

We polled our Support team and Ipro Community to find some common questions our product users had and the best resolution. Check back on Tuesdays for more tech tips to help you make the most of your Ipro investment.

Pausing Jobs and How This Could Affect Deduplication: eCapture

If you are ever in the situation where you need to pause a job in eCapture for some reason, then you should know the possible impact this could create with deduplication. In general, pausing a job will not impact anything with the job, but this can change depending on other jobs that are running or will be run. Here is an example of something that can happen:

We start a job called Job A. Then we pause Job A and start another job (Job B) in the same custodian.
We are de-duplicating at the custodian level.
Let’s say Job A has processed 10 files before it was paused, one of those files was found in Job B > Job B will list the item as a duplicate of the item in Job A.
Let’s let Job B finish and unpause Job A and let it finish
The last item in Job A was a duplicate of an item in Job B > Job A will deduplicate it out, keeping the item from Job B

In this case both jobs have an item that was deduplicated from the other. Whichever job discovers the item first will be the reference, and all other jobs will mark their items as duplicates, even if one job finishes before the other or if a job is paused. Let’s go over another scenario:

Let’s start Job A and let it get though the same 10 documents again, then pause it
Now we will start Job B and let it finish. One of Job B’s items is a duplicate of one of the items in Job A that is done with processing, and gets deduplicated
Now we delete Job A. What happens to the item in Job B? It still is marked as a duplicate and will still be deduplicated.

Now we are in a problem where an item is getting marked as a duplicate despite the original job being deleted. Normally if we delete Job A before starting Job B, this wouldn’t cause a problem, but because the jobs were active at the same time, the jobs are now “linked” by their duplicate items and deleting one job means potentially re-running the other.

For more tips, be sure to join our Ipro Community.