Output Extractor Key (Property) - Revision history

Randallkinard at 16:27, 28 August 2024

2024-08-28T16:27:00Z

← Older revision		Revision as of 11:27, 28 August 2024
Line 1:		Line 1:
	{{~~Migrated2023~~}}		{{Migrated}}
	{{2023:{{PAGENAME}}}}		{{2023:{{PAGENAME}}}}

Randallkinard: Randallkinard moved page Output Extractor Key to Output Extractor Key (Property): new naming convention

2024-04-16T21:26:16Z

Randallkinard moved page Output Extractor Key to Output Extractor Key (Property): new naming convention

← Older revision	Revision as of 16:26, 16 April 2024
(No difference)

Dgreenwood: Removed redirect to Output Extractor Key - 2023

2023-12-28T18:34:33Z

Removed redirect to Output Extractor Key - 2023

← Older revision		Revision as of 13:34, 28 December 2023
Line 1:		Line 1:
	~~#REDIRECT [[Output Extractor Key -~~ 2023]]		{{Migrated2023}}
			{{2023:{{PAGENAME}}}}

Rpatton: Redirected page to Output Extractor Key - 2023

2023-10-24T19:43:17Z

Redirected page to Output Extractor Key - 2023

Show changes

Dgreenwood at 18:09, 12 December 2022

2022-12-12T18:09:41Z

← Older revision		Revision as of 13:09, 12 December 2022
Line 103:		Line 103:

	[[Category:Articles]]		[[Category:Articles]]
			[[Category:Version 2.90]]

Dgreenwood at 18:09, 12 December 2022

2022-12-12T18:09:18Z

← Older revision		Revision as of 13:09, 12 December 2022
Line 102:		Line 102:
	If you would like a completed version of content linked above, and walked through in this article to compare against yours you can download it [[Media:Output_Extractor_Key_complete.zip\|here]]. ''This file was exported from and meant for use in Grooper 2.9''		If you would like a completed version of content linked above, and walked through in this article to compare against yours you can download it [[Media:Output_Extractor_Key_complete.zip\|here]]. ''This file was exported from and meant for use in Grooper 2.9''

	[[Category:~~Article~~]]		[[Category:Articles]]

Dgreenwood at 20:22, 9 December 2022

2022-12-09T20:22:09Z

← Older revision		Revision as of 15:22, 9 December 2022
Line 101:		Line 101:
	<br/>		<br/>
	If you would like a completed version of content linked above, and walked through in this article to compare against yours you can download it [[Media:Output_Extractor_Key_complete.zip\|here]]. ''This file was exported from and meant for use in Grooper 2.9''		If you would like a completed version of content linked above, and walked through in this article to compare against yours you can download it [[Media:Output_Extractor_Key_complete.zip\|here]]. ''This file was exported from and meant for use in Grooper 2.9''

			[[Category:Article]]

Dgreenwood at 19:58, 23 October 2020

2020-10-23T19:58:45Z

← Older revision		Revision as of 14:58, 23 October 2020
Line 1:		Line 1:
	[[File:Output_extractor_key_000.png\|right]]		[[File:Output_extractor_key_000.png\|right]]

	<blockquote style="font-size:14pt">Also known as "feature tagging", this is another weapon in the arsenal of powerful '''Grooper''' classification techniques.</blockquote>		<blockquote style="font-size:14pt">Also known as "feature tagging" or "data tagging", this is another weapon in the arsenal of powerful '''Grooper''' classification techniques.</blockquote>

	A '''[[Content Model]]''' and accompanying '''[[Batch]]''' for what will be built can be found '''[[Media:Output_Extractor_Key.zip\|here]]'''. It is not required to download to understand this article, but can be helpful because it can be used to follow along with the content of this article. ''This file was exported from and meant for use in Grooper 2.9''		A '''[[Content Model]]''' and accompanying '''[[Batch]]''' for what will be built can be found '''[[Media:Output_Extractor_Key.zip\|here]]'''. It is not required to download to understand this article, but can be helpful because it can be used to follow along with the content of this article. ''This file was exported from and meant for use in Grooper 2.9''

Dgreenwood: /* How To */

2020-10-23T19:58:18Z

How To

← Older revision		Revision as of 14:58, 23 October 2020
Line 38:		Line 38:
	\|}		\|}
	</tab>		</tab>
	<tab name="Configuring the '~~Data~~ Tagging' Extractor" style="margin:25px">		<tab name="Configuring the 'Feature Tagging' Extractor" style="margin:25px">
	====Configuring the '~~Data~~ Tagging' Extractor====		====Configuring the 'Feature Tagging' Extractor====
	{\| class="wikitable"		{\| class="wikitable"
	\| style="padding:25px; vertical-align:center; width:35%" \|		\| style="padding:25px; vertical-align:center; width:35%" \|

Dgreenwood at 19:56, 23 October 2020

2020-10-23T19:56:42Z

← Older revision		Revision as of 14:56, 23 October 2020
Line 6:		Line 6:

	==About==		==About==
	'''''Output Extractor Key''''' is a property on a the '''[[Data Type]]''' extractor. It is exposed when the '''''[[Collation]]''''' property is set to ''Individual''. When the '''''Output Extractor Key''''' is set to ''True'', each output value will be set to a key representing the name of the extractor which produced the match. It is useful when extracting non-word classification features.		'''''Output Extractor Key''''' is a property on a the '''[[Data Type]]''' extractor. It is exposed when the '''''[[Collation Provider\|Collation]]''''' property is set to ''Individual''. When the '''''Output Extractor Key''''' is set to ''True'', each output value will be set to a key representing the name of the extractor which produced the match. It is useful when extracting non-word classification features.
	<br/><br/>		<br/><br/>
	The main purpose of this property is to supplement the capabilities of '''Grooper's''' classification technology. When using ''Lexical'' classification, a '''Content Model''' must use an extractor to collect the lexical features upon training. A common use case is to have the extractor collect words, which is beneficial when the semantic content of a document is varied among examples, and indicative of their type. However, this breaks down when a document consists mainly of repeated types of information. Take, for example, a bank statement. With no keywords present on the document, the only way to properly classify the document is to recognize that it contains a high frequency of transaction line items. It would be highly impractical to train '''Grooper''' to understand every variation of a transaction line item.		The main purpose of this property is to supplement the capabilities of '''Grooper's''' classification technology. When using ''Lexical'' classification, a '''Content Model''' must use an extractor to collect the lexical features upon training. A common use case is to have the extractor collect words, which is beneficial when the semantic content of a document is varied among examples, and indicative of their type. However, this breaks down when a document consists mainly of repeated types of information. Take, for example, a bank statement. With no keywords present on the document, the only way to properly classify the document is to recognize that it contains a high frequency of transaction line items. It would be highly impractical to train '''Grooper''' to understand every variation of a transaction line item.