Manually Validate Extracted Data: Extraction Validation

Introduction

The Extraction Validation user interface is a central component of the Parashift Platform App. You use it to manually validate automatically extracted data and to train new fields. It’s designed to be easy to use for casual users while also catering to power users. This article provides insights into the different components and best practices for using Extraction Validation.

Overview

The interface can be divided into the following five areas:

1. Breadcrumbs

Displays some document information, such as:

1. The path to the menu from which Extraction Validation was opened (clickable for quick navigation).
2. The document ID or document name, with the ability to change the document name.

2. Actions

Shows the document type and the available actions for a document.

1. Document Type – Displays the current document type.
2. Back – Returns to the list from which the user entered Extraction Validation or the main Extraction list.
3. Switch between Single and Serial mode – See Serial Mode in-depth explanation.
4. Secondary Actions – See Done, Save, Force-Done, and Forwarding to 1st/2nd/3rd Level.
5. Finish Validation – This button is only active when all fields are properly validated (see Done, Save, Force-Done, and Forwarding to 1st/2nd/3rd Level).

3. Viewer

Allows you to view the document, navigate through pages, and more:

1. Page Navigation – Skim through pages or jump to the beginning or end of the document.
2. Rotation – If preprocessing didn’t rotate your document correctly, rotate it manually.
3. Zoom In/Out – Zoom in or out for a closer look.
4. Ruler – Useful when validating pages with many line items; helps keep track of your position.
   
   • Help – Lists shortcuts for features that are handy during validation.

4. Editor

Displays all extracted data and, together with the Info-Box/Field section, forms one of the most important parts of Extraction Validation.

Displays all extracted data and, together with the Info-Box/Field section, forms one of the most important parts of Extraction Validation.

Fields are grouped into Sections and Field Sets. The layout, size, and section names are either preconfigured (when using our standard document types) or customized by an administrator. The Field Editor uses lazy loading, ensuring fast and reliable performance even with large amounts of data.

For a full explanation of the functionality, see the Editor in combination with the Info Box – Field tab further down in this article.

5. Info-Box

Document

Provides general information about the document, such as the document owner, document type, recognized language, average recognition confidence, and relevant upload parameters and dates.

Hover over any title or data point for a more in-depth description.

 

Field

This tab opens by default when navigating through fields. Together with the Field Editor, it’s one of the most important screens in Extraction Validation. You’ll find:

All the details about field validation can be found further down.

1. A preview of the selected value on the document (useful for quickly comparing the read value to the actual text in case of low OCR confidence).
2. Field status and any open error or warning messages.
3. Prediction Confidence – How sure the machine is that it predicted the correct value. If a user manually picked the value, a user icon appears.
   
   
4. Recognition Confidence – How sure the machine is that it read the value correctly (OCR/Barcode, etc.). If a user manually corrected the value, a user icon appears
   
   

Deep Dive: Difference between Recognition and Prediction

 

Flags

Change whether the document should be part of the general training pool or mark a document as unprocessable.

Comments

Leave a comment on the document or read comments from other users. If a document has comments, a small notification bubble appears on this tab.

Field Validation – Status, Warnings & Errors

Refer to the Editor and Info Box – Field tabs above for an overview.

A field generally has three different states

• Valid (Green or Deactivated Look)

  • Fields are valid if configured thresholds are met (e.g., predicted with high confidence), the field is optional, or it’s already validated. They appear in gray to indicate they don’t need attention.

• Warnings (Yellow)

  • Fields with warnings need user action or confirmation.

• Errors (Red)

  • Fields with errors always require manual user interaction and cannot be confirmed without resolving the issue.

Valid

The platform distinguishes between automatically valid fields (no user interaction) and valid fields that required user interaction (validated).

Warning

A field can have one or more warnings. Each warning must either be corrected (value changed) or confirmed (by pressing ENTER). The Info Box provides a detailed description of the active warning.

Once confirmed, the warning remains visible in green to indicate it was present but acknowledged by a user.

Most Common Warnings

Error

A field can have one or more errors, each of which must be resolved by correcting the value. The Info Box provides a detailed description of the active error.

Most Common Errors

Navigation

General

The jump order goes from top-right to bottom-left.

On Opening

When opening a document, focus is on the first invalid field; valid fields are skipped.

Mouse Navigation (For Casual Users)

You can click any field in the Editor to edit it.

Keyboard Navigation (For Power Users)

Press ENTER to move to the next invalid field, skipping valid fields so you can focus on fields that need attention. If there are no more invalid fields, you can press ENTER again to finish Validation.

Although you can also navigate with TAB, it does not consider the field state.

End of Document

When you reach the end of the document:

• If any warnings/errors remain, focus returns to the first invalid field.
• If no invalid fields remain, a pop-up indicates that validation is complete. Press ENTER again to end Validation. Depending on Single or Serial mode, the next document either opens immediately or the list view loads.