Key-Value Pair (Collation Provider): Difference between revisions
Dgreenwood (talk | contribs) |
Dgreenwood (talk | contribs) No edit summary |
||
| Line 133: | Line 133: | ||
This will look for results of the "Value Extractor" and only return the closest ''vertically, below'' the "Key Extractor's" result. But... Something is not right here. What we want to extract is the phone number underneath the "home phone" label directly below it, as seen in the box labeled "Vertical Layout" on the document. | This will look for results of the "Value Extractor" and only return the closest ''vertically, below'' the "Key Extractor's" result. But... Something is not right here. What we want to extract is the phone number underneath the "home phone" label directly below it, as seen in the box labeled "Vertical Layout" on the document. | ||
: 4. The problem is, we're picking up the wrong key. | |||
The "Key Extractor" is set up to return "home phone", which appears three times on this document. The first time it appears is at the time of the page. If you draw a vertical line down from that label, sure enough, there is a phone number there, it's just using the wrong label. | The "Key Extractor" is set up to return "home phone", which appears three times on this document. The first time it appears is at the time of the page. If you draw a vertical line down from that label, sure enough, there is a phone number there, it's just using the wrong label. | ||
| Line 143: | Line 143: | ||
There are two very common ways to do this for ''Key-Value Pair'' Collation, the '''''Maximum Distance''''' and the '''''Enforce Line Boundaries''''' properties. | There are two very common ways to do this for ''Key-Value Pair'' Collation, the '''''Maximum Distance''''' and the '''''Enforce Line Boundaries''''' properties. | ||
: 5a. Both '''''Vertical Layout''''' and '''''Horizontal Layout''''' have a '''''Maximum Distance''''' sub-property. | |||
: 6a. You can set a length here, in inches, points, millimetres or centimetres. If the distance between the key and the value are greater than the length set, that result will be tossed out. | |||
:* Here, we set the distance to ''0.25in''. This threw out the result we were getting because the vertical distance between the first "home phone" label is much longer than 0.25 inches. Then, the extractor looked for the next key value, which does have a vertically aligned value next to it, within 0.25 inches. | |||
:* FYI: With the '''''Maximum Distance''''' property left blank, there is no maximum distance. ''Key-Value Pair'' collation will go from the "Key Extractor's" result all the way down the page looking for the "Value Extractor's" result. However, this will ''not'' span pages. The '''''Horizontal''''' and '''''Vertical Layouts''''' will only look for values next to a key on the same page. | |||
| | | | ||
[[File:Key-Value Pair - Grooper Screenshots 07.png]] | [[File:Key-Value Pair - Grooper Screenshots 07.png]] | ||
|- | |||
| | |||
The other solution to this problem will only be possible if your document utilizes ''lines'' to break up sections or fields. For documents that do this, information is visually divided from other information by putting it in a box. This example also does that. The values horizontally aligned are put in one box. The values vertically aligned are put in another box. Because of this fact, we can take advantage of the '''''Enforce Line Boundaries''''' property. | |||
: 5b. Select the '''''Enforce Line Boundaries''''' property | |||
: 6b. Set this to ''True''. If there is a line physically between the key and the value on the page, that result will be thrown out. | |||
:* Note: We set the '''''Maximum Distance''''' property back to blank. We're not cheating here. | |||
{|cellpadding="10" cellspacing="5" | |||
|-style="background-color:#f89420; color:white" | |||
|style="font-size:14pt"|'''⚠'''||This will only work if the document has line location information in its folder or page's LayoutData.json file. This information must be obtained ''before'' the extractor runs via the [[Image Processing]] or [[Recognize]] activity. | |||
|} | |||
| | |||
[[File:Key-Value Pair - Grooper Screenshots 08.png]] | |||
|} | |} | ||
Revision as of 17:00, 26 August 2020

