Field Mapping (Concept) - Revision history

Randallkinard at 19:33, 21 November 2024

2024-11-21T19:33:30Z

@@ Line 30: / Line 30: @@
 * [[Data Export]]
 <!---
@@ Line 107: / Line 88: @@
 When data about the Grooper process itself needs to be exported (user, batch name, statistics, machine name, etc.), these can be mapped to their corresponding database columns using expression-based mapping.
 <!---EDITOR'S NOTE

Dgreenwood: /* Mapping to and from properties in a content management system */

2024-09-18T15:05:51Z

Mapping to and from properties in a content management system

← Older revision		Revision as of 10:05, 18 September 2024
Line 17:		Line 17:


	For more information on '''''Write Mappings''' and '''''Read Mappings''''' on export, refer to the following articles:		For more information on '''''Write Mappings''''' and '''''Read Mappings''''' on export, refer to the following articles:
	* [[CMIS Export]]		* [[CMIS Export]]

Dgreenwood at 15:03, 18 September 2024

2024-09-18T15:03:31Z

← Older revision		Revision as of 10:03, 18 September 2024
Line 3:		Line 3:
	Field mappings are created between Grooper '''Data Elements''' in a '''Data Model''' and corresponding metadata fields in an external content storage platform. For example, a '''Data Field''' capturing an invoice document's invoice number could be mapped to a field in a content management system named "Invoice Number". After Grooper extracts those '''Data Fields''' from a document set, the extracted data is ''mapped'' to fields in the content management system on export.		Field mappings are created between Grooper '''Data Elements''' in a '''Data Model''' and corresponding metadata fields in an external content storage platform. For example, a '''Data Field''' capturing an invoice document's invoice number could be mapped to a field in a content management system named "Invoice Number". After Grooper extracts those '''Data Fields''' from a document set, the extracted data is ''mapped'' to fields in the content management system on export.

			=== Mapping to and from properties in a content management system ===

	Field mappings can be used for both ''import'' and ''export'' operations.		Field mappings can be used for both ''import'' and ''export'' operations, using either '''''Write Mappings''''' or '''''Read Mappings'''''
	* While exporting data from Grooper to an external platform via field mappings is more common, document metadata from an external storage platform can be imported into Grooper via field mappings as well.		:*<li class="fyi-bullet"> While exporting data from Grooper to an external platform via field mappings is more common, document metadata from an external storage platform can be imported into Grooper via field mappings as well.

	For more information on '''''~~Export~~ Mappings''''', ~~please visit~~ the following articles:
	* [[Data Export]]		For import, mappings are defined using an '''''Import Behavior'''''. '''''Read Mappings''''' define what metadata are read ''from'' the import source and mapped to which '''Data Fields''' in Grooper. '''''Write Mappings''''' define what (if any) metadata are written ''back to'' the import source after the import completes.
			:*<li class="fyi-bullet"> Mappings may also be defined by values generated from [[Code Expressions]].


			For export, mappings are defined using an '''''Export Behavior'''''. '''''Write Mappings''''' define what Grooper '''Data Field''' values are written to which metadata properties in the content management system. '''''Read Mappings''''' define what data is read back from the content management system to a Grooper '''Data Field''' (This is uncommon).
			:*<li class="fyi-bullet"> Mappings may also be defined by values generated from [[Code Expressions]].


			For more information on '''''Write Mappings''' and '''''Read Mappings''''' on export, refer to the following articles:
	* [[CMIS Export]]		* [[CMIS Export]]

	For more information on '''''~~Import~~ Mappings''''', please visit the following article:		For more information on '''''Write Mappings''''' and '''''Read Mappings''''' in import, please visit the following article:
	* [[Import Behavior]]		* [[Import Behavior]]

			=== Mapping to a database ===

			Field mapping may also refer to how Grooper extracted data are mapped to a database on export. The '''''Data Export''''' definition's '''''Table Mappings''''' define what '''Data Elements''' values are mapped to which columns in a database table.

			For more information on '''''Table Mappings''''' refer to the following article:
			* [[Data Export]]

	== Glossary ==		== Glossary ==

Dgreenwood at 14:43, 18 September 2024

2024-09-18T14:43:07Z

← Older revision		Revision as of 09:43, 18 September 2024
Line 8:		Line 8:

	For more information on '''''Export Mappings''''', please visit the following articles:		For more information on '''''Export Mappings''''', please visit the following articles:
	* [[Export Behavior]]
	* [[Data Export]]		* [[Data Export]]
	* [[CMIS Export]]		* [[CMIS Export]]

Randallkinard at 13:10, 10 May 2024

2024-05-10T13:10:53Z

@@ Line 14: / Line 14: @@
 For more information on '''''Import Mappings''''', please visit the following article:
 * [[Import Behavior]]
 <!---

Randallkinard at 19:21, 23 April 2024

2024-04-23T19:21:37Z

← Older revision		Revision as of 14:21, 23 April 2024
Line 1:		Line 1:
	~~<section begin="glossary" />~~		<blockquote>{{#lst:Glossary\|Field Mapping}}</blockquote>
	<blockquote>
	"Field ~~mappings" allow users to create logical connections between metadata content in Grooper and an external storage platform.~~
	</blockquote>
	~~<section end="glossary" />~~
	Field mappings are created between Grooper '''Data Elements''' in a '''Data Model''' and corresponding metadata fields in an external content storage platform. For example, a '''Data Field''' capturing an invoice document's invoice number could be mapped to a field in a content management system named "Invoice Number". After Grooper extracts those '''Data Fields''' from a document set, the extracted data is ''mapped'' to fields in the content management system on export.		Field mappings are created between Grooper '''Data Elements''' in a '''Data Model''' and corresponding metadata fields in an external content storage platform. For example, a '''Data Field''' capturing an invoice document's invoice number could be mapped to a field in a content management system named "Invoice Number". After Grooper extracts those '''Data Fields''' from a document set, the extracted data is ''mapped'' to fields in the content management system on export.

Randallkinard: Randallkinard moved page Field Mapping to Field Mapping (Concept): new naming convention

2024-04-17T15:32:30Z

Randallkinard moved page Field Mapping to Field Mapping (Concept): new naming convention

← Older revision	Revision as of 10:32, 17 April 2024
(No difference)

Dgreenwood at 18:25, 9 January 2024

2024-01-09T18:25:39Z

← Older revision		Revision as of 13:25, 9 January 2024
Line 1:		Line 1:
	<section begin="~~field_mapping_glossary~~" />		<section begin="glossary" />
	<blockquote>		<blockquote>
	"Field mappings" allow users to create logical connections between metadata content in Grooper and an external storage platform.		"Field mappings" allow users to create logical connections between metadata content in Grooper and an external storage platform.
	</blockquote>		</blockquote>
	<section end="~~field_mapping_glossary~~" />		<section end="glossary" />
	Field mappings are created between Grooper '''Data Elements''' in a '''Data Model''' and corresponding metadata fields in an external content storage platform. For example, a '''Data Field''' capturing an invoice document's invoice number could be mapped to a field in a content management system named "Invoice Number". After Grooper extracts those '''Data Fields''' from a document set, the extracted data is ''mapped'' to fields in the content management system on export.		Field mappings are created between Grooper '''Data Elements''' in a '''Data Model''' and corresponding metadata fields in an external content storage platform. For example, a '''Data Field''' capturing an invoice document's invoice number could be mapped to a field in a content management system named "Invoice Number". After Grooper extracts those '''Data Fields''' from a document set, the extracted data is ''mapped'' to fields in the content management system on export.

Dgreenwood at 22:01, 5 January 2024

2024-01-05T22:01:51Z

← Older revision		Revision as of 17:01, 5 January 2024
Line 1:		Line 1:
	<section begin="field_mapping_glossary" />		<section begin="field_mapping_glossary" />
	<blockquote>		<blockquote>
	"Field mappings" ~~allows~~ users to create logical connections between metadata content in Grooper and an external storage platform.		"Field mappings" allow users to create logical connections between metadata content in Grooper and an external storage platform.
	</blockquote>		</blockquote>
	<section end="field_mapping_glossary" />		<section end="field_mapping_glossary" />

Dgreenwood at 22:01, 5 January 2024

2024-01-05T22:01:40Z

← Older revision		Revision as of 17:01, 5 January 2024
Line 1:		Line 1:
			<section begin="field_mapping_glossary" />
	<blockquote>		<blockquote>
	"Field mappings" allows users to create logical connections between metadata content in Grooper and an external storage platform.		"Field mappings" allows users to create logical connections between metadata content in Grooper and an external storage platform.
	</blockquote>		</blockquote>
			<section end="field_mapping_glossary" />
	Field mappings are created between Grooper '''Data Elements''' in a '''Data Model''' and corresponding metadata fields in an external content storage platform. For example, a '''Data Field''' capturing an invoice document's invoice number could be mapped to a field in a content management system named "Invoice Number". After Grooper extracts those '''Data Fields''' from a document set, the extracted data is ''mapped'' to fields in the content management system on export.		Field mappings are created between Grooper '''Data Elements''' in a '''Data Model''' and corresponding metadata fields in an external content storage platform. For example, a '''Data Field''' capturing an invoice document's invoice number could be mapped to a field in a content management system named "Invoice Number". After Grooper extracts those '''Data Fields''' from a document set, the extracted data is ''mapped'' to fields in the content management system on export.