|
|
 |
 |
Along with the export modules that can be used for database marketing, Pathways also supplies a comprehensive
set of modules that can be used for importing data into the Pathways databases. To import data,
publishers simply “define” and “map” information from the external data source into the Pathways databases.
|
|
|
|
|
Each Input Field in the source file is defined using a data name, data type, and data size. Calculated
fields can then be added to “manufacture” data not available in the source file. An example might
be a detail file that includes quantity and price. If the publisher wants to map the sales total to a
field in a Pathways database, he/she can create a calculated field that is the product of the quantity
and price. The new calculated field can then be mapped to the new Pathways database field.
|
|
|
|
|
To aid publishers in normalizing data during importation, a variety of routines are available for
formatting and translating data that will be placed into the Pathways databases. These format routines
may be as simple as upshifting or downshifting data before storing it in the Pathways database. In contrast,
any valid FoxPro expression can be used to flexibly translate the data to any format desired by the publisher.
|
|
|
|
|
Split Algorithms are available to help publishers parse various pieces of information from a single
field that holds more than one piece of information, into individual data components. This allows the
information to be normalized, with each individual piece made available for publishing and exporting.
Algorithms are available to parse Executive Names into honorific, first name, last name, and title
fields. Algorithms are also available to help publishers parse City/Country Information which may
contain city, state, zip, province or country names in a single input field.
|
|
|
|
|
Abbreviation Tables are available for Executive Title, Company Name, Street Address,
and City fields. Although all Pathways database fields are extremely generous in length, these tables
allow information that is imported from a field that is longer than allowed in the Pathways database
to be abbreviated, rather than being arbitrarily truncated.
|
|
|
|
|
