The Root Node

The root node has four categories of properties, XML, Harvester, Import and Information. The XML properties define the XML output files, the harvester properties define how the information is harvested, the import properties define how data is imported and finally, the information properties give a short description of the model. The root node is basically a query node, with some additional properties. The root node can contain Query Nodes, Placeholders and Leaves. Right click on the root node to add child nodes.

The XML properties

Image 1, the root node Xml properties.

Creation
Max Occurrences	You may specify the maximum number of times the node may occur in the export. This information is used when generating an XSD file for your model. The default value is Unbounded.
Min Occurrences	You may specify the minimum number of times the node may occur in the export. This information is used when generating an XSD file for your model. The default value is Zero.
Type	Auto (default): The element is created at export as a result of harvesting. Manual: The element/attribute or any sub elements/attributes will not be created at export as a result of harvesting, but can optionally be added at a later time by e.g. a post processor or a leaf data parser. Manually added elements/attributes may be used to define import jobs.
Export Header
Elements	Create your own custom export header. You can add a list of name-value-pairs to your export. This could include information about the source system, the purpose of the export etc.
Export Rules
Embed Custom Export Header	Select “true” to embed the Custom Export Header in the xml export.
Embed Marshal Structure	Embed the Marshal model in the xml export. The Marshal model must be embedded if you intend to use the export files to import data.
Export Folder Naming	Rules for designing the created folder tree at export and for naming of the export folders. If folder naming is not enabled, the export will result in one export file. If folder naming is enabled, one Xml file will be created for each row returned by the root node harvester.
Other Namespaces
Custom Namespaces	You can supply additional namespaces to use in the export.
Use XLink for file references	If true, the http://www.w3.org/1999/xlink namespace is referenced, and the xlink-prefix is available for your elements and attributes. If you right-click on a "blob leaf", you are given the option to create a file element, please see the Parent Harvester article for more information.
Use XMLSchema-instance nil	If true, the http://www.w3.org/2001/XMLSchema-instance namespace is referenced and xsi:nil=true is used for null-value elements. If false, prefix:Isnull=true is used for null-value elements, where prefix is the selected prefix for the export.
XML
Element	The name of the Xml Element in the resulting XML document.
Export	Specify whether the node should be saved to the Xml document. Setting the property to false means that the data of the node is available during execution, e.g. for relations and data processors, but it will not be exported to XML.
Namespace	The namespace URI for the default namespace to use for the model.
Prefix	The default namespace prefix of the xml export. The field may be left empty.
Root element	Xml documents must have one, and only one, root element in order to be valid. If you export to one export file, then you must specify a root element. For multiple export files, the value of the Element property, as specified above, will become the root node in each export file.

The Harvester properties

The Harvester combo box item is named after the currently selected harvester. The default harvester is the ODBC database harvester, i.e. when you create a Query-node, an ODBC database harvester is automatically added to the node. All harvesters have their own set of properties, please see the Harvesters article for information about the different harvesters and their respective properties.

Image 2, the root node Harvester properties.

The Import properties

Import rules can be added to all query nodes, including the root node. This means that every query node can have rules for importing information to one or more databases. To add Import Rules for a Query Node, click on the Import Rules property for the node and click on the ellipsis button. For more information, please read the Import article.

Image 3, the root node Import properties.

The Information properties

Image 4, the root node Information properties.

Model Information
Created By	The user account that created the model.
Created Date	The date and time of creation of the model.
Description	In this property you may enter a description of your model.
Edited By	The user account that last edited the model.
Edited Date	Date and time of last modification.
Identifier	A unique identifier of the model.