Field Mapping (Concept): Difference between revisions

From Grooper Wiki
No edit summary
m Randallkinard moved page Field Mapping to Field Mapping (Concept): new naming convention
(No difference)

Revision as of 10:32, 17 April 2024

"Field mappings" allow users to create logical connections between metadata content in Grooper and an external storage platform.

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 can be used for both import and export operations.

  • 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:

For more information on Import Mappings, please visit the following article: