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. Using the IntelliScript Editor
  7. XMap
  8. Libraries
  9. Schema Object
  10. Command Line Interface
  11. Scripts
  12. Parsers
  13. Script Ports
  14. Document Processors
  15. Formats
  16. Data Holders
  17. Anchors
  18. Transformers
  19. Actions
  20. Serializers
  21. Mappers
  22. Locators, Keys, and Indexing
  23. Streamers
  24. Validators, Notifications, and Failure Handling
  25. Validation Rules
  26. Custom Script Components

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 March 18, 2021