Key-Value Pair is a Collation Provider for Data Type extractors. It uses the layout relationship between a key and a value on a document to return a result.
Key-Value Pair collation is one of the most commonly used Collation Providers. It provides an excellent way to extract data when a value exists next to a label on a document, whether next to it horizontally, vertically, or even in a "right-to-left & top-to-bottom" text flow.
About
The Key-Value Pair Collation Provider utilizes the spatial relationship between two related extractor results to return a single result, typically looking for a piece of data (the value) next to a label (the key).
|
For structured documents, it is common for a piece of data to be identified by some sort of label, usually to the left of it, or above it. In these images, the field label, highlighted in blue, identifies the field's value, highlighted in yellow. We use this kind of labeling relationship to identify data on documents all the time. The Key-Value Pair Collation Provider is perfectly suited to use these labeling relationships. Key-Value Pair collated Data Types (often just referred to as Key-Value Pairs) collate the results of two extractors, a "key extractor" and a "value extractor". The "key extractor" will locate the label (or whatever context is being used to return the data you want). The "value extractor" will return all possible values matching the data you want to return. Once collated, the Key-Value Pair will return the closest value to the key, according to the assigned Layout Settings (The top image uses a Horizontal Layout because the labels are aligned next to each other horizontally. The bottom uses a Vertical Layout). |
|
Key-Value Pair collation also has applications in unstructured document processing. Unstructured documents convey information in paragraphs and sentences more than they do with structured fields. Because of this, the value may not be horizontally or vertically aligned, but somewhere before or after a labeling key in the text flow. For these situations, the Flow Layout can be used, which will use the relationship between the key and the value in the text data's right-to-left and top-to bottom text flow. A Key-Value Pair could be build to extract the driver name (highlighted here in yellow), using the phrase "driver's name" in the text flow before it. |
How To
Create A Key-Value Pair Extractor
Create a Data Type
Data Type extractors use Collation Providers to combine, filter, or otherwise manipulate extraction results. Collation Providers are set using the Data Type's Collation property.
|
So, the very first thing to do is create a Data Type. Here, we are creating the Data Type in the Local Resources folder of a Content Model.
|
Create the Key Extractor
Key-Value Pair extractors must have exactly two extractors, a "Key Extractor" and a "Value Extractor". The "Value Extractor" is ultimately the value the Key-Value Pair returns. The "Key Extractor" is how you find the value. It's result will be used as a positional anchor to find the value. Our goal with the document seen here is to differentiate between the various "home phone" numbers from the "cell phone" numbers. So, our key extractor simply needs to find the label, "home phone".
|
Create the Value Extractor
For Key-Value Pair extractors, the "Value Extractor" is the extractor looking for the data you ultimately want to return. Here, we're looking for a home phone number. So, we simply need an extractor that finds phone numbers
|
Set the Collation Provider
Once you select Key-Value Pair, you will not see the results list change. It will still appear as if the two child extractors' results are being returned one by one (like the Individual Collation Provider). Some Collation Providers, such as Key-Value Pair, require some configuration before their results are collated. Specifically, you must choose which Layout method is used. |
Configure the Layout Settings
They Layout method will define how the "Key Extractor" and "Value Extractor" results are spatially related to each other. Is the key above the value? Is it to the left of it? The right? Configuring these settings will dictate where you expect to find the value in relation to the key.
The Layout may be:
- Horizontal
- Vertical
- Flow
|
Horizontal Layout
This will look for results of the "Value Extractor" and only return the closest horizontally to the right of the "Key Extractor's" result. None of the other phone numbers on the page are horizontally aligned with the key "home phone'. So, only a single result is returned. |
|
Vertical Layout
This will look for results of the "Value Extractor" and only return the closest vertically, below the "Key Extractor's" result. But... Something is not right here. What we want to extract is the phone number underneath the "home phone" label directly below it, as seen in the box labeled "Vertical Layout" on the document.
The "Key Extractor" is set up to return "home phone", which appears three times on this document. The first time it appears is at the time of the page. If you draw a vertical line down from that label, sure enough, there is a phone number there, it's just using the wrong label. |
|||
|
Coincidentally, this could be the right value you're looking for, but more often than not, this will produce false positive results. Typically, keys are much closer to their values than what we see here. We need a way to restrict the space between the two extractor results to toss out these false positives. There are two very common ways to do this for Key-Value Pair Collation, the Maximum Distance and the Enforce Line Boundaries properties.
|
|||
|
The other solution to this problem will only be possible if your document utilizes lines to break up sections or fields. For documents that do this, information is visually divided from other information by putting it in a box. This example also does that. The values horizontally aligned are put in one box. The values vertically aligned are put in another box. Because of this fact, we can take advantage of the Enforce Line Boundaries property.
|
|
Flow Layout
|









