2024:Tab Marking (Property) - Revision history

Dgreenwood at 13:29, 28 August 2025

2025-08-28T13:29:13Z

← Older revision		Revision as of 08:29, 28 August 2025
Line 66:		Line 66:
	<big>Where to Begin</big>		<big>Where to Begin</big>

	'''''Tab Marking''''' is enabled within the '''''Preprocessing''''' grouping of properties. '''''Preprocessing''''' is used all over '''Grooper''', but is most easily associated with '''''~~Extractor Types~~''''' like '''''Pattern Match''''' or '''''List Match'''''.		'''''Tab Marking''''' is enabled within the '''''Preprocessing''''' grouping of properties. '''''Preprocessing''''' is used all over '''Grooper''', but is most easily associated with '''''Value Extractors''''' like '''''Pattern Match''''' or '''''List Match'''''.

	# Right-click on your '''Project''', or a folder within the '''Project'''.		# Right-click on your '''Project''', or a folder within the '''Project'''.
Line 82:		Line 82:


	# <li value=7>Once ~~set to an Extractor Type~~, click the ellipsis button on the '''''Extractor''''' property to open the "Extractor" window.</li>		# <li value=7>Once selected, click the ellipsis button on the '''''Extractor''''' property to open the "Extractor" window.</li>

	[[image:2024_Wiki_Tab-Marking_02_03.png]]		[[image:2024_Wiki_Tab-Marking_02_03.png]]

Dgreenwood: Dgreenwood moved page Tab Marking (Property) to 2024:Tab Marking (Property)

2025-03-02T14:12:02Z

Dgreenwood moved page Tab Marking (Property) to 2024:Tab Marking (Property)

← Older revision	Revision as of 09:12, 2 March 2025
(No difference)

Randallkinard at 15:41, 22 November 2024

2024-11-22T15:41:57Z

