• Chapter 1: Getting Started with Stylus Studio®
• Chapter 2: Editing and Querying XML
• Chapter 3: Converting Non-XML Files to XML
  • Overview of Convert to XML
  • Choosing an Input File
  • The Convert to XML Editor
  • Parts of an Input File
  • Working with Regions
  • Working with Fields
  • Controlling XML Output
    • Specifying Element Names
    • Specifying Format
    • Omitting Regions and Fields, and Rows
    • Pattern Matching
    • Using Lookup Lists
      • Defining Lookup Lists
      • Working with Lookup Lists
    • Using Key=Value Characters
  • Creating an Adapter
  • Using Adapters in Stylus Studio
  • More About Converting EDI
  • User-Defined Adapters Properties Reference
• Chapter 4: Working with XSLT
• Chapter 5: Creating XSLT Using the XSLT Mapper
• Chapter 6: Debugging Stylesheets
• Chapter 7: Defining XML Schemas
• Chapter 8: Defining Document Type Definitions
• Chapter 9: Writing XPath Expressions
• Chapter 10: Working with XQuery in Stylus Studio
• Chapter 11: Composing Web Service Calls
• Chapter 12: Accessing Relational Data as XML
• Chapter 13: Building XML Pipelines
• Chapter 14: Publishing XML Data
• Chapter 15: Integrating with Third-Party File Systems
• Chapter 16: Extending Stylus Studio
• Chapter 17: The Stylus Studio Java API
• Chapter 18: Stylus Studio GUI Reference

Home > Online Product Documentation > Table of Contents > Using Lookup Lists

Using Lookup Lists

You can define lookup lists for individual fields. When Stylus Studio converts the input file, it replaces the string in the input file (the lookup) with the value you have defined for it in the Lookup List dialog box. Figure 191 shows an example of a lookup list that has been defined for a Status field:

Figure 191. Sample Lookup List

For any Status fields in the input document with a value of, say, 100, Stylus Studio would convert that value to Continue in the XML document it outputs; values of 202 would be converted to Accepted; and so on.

Input file values that do not match a lookup are emitted in the XML document as-is, allowing exceptional values to be decoded. For example, you might have a temperature lookup list with these values for a <Temperature> field:

32 | Freeze

212 | Boil

All other temperatures would be emitted as-is.

Defining Lookup Lists

Lookups are case-sensitive, so, for example, a lookup of bmw would not match any of the Make fields in the following sample file:

Make,Model,Year,Mileage
               
BMW,R1150RS,2004,14274  
               
Kawasaki,GPz1100,1996,60234  
               
Ducati,ST2,1997,24000  
               
Moto Guzzi,LeMans,2001,12393  
               
BMW,R1150R,2002,17439  
               
Ducati,Monster,2000,15682  
               
Aprilia,Futura,2001,17320 
               

            

You can define lookup lists only for fields in rows for which a match pattern (even a blank match pattern, as is the default) exists. Finally, you can paste comma- and tab-delimited text directly into the lookup list. This allows you to easily reuse existing lookup tables without having to re-enter text.

To define a lookup list:

The Lookup List dialog box appears.

Figure 192. Lookup List Dialog Box

Working with Lookup Lists

The following table summarizes the functions of the Lookup List dialog box, which allow you to work with new and existing lookup lists.