Introducción

The UiPath® Document Understanding^TM framework facilitates the processing of incoming files, from file digitization to extracted data validation, all in an open, extensible, and versatile environment.

Document Understanding está diseñado para ayudarte a combinar diferentes enfoques para extraer información de múltiples tipos de documentos. El objetivo principal es facilitar al máximo el proceso de extracción de datos: crear un único flujo de trabajo que extraiga datos de diversos documentos.

Antes de usar el marco de trabajo de Document Understanding, se recomienda entender los siguientes componentes del marco de trabajo de Document Understanding.

• Taxonomía What documents need to be processed and what data is required from them? Used to define the document types and the pieces of information targeted for data extraction (fields) for each document type, and formalizes this information into a dedicated Taxonomy structure. This metadata information is managed through the Taxonomy Manager.
• Digitalización What does this file contain? Used to obtain the textual content and the structure of the incoming document, turning a file into machine-readable content so it can be further processed downstream.
• Clasificación de documentos What types of documents from the taxonomy are found in this file? Used to automatically determine what document types are found within a digitized file.
• Validación de clasificación de documentos Is the predicted classification correct? This is how I can review and correct it. Used for assisting in the human validation and correction of the automatic classification and document splitting results.
• Entrenamiento de la clasificación Did the human review the data? This is how the robot can learn from it. Used to pass the human validated information back to the classifiers, to use it to improve their future predictions.
• Extracción de información What data can be found in this particular document? Used to capture the information required for the identified document type, within the given input document and classification page range.
• Validación de extracción de datos Is the extracted information correct? This is how I can review and correct it. Used for assisting in the human validation and correction of the automatically extracted data results.
• Entrenamiento de extracción de datos Did the human review the data? This is how the robot can learn from it. Used to pass the human validated extracted data back to the extractors, to use it to improve their extraction predictions.
• Data Consumption Used to export the validated data in order to consume it.
• Metering & Charging Logic Used to explain the consumption of units per page for each available service.

El siguiente diagrama presenta los componentes del marco de Document Understanding y cómo se relacionan entre sí:

The Document Understanding framework is found in the UiPath.IntelligentOCR.Activities package. Once the UiPath.IntelligentOCR.Activities package is installed, the Taxonomy Manager wizard appears in the top ribbon of the UiPath Studio. This same package contains all the core document understanding framework activities.

The scope activities (Classify Document Scope, Data Extraction Scope, Train Classifiers Scope, Train Extractors Scope) that are part of the Document Understanding framework allow you to use any document classification and data extraction algorithms that fit your use case and then train these algorithms.

The Document Understanding framework can be used not only with the out-of-the-box classifiers and extractors but also with any custom-built ones. These can be created using the abstract classes from the UiPath.DocumentProcessing.Contracts package and can be implemented as classification or data extraction activities. Custom-built OCR engines can also be created using the abstract classes from the UiPath.OCR.Contracts package.

Recursos

Dedicated Document Understanding courses can be found in the UiPath RPA Academy.

El Foro de UiPath Community es el lugar donde recibir ayuda de nuestra creciente comunidad de usuarios.