← Older revision		Revision as of 10:41, 22 November 2024
Line 139:		Line 139:
	::: For example, consider a document with a table where vertical lines separate the columns, and the values of those columns are close together in physical dimension on the document. By enabling vertical line detection, '''Grooper''' can insert tab characters at these intersections, allowing extractors to more accurately segment and extract data from each column. This feature is beneficial for processing densely populated documents where vertical lines are used to organize information.		::: For example, consider a document with a table where vertical lines separate the columns, and the values of those columns are close together in physical dimension on the document. By enabling vertical line detection, '''Grooper''' can insert tab characters at these intersections, allowing extractors to more accurately segment and extract data from each column. This feature is beneficial for processing densely populated documents where vertical lines are used to organize information.
	</div>		</div>
	~~== Glossary ==~~
	~~<u><big>'''Batch'''</big></u>: {{#lst:Glossary\|Batch}}~~

	~~<u><big>'''Data Type'''</big></u>: {{#lst:Glossary\|Data Type}}~~

	~~<u><big>'''Preprocessing'''</big></u>: {{#lst:Glossary\|Preprocessing}}~~

	~~<u><big>'''Project'''</big></u>: {{#lst:Glossary\|Project}}~~

	~~<u><big>'''Tab Marking'''</big></u>: {{#lst:Glossary\|Tab Marking}}~~

	~~<u><big>'''Value Reader'''</big></u>: {{#lst:Glossary\|Value Reader}}~~

Randallkinard: 2024 updates // via Wikitext Extension for VSCode

2024-11-20T23:02:49Z

2024 updates // via Wikitext Extension for VSCode

Show changes

Randallkinard: // via Wikitext Extension for VSCode

2024-11-20T18:04:35Z

// via Wikitext Extension for VSCode

← Older revision		Revision as of 13:04, 20 November 2024
Line 15:		Line 15:
	However, often, knowing there's a large amount of space one one or both sides of a label or value can be useful information for how to extract that data. The image here has three columns each with pairs of numbers.		However, often, knowing there's a large amount of space one one or both sides of a label or value can be useful information for how to extract that data. The image here has three columns each with pairs of numbers.
	\|		\|
	[[image:2024_Wiki_Tab-Marking_01_01.png\|center~~\|border~~]]		[[image:2024_Wiki_Tab-Marking_01_01.png\|center]]
	\|-		\|-
	\|style="width:50%" valign=top\|		\|style="width:50%" valign=top\|
	You can visually differentiate between the numbers in the second column from the others based on the spatial context around it. The numbers in this columns have a large amount of space on either side between them and the numbers in the other columns.		You can visually differentiate between the numbers in the second column from the others based on the spatial context around it. The numbers in this columns have a large amount of space on either side between them and the numbers in the other columns.
	\|		\|
	[[~~File~~:~~Tab Marking 02~~.png\|center]]		[[image:2024_Wiki_Tab-Marking_01_02.png\|center]]
	\|-		\|-
	\|style="width:50%" valign=top\|		\|style="width:50%" valign=top\|
Line 27:		Line 27:
	As is, it would be cumbersome to write a regex pattern to differentiate between the pairs of numbers (or other "segments" on the page).		As is, it would be cumbersome to write a regex pattern to differentiate between the pairs of numbers (or other "segments" on the page).
	\|		\|
	[[file:~~tab Marking 03~~.png\|center]]		[[file:2024_Wiki_Tab-Marking_01_03.png\|center]]
	\|-		\|-
	\|valign=top\|		\|valign=top\|
	With the '''''Tab Marking''''' property enabled, tab characters are inserted wherever there is a large gap between segments. This is the <code>~~<\t>~~</code> character you now see in the text.		With the '''''Tab Marking''''' property enabled, tab characters are inserted wherever there is a large gap between segments. This is the <code>→</code> character you now see in the text.

	Now, we have a character regular expression can use to pattern match the large white space on either side of the segments in the second column. The tab characters can act as anchors to help us locate what we want on a document.		Now, we have a character regular expression can use to pattern match the large white space on either side of the segments in the second column. The tab characters can act as anchors to help us locate what we want on a document.
	\|		\|
	[[file:~~tab Marking 04~~.png\|center]]		[[file:2024_Wiki_Tab-Marking_01_04.png\|center]]
	\|-		\|-
	\|valign=top\|		\|valign=top\|
Line 44:		Line 44:


	''Note: In the ~~text data~~, the tab character is represented by <code>~~<\t>~~</code>. As far as regex is concerned <code>\t</code> is the way to match this character '''not''' <code>~~<\t>~~</code>. You may also see several spaces after the tab character in the text data. These spaces are there to make the text data more readable, but are not actually part of the text data. You only need to match the tab character.		''Note: In the "Preprocessed Text" view of the Document Viewer, the tab character is represented by <code>→</code>. As far as regex is concerned <code>\t</code> is the way to match this character '''not''' <code>→</code>. You may also see several spaces after the tab character in the text data. These spaces are there to make the text data more readable, but are not actually part of the text data. You only need to match the tab character.
	\|		\|
	[[file:~~tab Marking 05~~.png\|center]]		[[file:2024_Wiki_Tab-Marking_01_05.png\|center]]
	\|}		\|}

Randallkinard: // via Wikitext Extension for VSCode

2024-11-20T17:21:07Z

// via Wikitext Extension for VSCode

← Older revision		Revision as of 12:21, 20 November 2024
Line 15:		Line 15:
	However, often, knowing there's a large amount of space one one or both sides of a label or value can be useful information for how to extract that data. The image here has three columns each with pairs of numbers.		However, often, knowing there's a large amount of space one one or both sides of a label or value can be useful information for how to extract that data. The image here has three columns each with pairs of numbers.
	\|		\|
	[[image:2024_Wiki_Tab-Marking_01_01.png\|center]]		[[image:2024_Wiki_Tab-Marking_01_01.png\|center\|border]]
	\|-		\|-
	\|style="width:50%" valign=top\|		\|style="width:50%" valign=top\|

Randallkinard: // via Wikitext Extension for VSCode

2024-11-20T17:20:24Z

// via Wikitext Extension for VSCode

← Older revision		Revision as of 12:20, 20 November 2024
Line 1:		Line 1:
	{{~~Migrated~~}}		{{AutoVersion}}
	{{2.90:{{~~PAGENAME~~}}}}
			[[File:Tab Marking Icon 5.png\|right\|200px]]

			<blockquote>{{#lst:Glossary\|Tab Marking}}</blockquote>

			The '''''Tab Marking''''' property enables tab characters for regular expression pattern matching. These characters are inserted into a document's text data wherever there is a large gap of space between characters on a line. Space characters are converted to tab characters based on the width of the gap between text characters.
			<br clear=all>

			== About ==
			Normally, a space is a space is a space. Whether a space between characters, a space between columns, or any other space between characters, those spaces are represented by a single space character in a document's text data.

			{\|cellpadding=10 cellspacing=5 style="margin:20px"
			\|style="width:50%" valign=top\|
			However, often, knowing there's a large amount of space one one or both sides of a label or value can be useful information for how to extract that data. The image here has three columns each with pairs of numbers.
			\|
			[[image:2024_Wiki_Tab-Marking_01_01.png\|center]]
			\|-
			\|style="width:50%" valign=top\|
			You can visually differentiate between the numbers in the second column from the others based on the spatial context around it. The numbers in this columns have a large amount of space on either side between them and the numbers in the other columns.
			\|
			[[File:Tab Marking 02.png\|center]]
			\|-
			\|style="width:50%" valign=top\|
			However, with default extractor settings, there's no differentiation between the spaces between words and large spaces between the columns. We call words, phrases, numbers or other data separated by large amounts of space like this "segments".

			As is, it would be cumbersome to write a regex pattern to differentiate between the pairs of numbers (or other "segments" on the page).
			\|
			[[file:tab Marking 03.png\|center]]
			\|-
			\|valign=top\|
			With the '''''Tab Marking''''' property enabled, tab characters are inserted wherever there is a large gap between segments. This is the <code><\t></code> character you now see in the text.

			Now, we have a character regular expression can use to pattern match the large white space on either side of the segments in the second column. The tab characters can act as anchors to help us locate what we want on a document.
			\|
			[[file:tab Marking 04.png\|center]]
			\|-
			\|valign=top\|
			We can now easily create an extractor to return just the pairs of digits in the center column.

			For the '''''Value Pattern''''' we have <code>\d+ \d+</code> to pick up the digits, and the '''''Prefix''''' and '''''Suffix Patterns''''' are using the tab characters as anchors. With '''''Tab Marking''''' enabled, <code>\t</code> in a regex pattern will match the <code><\t></code> inserted into the text data. So, we are only matching pairs of digits, with a tab character before and after them.

			For more information on how to enable and configure the '''''Tab Marking''''' property, visit the [[#How To\|How To]] section of this article.


			''Note: In the text data, the tab character is represented by <code><\t></code>. As far as regex is concerned <code>\t</code> is the way to match this character '''not''' <code><\t></code>. You may also see several spaces after the tab character in the text data. These spaces are there to make the text data more readable, but are not actually part of the text data. You only need to match the tab character.
			\|
			[[file:tab Marking 05.png\|center]]
			\|}

			'''''Tab Marking''''' uses potentially infinite. Essentially, any time you need to match a text segment by anchoring it to a large amount of white space on either side, you will use tab characters in your regex pattern to do so.

			== How To ==

			=== Enable Tab Marking ===

			<tabs style="margin:20px">
			<tab name="Where to Begin" style="margin:20px">
			=== Where to Begin ===

			{\|cellpadding=10 cellspacing=5
			\|style="width:40%" valign=top\|
			'''''Tab Marking''''' is enabled within the '''''Preprocessing''''' grouping of properties. '''''Preprocessing''''' is used all over '''Grooper''', but is most easily associated with '''''Extractor Types''''' like '''''Pattern Match''''' or '''''List Match'''''.

			Notice here, our pattern is not matching anything, even though we have <code>\t</code> in the '''''Prefix''''' and '''''Suffix Patterns'''''. That's because we have not enabled '''''Tab Marking''''' yet. By default, these characters are not inserted into the text data. Since those characters aren't there, the pattern doesn't match.
			\|
			[[File:Tab Marking - How To Enable 01.png]]
			\|}
			</tab>
			<tab name="Enable the Tab Marking Property" style="margin:20px">
			=== Enable the Tab Marking Property ===

			{\|cellpadding=10 cellspacing=5
			\|style="width:40%" valign=top\|
			Once you're on a '''''Pattern Editor''''' in Grooper, you can turn on '''''Tab Marking''''' with the "Properties" tab.

			# Navigate to the "Properties" tab.
			# Expand the '''''Preprocessing Options''''' property.
			# Select the '''''Tab Marking''''' property.
			# Change the property from ''Disabled'' to ''Enabled''.
			\|
			[[File:Tab Marking - How To Enable 02.png]]
			\|}
			</tab>
			<tab name="Verify the Results">
			=== Verify Tab Characters Are Inserted ===

			{\|cellpadding=10 cellspacing=5
			\|style="width:40%" valign=top\|
			With '''''Tab Marking''''' enabled, tab characters replace single spaces in the document's text data wherever there is a long horizontal gap between characters.

			We can see now, our pattern matches. With tab characters on either side of the second column segments, the <code>\t</code> regex in the '''''Prefix''''' and '''''Suffix Pattern''''' now matches, and the digits captured by the '''''Value Pattern''''' <code>\d+ \d+</code> are returned.


			''Note: In the text data, the tab character is represented by <code><\t></code>. As far as regex is concerned <code>\t</code> is the way to match this character '''not''' <code><\t></code>. You may also see several spaces after the tab character in the text data. These spaces are there to make the text data more readable, but are not actually part of the text data. You only need to match the tab character.
			\|
			[[File:Tab Marking - How To Enable 03.png]]
			</tab>
			</tabs>

			=== Configure Tab Marking ===

			== Glossary ==
			<u><big>'''Data Type'''</big></u>: {{#lst:Glossary\|Data Type}}

			<u><big>'''Preprocessing'''</big></u>: {{#lst:Glossary\|Preprocessing}}

			<u><big>'''Tab Marking'''</big></u>: {{#lst:Glossary\|Tab Marking}}

			<u><big>'''Value Reader'''</big></u>: {{#lst:Glossary\|Value Reader}}

Randallkinard: Randallkinard moved page Tab Marking to Tab Marking (Property): new naming convention

2024-04-18T16:39:19Z

Randallkinard moved page Tab Marking to Tab Marking (Property): new naming convention

← Older revision	Revision as of 11:39, 18 April 2024
(No difference)

Dgreenwood: Created page with "{{Migrated}} {{2.90:{{PAGENAME}}}}"

2024-01-03T16:24:26Z

Created page with "{{Migrated}} {{2.90:{{PAGENAME}}}}"

New page

{{Migrated}}
{{2.90:{{PAGENAME}}}}