Table of Contents

Search

  1. Preface
  2. Introduction to Data Transformation
  3. Data Processor Transformation
  4. Wizard Input and Output Formats
  5. Relational Input and Output
  6. XMap
  7. Libraries
  8. Schema Object
  9. Command Line Interface
  10. Scripts
  11. Parsers
  12. Script Ports
  13. Document Processors
  14. Formats
  15. Data Holders
  16. Anchors
  17. Transformers
  18. Actions
  19. Serializers
  20. Mappers
  21. Locators, Keys, and Indexing
  22. Streamers
  23. Validators, Notifications, and Failure Handling
  24. Validation Rules
  25. Custom Script Components

Data Transformation User Guide

Data Transformation User Guide

Mapping Content Anchors to Data Holders

Mapping Content Anchors to Data Holders

A
Content
anchor stores the text that it extracts from a source document in a data holder. For example, you might configure a
Content
anchor to store its result in an XML element called
FirstName
. If the
Content
anchor retrieves the text
Jack
, the Parser produces the following output:
<FirstName>Jack</FirstName>
More precisely, you might specify that the anchor should store the retrieved text at the path
/Person/*s/FirstName
, which refers to an element defined in the XML schema. The actual Parser output would be:
<Person> <FirstName>Jack</FirstName> </Person>
On the other hand, suppose that the schema defines
FirstName
as an attribute of the
Person
element. You might map the
Content
anchor to
/Person/@FirstName
. The output would be:
<Person FirstName="Jack" />
You must map to a data holder that has an appropriate data type. For example, do not map
Jack
to an XML element that has an
xs:integer
data type, or to an XML element that has a complex data type containing nested elements. For more information about this rule, see Using Data Types to Narrow the Search Criteria.


Updated September 26, 2018