7.5

Table Of Contents

l Search from a specific location only.

l Search from level X to Job, where X can be any metadata level (Job, Group, Document, Datapage, Page). With this

search option, if the selected metadata element does not exist at the specified level, then it will be searched for, start-

ing at the lowest metadata level as specified in the search option, then one level up until the element is found.

The Raise an error if the field does not exist option allows to control what to do when a given metadata element is not

found, regardless of the search option.

The Data page box lets the user choose which data page metadata elements to be displayed.

The Metadata level is a treeview allowing users to select the metadata level from which to display or select metadata ele-

ments.

TheAttributes list displays all metadata attributes describing the current metadatalevel,as selected in the Metadata Level

treeview, for the current data page, as selected in theData Page control.

The Production information list displays all metadata fields describing the current metadatalevel,as selected in the Meta-

data Level treeview, for the current data page, as selected in theData page box.

Data Page

A data page is the amount of data that your data file, through your emulation, is passing through a single document. This can

mean one or more lines of a CSVfile, a PDFpage, or a certain number of lines of a text file.

Adata page can ignored and print no page at all, or it can be used to generate multiple pages when printing. Unless you are

using an N-Up object however, you cannot use multiple data pages to generate a single physical page.

To configure what appears in a data page, you use the Data Selector to specify emulation parameters.

Emulation

The emulation defines how your document receives and processes its input data. It is basically a method with which Plan-

etPress Design will read the data and display it on screen. The way data selections are made and data pages are created

depends on the emulation, so it is always set at the beginning of your document creation, as you select your data file(s).

While you can have multiple sample data files in your document, all of them have to use the same emulation, since

data selections and data pages rely on the emulation to work properly.

Various emulation specific options can be set for most emulations, with the exception of the line printer and database emu-

lations. All emulations, except the database and XML emulations, also let you perform operations on the data to stabilize it,

such as add and remove characters or lines.

The sample data file you associate with the document, the emulation you select and the PPD you associate with the document

define how your document handles its input data, and consequently determine the accuracy of the output the document

produces with the data stream it receives at runtime. If you alter any of these settings, you should verify the change does not

compromise the output accuracy of the output.

This section explains what an emulation is, the different types of emulations available in PlanetPress Design, and how to fine-

tune the emulation to your input data.