Review Pass Document Loading Acceleration

Introduction

Loading documents in a review pass is much faster now that the near native HTML files can be rendered during batch creation rather than only on the fly as the native documents are being reviewed.

Note: These HTML files are called "near native" as they contain the native document content, but in HTML format. A near native HTML file is generally smaller than its corresponding native document because the HTML file contains only code and not the embedded textual and/or graphic elements of the native document.

Rendering Near Native HTML Files Through Batch Creation

To increase user performance by not having to render all near native HTML files at the same time, and also to reduce the amount of storage space, the number of batches created at one time defaults to 20. This means, for example, that once a batch in that group of 20 is entered, a "batch 21" will be created to keep the number of batches in the queue at 20.

Note: The number of batches created at a time can be configured through SQL. And this number determines how many batches can be available at one time to render near native HTML files through batch creation.

Also note that if you want to render the HTML files on the fly as was previously done, you can set the batch creation value to zero.
Reviewing documents outside of the batch will still create the HTML files on the fly as before.

The HTML files are stored within the case directory. When you create a batch (see Manage Review Passes), the following occurs:

  1. A folder named NativeHTML is created in the case directory.
  2. The near native HTML files are being rendered and placed in the NativeHTML folder.

As the batch is created, the jobs that create the HTML files show up in the Job Manager queue. As the HTML files jobs are created, they are placed into temporary folders. As soon as each job completes, the HTML files are loaded into the NativeHTML folder.

Deleting Near Native HTML Files

Near native HTML files are deleted when:

  • (a) The review pass is deleted
    -and-
  • (b) Those files do not exist in any other review passes in which the respective native document is not marked as complete. (That is, if a near native HTML file still exists in a review pass that has not yet completed, it will not be deleted.)

  • The batch that contains them is checked in.
  • The case that contains them is deleted.
  • The respective native documents are deleted.

 

Related pages:

Create Review Passes and Batches