2023:List Match (Value Extractor): Difference between revisions

From Grooper Wiki
No edit summary
No edit summary
Line 34: Line 34:
If the information you need to extract follows a specific pattern, such as a date or social security number, then it may be better to consider a different extractor like a '''''[[Pattern Match]]'''''.  
If the information you need to extract follows a specific pattern, such as a date or social security number, then it may be better to consider a different extractor like a '''''[[Pattern Match]]'''''.  


===Configuring by Object Type===


===Configuring by Object Type===


<tabs>
<tabs style="margin:20px">


<tab Name="Configuring on a Value Reader">
<tab Name="Configuring on a Value Reader" style="margin:20px">
{|cellpadding=10 cellspacing=5
{|cellpadding=10 cellspacing=5
|valign=top style="width:40%"|
|valign=top style="width:40%"|
Line 53: Line 53:
</tab>
</tab>


<tab Name="Configuring on a Data Type">
<tab Name="Configuring on a Data Type" style="margin:20px">
# In your '''Node Tree''', right click and create a '''Data Type'''(if you have not already created one).  
{|cellpadding=10 cellspacing=5
# Select the '''Data Type''' object to bring up its configuration properties.  
|valign=top style="width:40%"|
# In your '''Node Tree''', create or select a '''Data Type'''.
#* Visit the [[Data Type]] Wiki Page for instructions on how to create a '''Data Type'''.
# Select the ''Data Type'' tab.
# Select the ''Data Type'' tab.
# Click the drop down list next to ''Local Extractor'' and select '''''List Match'''''.  
# Click the drop down list next to ''Local Extractor'' and select '''''List Match'''''.  


|
[[File:2023-List Match-How To 02.png]]
|}
</tab>
</tab>


Line 67: Line 73:
A '''''List Match''''' can be configured using a '''''Local Entry''''' or a '''''Lexicon'''''. '''''Local Entries''''' are simple and easy to set up, especially if you only need to add a few entries. If you plan to extract a large amount of information multiple times across different objects, it might be more efficient to set up a '''''Lexicon''''' to reference first.  
A '''''List Match''''' can be configured using a '''''Local Entry''''' or a '''''Lexicon'''''. '''''Local Entries''''' are simple and easy to set up, especially if you only need to add a few entries. If you plan to extract a large amount of information multiple times across different objects, it might be more efficient to set up a '''''Lexicon''''' to reference first.  


<tabs>
<tabs style="margin:20px">


<tab Name="Configuring Local Entries">
<tab Name="Configuring Local Entries" style="margin:20px">
{|cellpadding=10 cellspacing=5
{|cellpadding=10 cellspacing=5
|valign=top style="width:40%"|
|valign=top style="width:40%"|
Line 75: Line 81:
|-
|-
|valign=top style="width:40%"|
|valign=top style="width:40%"|
# Save and select the "Tester" tab making sure the ''Expressions'' sub-tab is selected.
# Select the object you wish to configure and click "Tester" tab.
#* When configuring a '''Data Type''', first click the ellipsis button next to your ''List Match'' selection to bring up the editing window.
# Make sure the ''Expressions'' sub-tab is selected.
 
|
[[File:2023-List Match-How To 03.png]]
 
|-
|valign=top style="width:40%"|
# Under '''''LOCAL ENTRIES''''', type the desired text to be extracted.  
# Under '''''LOCAL ENTRIES''''', type the desired text to be extracted.  
#* Hit Enter after each entry to extract multiple text segments under one ''List Match''.  
#* Hit Enter after each entry to extract multiple text segments under one ''List Match''.  
#* If needed, add a '''''Prefix''''' and '''''Suffix Pattern''''' to anchor your extraction (When using tabs as an anchor (<code>\t</code>) make sure ''Tab Marking'' is set to Enabled under ''Preprocessing'' in your ''Properties'' tab).
# If needed, add a '''''Prefix''''' and '''''Suffix Pattern''''' to anchor your extraction.
#*When using tabs as an anchor (<code>\t</code>) make sure ''Tab Marking'' is set to Enabled under ''Preprocessing'' in your ''Properties'' tab.
# Save and test your extraction.
# Save and test your extraction.


|
|
[[File:List Match Steps 5 and 6.png]]  
[[File:2023-List Match-How To 04.png]]  


|}  
|}  
</tab>
</tab>


<tab Name="Referencing Lexicons">
<tab Name="Referencing Lexicons" style="margin:20px">
# In your '''Node Tree''', right click and create the desired object such as a '''Data Type''' or '''Value Reader'''.  
# In your '''Node Tree''', right click and create the desired object such as a '''Data Type''' or '''Value Reader'''.  
# Select the created object to bring up its configuration properties.  
# Select the created object to bring up its configuration properties.  

Revision as of 12:11, 23 January 2023

WIP

This article is a work-in-progress or created as a placeholder for testing purposes. This article is subject to change and/or expansion. It may be incomplete, inaccurate, or stop abruptly.

This tag will be removed upon draft completion.

A List Match is an extractor type that can be used when configuring several data extraction tools such as a Value Reader or Data Type. It is designed to return values matching one or more items in a defined list. By default, the List Match extractor does not use or require regular expressions (regex).

About

The List Match is one of the the simplest extractors used in Grooper. It is designed to return values matching one or more items in a defined list. This can be used to extract numbers, specific words, or full phrases contained within a document. A List Match extractor returns an exact match including any spaces, numbers, punctuation, or special characters.

To configure a List Match, you can input the desired extracted value as a Local Entry or reference a pre-configured Lexicon.

Unlike a Pattern Match, the List Match extractor does not use or require regular expressions by default, but regex can be enabled in the properties menu. Similar to a Pattern Match, Suffix and Prefix Patterns can be added to help anchor the expression and limit the amount of false positives extracted.

How To

A List Match is most commonly used when configuring objects such as Value Readers or Data Types. It is great for extracting text information such as:

  • Specific company names
  • Field labels
  • Headers and Footers
  • Full phrases
  • Exact numbers

If the information you need to extract follows a specific pattern, such as a date or social security number, then it may be better to consider a different extractor like a Pattern Match.

Configuring by Object Type

  1. In your Node Tree, create or select a Value Reader.
    • Visit the Value Reader Wiki Page for instructions on how to create a Value Reader.
  2. Select the "Value Reader" tab.
  3. Click the drop down list next to Extractor and select List Match.

  1. In your Node Tree, create or select a Data Type.
    • Visit the Data Type Wiki Page for instructions on how to create a Data Type.
  2. Select the Data Type tab.
  3. Click the drop down list next to Local Extractor and select List Match.

Local Entries vs Lexicons

A List Match can be configured using a Local Entry or a Lexicon. Local Entries are simple and easy to set up, especially if you only need to add a few entries. If you plan to extract a large amount of information multiple times across different objects, it might be more efficient to set up a Lexicon to reference first.

  1. Select the object you wish to configure and click "Tester" tab.
    • When configuring a Data Type, first click the ellipsis button next to your List Match selection to bring up the editing window.
  2. Make sure the Expressions sub-tab is selected.

  1. Under LOCAL ENTRIES, type the desired text to be extracted.
    • Hit Enter after each entry to extract multiple text segments under one List Match.
  2. If needed, add a Prefix and Suffix Pattern to anchor your extraction.
    • When using tabs as an anchor (\t) make sure Tab Marking is set to Enabled under Preprocessing in your Properties tab.
  3. Save and test your extraction.

  1. In your Node Tree, right click and create the desired object such as a Data Type or Value Reader.
  2. Select the created object to bring up its configuration properties.
  3. In the Value Reader tab, click the drop down list next to Extractor and select List Match.
  4. Save and select the Tester tab. Then make sure the Properties sub-tab is selected.
  5. Click the arrow next to Vocabulary to access additional properties.
  6. Click the ellipsis button next to the Included Lexicons property. This should open a new window where you can add pre-configured Lexicons.
  7. In the new window, click through the Projects and Folders until you find the desired Lexicon. Click the check boxes next to the desired Lexicons.
  8. Click OK to apply the Lexicon.
  9. Save and test your extraction.


See Also