Field Mapping (Concept): Difference between revisions

Revision as of 10:46, 25 September 2023

Field Mapping allows users to create logical connections between metadata content in Grooper and an external storage platform.

For example, field mappings can be created between data elements in a data model in Grooper and corresponding metadata fields in an external content management system. A Data Field capturing an invoice document's invoice number could be mapped to a field in the content management system named "Invoice Number". After those data fields are extracted from a document set, when the documents are exported their information will populate the mapped fields in the content management system.

Field mappings can be used for both import and export operations. Document metadata from an external storage platform can be imported via field mappings as well as exported.

For more information on Export Mappings, please visit the following articles:

@@ Line 7: / Line 7: @@
 Field mappings can be used for both import and export operations.  Document metadata from an external storage platform can be imported via field mappings as well as exported.
-== Version 2021 ==
+For more information on '''''Export Mappings''''', please visit the following articles:
+* [[Data Export]]
+* [[CMIS Export]]
-More in depth explanations of how to set up field mappings to export extracted data are present in the '''''[[Data Export]]''''' and '''''[[CMIS Export]]''''' articles.
+<!---
+EDITORS NOTE:  I've commented out the rest of this article because it is out of date, old, and unhelpful.
 == Version 2.72 ==