Default settings: mapping mixed content
|
| Previous Top Next |
Default settings: mapping mixed content |
Creating mixed content connections between items:
| 1. | Select the menu option Connection | Auto Connect matching children to activate this option, if it is not currently activated. |
| 2. | Connect the Desc item in the source schema, with the Desc item in the target schema. |
A message appears, asking if you would like to create a mixed content connection. You are also notified that the text and child items will be transferred in the same order they appear in the XML source file.
| 3. | Click Yes to create a mixed content connector. |
Please note:
Although the Desc element is not of mixed content, a message appears because the auto-connect option has been activated, and para exists in both source and target components. Para is of mixed content, and makes the message appear at this point.
The mixed-content message also appears if you only map the para items directly, without having the autoconnect option activated.
All child items of Desc have been connected. The connector joining the para items is displayed as a dotted line, to show that it is mixed content.
| 4. | Click the Output tab to see the result of the mapping. |
| 5. | Click the word Wrap icon  , to view display the complete text in the Output window. |
The mixed content text of each office description has been mapped correctly; the text, as well as the bold and italic tag content, have been mapped as they appear in the XML source file.
| 6. | Switch back to the Mapping view. |
Removing text nodes from mixed content items:
| 1. | Right click the para connector and select Connection Settings. |
The image shows the default settings when you first create mixed content mapping. The "Map Text content" check box is active per default.
| 2. | Deactivate the Map Text content check box and click OK to confirm. |
| 3. | Click the Output tab to see the result of the mapping. |
Result:
| • | all text nodes of the para element have been removed. |
| • | mapped bold and italic text content remain |
| • | bold and italic item sequence still follow that of the source XML file! |
Text nodes and mixed content mapping:
| • | Text nodes can only be mapped in their entirety; you cannot limit, or transform the data they contain. All text nodes of the para element are either mapped, or excluded, as in the example above. |
| • | Filters, or any other type of function, cannot be used to access text node data. |
| • | Mixed content child node data, i.e. data enclosed in bold/italic tags in this example, can of course be mapped individually. If a connector exists, then the child data will be mapped. |
| • | There is currently no way of accessing the text node(s) of a mixed content element, for further processing, or filtering. |
| • | Right click the para connector and select Connection Settings. |
This opens the Connection Settings dialog box in which you can define the specific (mixed content) settings of the current connector. Note that unavailable options are greyed out.
Please note that these settings also apply to complexType items which do not have any text nodes!
Target Driven (Standard)
Changes the connector type to Standard mapping, please see: "Source-driven / mixed content vs. standard mapping" for more information.
Source Driven (mixed content)
Changes the connector type to source driven / mixed content, and enables the selection of additional elements to be mapped. The additional elements have to be child items of the mapped item in the XML source file, to be able to be mapped.
Annotation settings:
Individual connectors can be labeled for clarity.
| 1. | Double click a connector and enter the name of the connector in the Description field. |
This enables all the options in the Annotation Settings group.
| 2. | Use the remaining groups to define the position and alignment of the label. |
|