7.4

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.
Metadata
Simply put, metadata is data about data or, in other words, information tagged to data. Metadata includes information about
the data file itself, the document, page properties, page counts and custom user fields.
Applications or plug-ins created in PlanetPress Suite 6 and using Metadata will need to be updated for use in version 7.
No backward compatibility mode is available.
When a user-defined emulation is used with metadata, results and behavior are unknown and unsupported. For
instance, refreshing the metadata file may cause the document to crash and/or corrupt. For this reason, it is strongly
advised to create backup copies of your documents beforehand.
Metadata structure
Metadata in PlanetPress Suite Version 7 introduces the following concepts for adding information to a job:
l Page: 1 side of a physical paper sheet.
l Datapage: 1 atomic unit of content that produces zero, one or more pages.
l Document: group of 1 or more ordered datapages intended to the same recipient from the same source (ex:
invoice).
l Group: a logical and ordered group of documents (ex: all invoices for a specific customer number; all documents
going to the same address, etc.)
l Job: file that contains 1 or more groups.
When Metadata is produced for a given job, a hierarchical (i.e. tree-like) structure is created, composed of the above ele-
ments in the following order: Job->Group(s)->Document(s)->Datapage(s)->Page(s). Any operation that modifies the data
with regards to this structure (ex: remove pages, alter the data, etc.) makes the metadata obsolete and so it must be rec-
reated or refreshed.
As an example, consider the typical case of a PlanetPress Design document which uses a Line Printer datafile of transactional
data in order to generate PDF invoices for a series of clients. By using the Metadata tools available in PlanetPress Suite version
7, we can add the following information to the datafile:
l The job contains only invoices for clients located in Montreal.
l Since more than one invoice can go to the same recipient, invoices are grouped by customer.
l Each invoice is a document resulting from the execution of a PlanetPress Design document over one or more datap-
ages, which results in zero or more physical pages being output.
Data in PlanetPress Suite Workflow Tools