Perform quality control checks

Administrators can perform pre-production quality control checks to verify that underlying data required for the production is correct. These checks allow administrators to address any issues before locking the production.

Ringtail only enables checksif documents are added to the unlocked production and the checks are relevant based on the designated production details. For example, the Missing native files check is not enabled if the production is set up as Endorsable image only.

Note: Quality control checks do not scan the file share for files. They check the database for files associated with documents. If these checks indicate that documents have missing native or text files when those files actually exist on the file share, you can run the documents through the Indexing and enrichment process, so that Ringtail recognizes them. Ringtail does not identify as missing and files that are associated with a document, but that are later manually deleted from the file share. You can add an Indexing and enrichment job to the case using the Tools menu on the Documents page. For more information, see Index and analyze documents.

Use the following procedure to run quality control checks for a production.

1.On the Case Home page, under Manage Documents, click Productions.

2.In the Productions list, click the name of a production.

3.In the navigation pane, click Quality Control.

4.To select one or more quality control checks, select the check boxes in the Quality control checks column. See the following table for a description of each of the checks.

5.Click Run.

6.Results appear in the Result column. If any exceptions are identified, the results message includes a link to the exception documents. Click the link to view the list of those documents.

7.Click Run, or to see updated results, click Refresh.

Note: You can run checks again to verify any changes that may have been made. The Last date checked column contains the date and time that the check was last run.

The quality control checks are described in the following table.

Quality control check	When the check is enabled	Results
Missing endorsable image files	Documents in the unlocked production are identified to be produced as an endorsable image, as part of either an Endorsable image only or Native with endorsable image population.	Returns successful message if: At least one .tif, .tiff, .jpeg, .jpg, .bmp, .png or .pdf file (if PDF annotations is enabled) exists in the main_pages table for each document to be produced as an image. Returns exception message if: Any documents to be produced as an image do not have an endorsable image file in the main_pages table, or an endorsable image file is not available to be produced after file extension filters and page deletions are applied.
Missing required page information	Documents in the production are identified to be produced as Endorsable image only or Native with endorsable image and do not have the page information that is required to produce image files.	Returns successful message if: No document in the unlocked production is missing page information that is required to produce image files. Returns exception message if: Any document in the unlocked production is missing page information that is required to produce image files, or Ringtail cannot access that information (for example, if the document is encrypted).
Missing content files (extracted text, then .txt)	The option to include text files is selected and the Content file (.txt) = Extracted text, and then .txt file rule is selected.	Returns successful message if: All documents coded to the production have extracted text saved in the database for populations that Ringtail identified as having "extracted text, then .txt". Returns exception message if: Any documents have a .txt file associated with the base document but they do not have extracted text saved in the database for populations that Ringtail identified as having "extracted text, then .txt." Any documents do not have extracted text saved in the database and also do not have a .txt file associated with the base document for populations that Ringtail identified as having "extracted text, then .txt." Note: This check validates the existence of extracted text or a .txt file for all documents in this content rule. It does not take into account any requirements around redactions or excluding .txt files for documents with redactions.
Missing content files (extracted text)	The option to include text files is selected with at least one rule set to Content file (.txt) = Extracted text only.	Returns successful message if: All documents coded to the production have extracted text saved in the database for populations that Ringtail identifies as having extracted text only. Returns exception message if: No extracted text is saved in the database for any documents in populations that Ringtail identifies as having extracted text only. Note: This check validates the existence of extracted text for all documents in this content rule. It does not take into account any requirements around redactions or excluding .txt files for documents with redactions.
Missing content files (.txt from base document)	The option to include text files is selected with at least one rule set to Content file (.txt) = Text from base document only.	Returns successful message if: All documents coded to the production have a .txt file associated with them in the main_contentFile table for populations that Ringtail identified as having text from base documents only. Returns exception message if: No .txt files are associated with documents in the main_contentFile table for populations Ringtail identified as having text from base documents only. Note: This check validates the existence of a .txt file for all documents in this content rule. It does not take into account any requirements around redactions or excluding .txt files for documents with redactions.
Missing native files	Documents in the unlocked production are identified to be produced as native, as part of either a Native only, Native with placeholder, or Native with endorsable image population	Returns successful message if: At least one file is associated with all documents to be produced natively in the main_contentFile table. Returns exception message if: Any documents to be produced natively do not have an associated file in the main_contentFile table, or the only file in the main_contentFile table is a .txt file and the user selected the option to Omit Native if only available file is *.txt file. Note: This check does not identify a document as missing a native file if the document is in a population to be produced natively, and that document has a redaction or highlight that is selected to be applied in the production.
Missing value in field chosen for native extension information	Documents in the unlocked production are identified to be produced as native as part of either a Native only, Native with placeholder, or Native with endorsable image population, AND a field is selected to identify the native file	Returns successful message if: All documents to be produced natively have a value in the field selected to identify the native file. Returns exception message if: Any documents to be produced natively have no value in the field selected to identify the native file. Note: This is only a check to confirm that a value exists in the field. It does not verify that the value matches a file associated with the document.
Overlapping exception rule populations	Documents in the unlocked production exist in more than one production rule population.	Returns successful message if: No document in the unlocked production appears in more than one exception rule population. Returns exception message if: Any document in the unlocked production appears in more than one exception rule population.
To be produced natively but have annotations applied on images	Documents in the unlocked production are identified to be produced as native, either as part of the Native only, Native with endorsable image, or Native with placeholder populations, AND redactions or highlights are applied in the production.	Returns successful message if: None of the documents to be produced natively contain a highlight or redaction that is applied to the production. Returns exception message if: At least one of the documents to be produced natively contains a highlight or redaction that is applied to the production. Note: This check does not consider whether the user selects the Omit Native if document is redacted setting.

top