2.80:Database Lookup (Lookup Specification) - Revision history

Dgreenwood at 15:07, 5 August 2025

2025-08-05T15:07:49Z

← Older revision		Revision as of 10:07, 5 August 2025
Line 1:		Line 1:
			__NOINDEX__
	{{AutoVersion}}		{{AutoVersion}}

Dgreenwood: Dgreenwood moved page 2.80:Database Lookup (Lookup) to 2.80:Database Lookup (Lookup Specification) without leaving a redirect

2024-10-04T20:28:27Z

Dgreenwood moved page 2.80:Database Lookup (Lookup) to 2.80:Database Lookup (Lookup Specification) without leaving a redirect

← Older revision	Revision as of 15:28, 4 October 2024
(No difference)

Randallkinard at 15:59, 29 April 2024

2024-04-29T15:59:00Z

← Older revision		Revision as of 10:59, 29 April 2024
Line 1:		Line 1:
	{{AutoVersion}}		{{AutoVersion}}
	<blockquote ~~style="font-size~~:~~14pt">~~
	~~'''~~Database ~~Lookups''' are used to populate or validate fields in a '''Data Model''' using an external database, such as a SQL database.~~		<blockquote>{{#lst:Glossary\|Database Lookup}}</blockquote>
	</blockquote>

	For validation, values in a '''Data Field''' are compared to corresponding values in a database table. If the results differ from what’s in the table, that field can be flagged.		For validation, values in a '''Data Field''' are compared to corresponding values in a database table. If the results differ from what’s in the table, that field can be flagged.

Randallkinard: Randallkinard moved page 2.80:Database Lookup to 2.80:Database Lookup (Lookup) without leaving a redirect: new naming convention

2024-04-16T20:11:33Z

Randallkinard moved page 2.80:Database Lookup to 2.80:Database Lookup (Lookup) without leaving a redirect: new naming convention

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

Dgreenwood: Dgreenwood moved page Database Lookup - 2.80 to 2.80:Database Lookup without leaving a redirect

2023-12-28T18:43:08Z

Dgreenwood moved page Database Lookup - 2.80 to 2.80:Database Lookup without leaving a redirect

← Older revision	Revision as of 13:43, 28 December 2023
(No difference)

Dgreenwood at 18:42, 28 December 2023

2023-12-28T18:42:43Z

← Older revision		Revision as of 13:42, 28 December 2023
Line 1:		Line 1:
	~~<onlyinclude>~~		{{AutoVersion}}
	<blockquote style="font-size:14pt">		<blockquote style="font-size:14pt">
	'''Database Lookups''' are used to populate or validate fields in a '''Data Model''' using an external database, such as a SQL database.		'''Database Lookups''' are used to populate or validate fields in a '''Data Model''' using an external database, such as a SQL database.
Line 9:		Line 9:

	The Grooper data fields used for comparison against a database table are called "lookup fields". The fields populated from the database table are called "target fields". A SQL query is used to find the lookup fields and target fields in the database table.		The Grooper data fields used for comparison against a database table are called "lookup fields". The fields populated from the database table are called "target fields". A SQL query is used to find the lookup fields and target fields in the database table.
	~~</onlyinclude>~~

	== About ==		== About ==
Line 421:		Line 420:
	* Supplement - Target fields are populated only if they are empty. If these fields were populated during Extract with other information on the document, they will be left alone.		* Supplement - Target fields are populated only if they are empty. If these fields were populated during Extract with other information on the document, they will be left alone.
	* None - No fields will be populated. This mode is used for validating extracted data against data present in the database.		* None - No fields will be populated. This mode is used for validating extracted data against data present in the database.

	~~[[Category:Articles]]~~
	~~[[Category:Version 2.80]]~~

Dgreenwood: Dgreenwood moved page Database Lookup to Database Lookup - 2.80: Respecting naming convention

2023-06-27T18:33:22Z

Dgreenwood moved page Database Lookup to Database Lookup - 2.80: Respecting naming convention

← Older revision	Revision as of 13:33, 27 June 2023
(No difference)

Dgreenwood at 20:32, 9 December 2022

2022-12-09T20:32:11Z

← Older revision		Revision as of 15:32, 9 December 2022
Line 421:		Line 421:
	* Supplement - Target fields are populated only if they are empty. If these fields were populated during Extract with other information on the document, they will be left alone.		* Supplement - Target fields are populated only if they are empty. If these fields were populated during Extract with other information on the document, they will be left alone.
	* None - No fields will be populated. This mode is used for validating extracted data against data present in the database.		* None - No fields will be populated. This mode is used for validating extracted data against data present in the database.

			[[Category:Articles]]
			[[Category:Version 2.80]]

Dgreenwood at 18:03, 23 November 2020

2020-11-23T18:03:17Z

← Older revision		Revision as of 13:03, 23 November 2020
Line 1:		Line 1:
			<onlyinclude>
	<blockquote style="font-size:14pt">		<blockquote style="font-size:14pt">
	'''Database ~~Lookup~~''' is used to ~~fill~~ or validate fields in a Data Model using an external database, such as a SQL database.		'''Database Lookups''' are used to populate or validate fields in a '''Data Model''' using an external database, such as a SQL database.
	</blockquote>		</blockquote>

	For validation, values in a Data Field are compared to corresponding values in a database table. If the results differ from what’s in the table, that field can be flagged.		For validation, values in a '''Data Field''' are compared to corresponding values in a database table. If the results differ from what’s in the table, that field can be flagged.

	For data population, as long as the values exist in the external database, Grooper extracted values can be used to populate additional Data Fields. Given a certain field or fields in a Data Model matches fields in a database table, additional values in the table’s row can be assigned to empty Grooper Data Fields. For example, an extracted social security number from a document could be used to lookup a corresponding name in database that has both the social security number and name.		For data population, as long as the "lookup values" exist in the external database, Grooper extracted values can be used to populate additional '''Data Fields'''. Given a certain field or fields in a '''Data Model''' matches fields in a database table, additional values in the table’s row can be assigned to empty Grooper Data Fields. For example, an extracted social security number from a document could be used to lookup a corresponding name in database that has both the social security number and name.

	The Grooper data fields used for comparison against a database table are called "lookup fields". The fields populated from the database table are called "target fields". A SQL query is used to find the lookup fields and target fields in the database table.		The Grooper data fields used for comparison against a database table are called "lookup fields". The fields populated from the database table are called "target fields". A SQL query is used to find the lookup fields and target fields in the database table.
			</onlyinclude>

	== About ==		== About ==

Configadmin: /* How To: Perform a Database Lookup for field population */

2019-12-13T16:04:50Z

How To: Perform a Database Lookup for field population

← Older revision		Revision as of 11:04, 13 December 2019
Line 288:		Line 288:
	\|-style="background-color:#ddf5f5"		\|-style="background-color:#ddf5f5"
	\|Our test model, with the Data Table selected.\|\|A preview of our empty data table before extraction.		\|Our test model, with the Data Table selected.\|\|A preview of our empty data table before extraction.
	\|[[file:1574713410861-676.png\|center]]\|\|[[file:1574713513002-331.png\|center]]		\|-style="background-color:#ddf5f5"
			\|[[file:1574713410861-676.png\|center\|250px]]\|\|[[file:1574713513002-331.png\|center\|700px]]
	\|}		\|}

Line 300:		Line 301:


	[[file:1574713792514-291.png\|center]]		[[file:1574713792514-291.png\|border\|center]]


Line 322:		Line 323:


	[[file:1574699272854-690.png\|center]]		[[file:1574699272854-690.png\|border\|center]]


	</tab>		</tab>