XML Metadata

Specifies the file extension (such as .xml) for the exported metadata file.

• By default, this is set to .xml.
• You may change this if your workflow or target system requires a different extension.

> Tip:
> Choose an extension that matches the expectations of downstream systems or users.

When enabled, the exported XML will use the legacy Grooper structure for compatibility with older systems.

• Set to true to generate legacy XML.
• Set to false to use the modern, schema-driven XML format.

> Note:
> The 'Include Parents' property is not available when using the legacy format.

When enabled, the exported XML will include metadata from parent documents or folders, providing additional context.

What is Parent Data?

"Parent data" refers to data elements belonging to a parent Content Type in a hierarchical batch structure. This relationship is established using the 'Child Of' property on a Content Type. When a Content Type is configured as a child of another, its exported metadata can include data from its parent and ancestor folders/documents.

For example, if you have a batch structure like:

• Personnel File (parent Content Type)
  • Employee_ID (field on Personnel File)
  • Employee_Name (field on Personnel File)
  • Benefits Change Form (child Content Type, with 'Child Of' set to Personnel File)
    • Request_Date (field on Benefits Change Form)
    • Change_Reason (field on Benefits Change Form)

Enabling 'Include Parent Data' on the export format for 'Benefits Change Form' will include both its own fields and the parent Personnel File's fields (such as Employee_ID and Employee_Name) in the exported metadata.

How to Configure Parent Data

1. In your Content Type configuration, set the 'Child Of' property to establish the parent-child relationship between content types.
2. When exporting metadata, enable 'Include Parent Data' to include data from the parent and ancestor folders/documents as defined by the batch structure and content type hierarchy.

> Tip:
> Use this option for multi-level batch structures where child documents need to reference or include data from their parent folders or documents. Be aware that enabling this may introduce additional fields into the export, which should be considered for downstream integration.