Skip to main content
Skip table of contents

AO Multi Line Name Parse

Advanced Option (AO) Multi Line Name Parse parses names from one or more fields and assigns gender based on those names. As with the Data Management Name Parse macro, you can select formatting and parsing options. The macro accepts a single stream as input and produces one output.

AO Multi Line Name Parser configuration parameters

AO Multi Line Name Parser has two sets of configuration parameters in addition to the standard execution options: Fields and Options.

AO Multi Line Name Parser Fields tab

Input fields

Line 1 ... 8

One or more fields containing Name data. Default: None.

Name order field

Optional field indicating whether names are formatted with first name first or last name first. This is a two-byte text field containing the values FL (first name followed by last name) or LF (last name followed by first name). If this is unspecified, names are assumed to be first name followed by last name. Default: None.

Output options

Max output name fields

Specify the number (1-16) of name fields that can be output. Default: 2 per input line.

Suppress descriptors

Select if you do not want descriptors to be appended to the output records. Default: Yes.

Field name as descriptor

Select to append field names to output records as descriptors. This indicates which field a name was found in. Default: No.

Select descriptors

Line 1 ... 8 descriptor

You can optionally specify fields to associate descriptive data with output fields. You must clear the Suppress descriptors option. Default: Yes.

AO Multi Line Name Parser Options tab

Parsing/gender data source

You may specify an optional parsing/gender data source. This is a table in DLD format containing either two or three columns: TOKEN, SYMBOL, and (optionally) GENDER.

Parsing behavior

Use large table

Select to use Data Management's comprehensive parsing lookup table. If you are resource-limited, you should leave this off. Default: No.

Treat "/" as AND

If the name field might contain two names separated by a slash ("/"), select this option to ensure that the name is parsed correctly. Default: No.

Fix reversed First/Last

Select this if you suspect that your records may have First name and Last name reversed. Default: No.

Preserve dual LastName

If the name field might contain names with two last names, you can select this option to put both in a single last name field. If you have the name Mary Andrews Smith, selecting this option will write Andrews Smith to the OUT_LNAME1 field. If this option isn't selected, Andrews will be written to the OUT_MIDNAME1 field and Smith will be written to the OUT_LNAME1 field. Default: No.

Split hyphenated LastNames

If the name field might contain names with hyphenated last names, you can you can select this option to store hyphenated last names in separate fields. If you have a last name of Watson-Jones, selecting this option will write Watson to the OUT_LNAME1 field and Jones to the OUT_LNAME1_2 field. If this option isn't selected, then Watson-Jones will be written to the OUT_LNAME1 field. Default: No.

Parse suffix types

Select this option to distinguish between generational suffixes such as Jr and III, suffixes such as DR and PhD and professional titles such as Finance Manager. An input name of the form "James Smith III, MD" will be output with "III" in the OUT_POSTNAME1 field and "MD" in the OUT_SUFFIX1 field. The name "Janice Jones, PhD, VP of Development" will be output with "PhD" in the OUT_SUFFIX1 field and "VP of Development" in the OUT_PROFTITLE1 field. Without this option checked, "PhD" and "VP of Development" would both go to the OUT_SUFFIX1 field. Default: Yes.

No punctuation in titles

Select to remove the punctuation from honorary titles. This will strip the periods in titles like M.D. Default: No.

Capitalization

Choose capitalization style of the output. Default: Original.

Treat "President" as

You can treat the word "President" as either Title or Prefix. If you select Title, then "President" will be put in the OUT_PROFTITLE1 field. Default: Title.

Treat "C O" as "C/O"

Select to interpret the string "C O" as "Care Of". Default: Yes.

Prefix options

Add prefix if none present

Select to add a prefix such as "Mr" or "Mrs" to names that don't have one. Use the other prefix options (below) to specify the default prefix. Default: No.

Default male prefix

Select a default male prefix from the list. Default: MR.

Default female prefix

Select a default female prefix from the list. Default: MS.

If multi-name use alt female prefix

Select to assign a prefix to the female name if a pair of parsed names includes a female. Default: Yes.

Alt female prefix

If you selected If multi-name use alt female prefix, select a default female prefix. Default: MRS.

Configure AO Multi Line Name Parser

  1. Select AO Multi Line Name Parser, and then select the Fields tab on the Properties pane.

  2. Select Line 1 and select the input field. Repeat for any additional input fields.

  3. Optionally, specify a Name order field that indicates whether names are formatted with first name first or last name first. This is a two-byte text field containing the values FL (first name followed by last name) or LF (last name followed by first name). If this is unspecified, names are assumed to be first name followed by last name.

  4. Optionally, select Max output name fields to set the maximum number of name fields included on output.

  5. Optionally, clear Suppress descriptors to include associate a field descriptor with each output record. Two descriptor options are available:

  6. Select Field name as descriptor to use the field name to indicate which field a name was found in, or

  7. Select Line 1 descriptor and select a field containing the descriptor for that input field. Repeat for additional fields.

  8. Select the Options tab and configure the desired parsing behavior and output options. You may optionally specify an additional parsing data source. See adding a parsing/gender data source.

  9. Optionally, go to the Execution tab, and then set Web service options.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.