Glossary
Search a term:
|
Term |
Definition |
|---|---|
|
@ |
A prefix that need to be used with a required ontology field or a table name for referencing them in an ontology rule. |
|
Anchor |
A value available in a document that provides the spatial reference to an ontology field with respect to itself. |
|
Audit trail |
A trail of activities performed by an authorized user logged for audit purpose. |
|
Baseline |
An activity that measures the accuracy of the extracted data against the golden data. Golden data refers to the data that is considered to be fairly accurate. |
|
Batch of documents |
Often used in context of documents; it represents a set of documents used for the purpose of baselining and training OCR- and ML-based models. |
|
Blacklist profile |
A set of keywords that prevent a document from being taken up for data extraction. |
|
Class library |
A DLL that can be added to the application to include methods for data extraction. |
|
Cleanup |
Refers to rules that are used for cleaning-up extracted data such as removing leading and trailing spaces, etc. |
|
Confidence |
The level of certainty that the OCR system has regarding the accuracy of the recognized characters. The confidence level range is 0-9, where 0 represents least confidence and 9 represents highest confidence. |
|
Copilot |
An ML-based capability for automatically generating ontology. |
|
Data lookup |
An approach in which data is fetched directly from the database rather than using OCR-based extraction, which is comparatively slower and less accurate. |
|
Datasource |
Represents the data stored in a database (either as a static list or as a table) that can be looked-up for populating ontology fields. |
|
Datatable |
A datatable comprises of a table that is generated for a 'Datatable' type ontology field and is populated by looking-up data from the database. |
|
Datatype |
Also referred to as field type, it represents to the nature of an ontology field. It is broadly classified as standard type (numeric, alphanumeric, etc.) and business type (email, website, etc.). |
|
Document category |
Depending on the context, a category may either imply 1) the first level of document categorization or, 2) refer to the labels applied to business keywords for the purpose of source identification. |
|
Document hierarchy |
A document hierarchy in TruCap+ is represented by 'Category', followed by 'Project', and then by 'Subtype'. |
|
Document ontology |
It is a means through which important fields in a document can be identified for the purpose of data extraction. It also defines the methodologies that are to be used for extracting a given field. |
|
Document subtype |
The last level of document categorization after 'Category' and 'Project'. It is usually used to represent the nature of a document set. For example, a subtype may represent an invoice, a report, an insurance form, or something else. |
|
Document template |
A template is a format in which data is arranged in a document. Based on a template, an ontology is defined for the purpose of extracting data from the documents. |
|
Enqueue |
A feature that allows high-priority documents to be processed on-demand by bypassing the queued documents. |
|
Field type |
Also known as datatype, it represents the nature of an ontology field. Ontology fields are broadly classified as standard type (like numeric, alphanumeric, and others) and business type (like email, website, and others). |
|
Footer section |
For extraction purpose, the fields in an ontology are categorized under header, details, and footer sections. The 'details' section generally refers to the document table, and the 'header' and 'footer' sections refer to the document data above and below the table respectively. |
|
Golden data |
Golden data refers to the data that has been manually inspected and quality-checked for accuracy and is used as a benchmark to assess the accuracy of other OCR- and ML-based models. |
|
Header section |
For extraction purpose, the fields in an ontology are categorized under header, details, and footer sections. The 'details' section generally refers to the document table, and the 'header' and 'footer' sections refer to the document data above and below the table respectively. |
|
Heterogeneous documents |
Represents a set of documents belonging to different subtypes like invoice, report, insurance form, etc. |
|
HITL |
Human-in-the-loop (HITL) is a term used to represent human interaction with the data extraction process to provide data for the unextracted fields and doing quality-check on the data. |
|
Image profile |
A set of attribute values that can be applied to an image for improving it's quality (contrast, brightness, etc.) for the purpose of data extraction. |
|
Input source |
The source location where the documents from which the data is to be extracted are kept. TruCap+ offers wide variety of input location choices to its users like FTP, cloud, shared location, etc. |
|
Integrated documents |
Documents belonging to different subtypes clubbed together in an integrated project for business purpose. (Such documents are heterogeneous by nature.) |
|
Integrated project |
A type of project for managing heterogeneous documents. |
|
Keyword annotation |
An activity of providing additional information in regard to logos and business keywords for the purpose of source identification that leads to populating of ontology fields for a give document. |
|
Knowledge Master (KM) |
Knowledge master represents a collection of database tables that represent information about document source (owner) such as name, address, office, etc. This data is used to populate ontology fields after the document source is identified. |
|
Leadtools |
Refers to the LEADTOOLS software development toolkits created by LEAD Technologies, Inc. It is used to integrate functionality such as OCR, barcode recognition, etc. |
|
Logo identification |
Logos are used for source identification that leads to data being fetched from the database rather than being extracted using OCR, which is comparatively slower and less accurate. |
|
Manual handling |
An activity carried out by authorized users to manually inspect the extracted data to add or modify it as per their discretion. |
|
Master data |
A set of data maintained in a database for purpose of populating ontology fields and for verifying the correctness of extracted data. This data is fed manually by an authorized user. |
|
Ontology field |
An ontology field represents the data in a given document that needs to be extracted by using the methodologies defined for it in the ontology. |
|
Ontology rule |
Rules are created to extract data and process it as per the given requirement. Different categories of rules are available like extraction rules, clean-up rules, and so on. |
|
Output file |
A file that contains the extracted data. |
|
Output source |
A location where the output files containing the extracted data are stored. |
|
Primary customer |
Primary customer are official partners of Datamatics that can sell and manage TruCap+ subscriptions. |
|
Project template |
In the context of customized DLLs, a project template defines the interface for an extraction method, which a user can use to define a customized extraction rule. |
|
Published model |
A model that has been trained and approved for the purpose of data extraction and related activities. |
|
Quality check (QC) |
An activity carried out by authorized users to check the correctness of data that has been either programmatically extracted or filled-in by a manual operator. |
|
Queues |
A queue represents one of the several stages of processing in which documents are queued awaiting their turn to get processed. |
|
Regex |
A regex type is a regular expression that is created to identify and extract business data like phone numbers, websites, zip codes, etc. |
|
Region of Interest |
(RoI) is an area that is marked by a user on a document for identifying the region where a data field is most likely to be found. |
|
Source identifier |
Source identification leads to the population of ontology fields by fetching data directly from the database which is relatively faster and more accurate than OCR based extraction. Note: The required Source identifier setting must be enabled. |
|
Synonym |
Synonyms (also known as keywords) are used to represent a group of labels that often appear in a set of documents in vicinity to a relevant data field. By providing a spatial reference in respect to a keyword (like above or below the keyword), it becomes possible to know the position of the data field. For example, 'Number', 'No.', and 'Sno.' are possible synonyms for serial number. |
|
table field |
An ontology table represents the tabular data in a given document that needs to be extracted by using the methodologies defined for it in the ontology. |
|
training workbench |
It is a centralized dashboard which displays the ML models published and available for training. |
|
Template |
A template is a format in which data is arranged in a document. Based on a template, an ontology is defined for the purpose of extracting data from the documents. |
|
UWUC |
Unique word, unique couple' is a principle that states that a document source (owner) can be identified by identifying certain words or a group of words (like phone number, website, etc.) in a document that are unique to a source. Source identification leads to data-lookup from database which is faster than OCR-based extraction. |