Table of Contents

Search

  1. Preface
  2. Introduction to Transformations
  3. Transformation Ports
  4. Transformation Caches
  5. Address Validator Transformation
  6. Aggregator Transformation
  7. Association Transformation
  8. Bad Record Exception Transformation
  9. Case Converter Transformation
  10. Classifier Transformation
  11. Comparison Transformation
  12. Consolidation Transformation
  13. Data Masking Transformation
  14. Data Processor Transformation
  15. Decision Transformation
  16. Duplicate Record Exception Transformation
  17. Expression Transformation
  18. Filter Transformation
  19. Hierarchical to Relational Transformation
  20. Java Transformation
  21. Java Transformation API Reference
  22. Java Expressions
  23. Joiner Transformation
  24. Key Generator Transformation
  25. Labeler Transformation
  26. Lookup Transformation
  27. Lookup Caches
  28. Dynamic Lookup Cache
  29. Macro Transformation
  30. Match Transformation
  31. Match Transformations in Field Analysis
  32. Match Transformations in Identity Analysis
  33. Normalizer Transformation
  34. Merge Transformation
  35. Parser Transformation
  36. Python Transformation
  37. Rank Transformation
  38. Read Transformation
  39. Relational to Hierarchical Transformation
  40. REST Web Service Consumer Transformation
  41. Router Transformation
  42. Sequence Generator Transformation
  43. Sorter Transformation
  44. SQL Transformation
  45. Standardizer Transformation
  46. Union Transformation
  47. Update Strategy Transformation
  48. Web Service Consumer Transformation
  49. Parsing Web Service SOAP Messages
  50. Generating Web Service SOAP Messages
  51. Weighted Average Transformation
  52. Window Transformation
  53. Write Transformation
  54. Appendix A: Transformation Delimiters

Developer Transformation Guide

Developer Transformation Guide

Token Parsing Ports

Token Parsing Ports

Configure the token parsing ports with settings appropriate for your data.
A Parser transformation in token parsing mode has the following port types:
Input
Contains data that you pass to the Parser transformation. The transformation merges all input ports into a combined data string using the
Input Join Character
specified on the
Strategies
tab. If you do not specify an input join character, the transformation uses a space character by default.
Parsed Output Ports
User-defined output port(s) that contains successfully parsed strings. In cases where multiple parsing strategies use the same output, the transformation merges the output into a combined data string using the
Output Join Character
specified on the
Strategies
tab. If you do not specify an output join character, the transformation uses a space character by default.
Overflow
Contains successfully parsed strings that do not fit into the number of outputs defined in the transformation. For example, if the transformation only has two "WORD" outputs, the string "John James Smith" results in an overflow output of "Smith." The Parser transformation creates an overflow port for each strategy that you add.
When you select the Detailed Overflow option, the transformation creates an overflow port for each label in the model.
Unparsed
Contains strings that the transformation cannot parse successfully. The Parser transformation creates an unparsed port for each strategy that you add.

Output Ports in Probabilistic Matching

When you configure a parsing strategy to use probabilistic matching techniques, the Parser transformation adds a port to store the match scores for each output port.
The following table describes the types of port:
Port Type
Port Created in Probabilistic Matching
Parsed output port
[label name] output
[label name] score output
Overflow data port
[overflow data] output
[[overflow data] score output
Unparsed data port
[unparsed data] output
[unparsed data] score output

0 COMMENTS

We’d like to hear from you!