7.4

Table Of Contents
l Document: Create a new Document level. Note: Attributes and Fields are deleted for all new Document levels
created as well as existing Groups.
l Group: Create a new Group level. Note: Attributes and Fields are deleted for all new Group levels created.
l Delimiter defines if the Condition parameter is triggering the beginning or the end of a Group or Document. If
the delimiter option is set to None, the action is not performed.
l Rules enable the user to define on which criterions the action must to be performed. The condition must be
TRUE to execute the action. If the condition is not met at least once, the rule is not applied. To set up conditions,
the Rule Interface is displayed, allowing to edit the condition for the given action. See theRule Interface page for
more details.
On Error Tab
The On Error Tab is common to all tasks. Details can be found on Task Properties Dialog.
If storing the message or ID, if they are store in a jobinfo they will be available in any error handling process where errors are
being forwarded. In all cases, if your process continues after the error, the contents of the variables selected in this window
will be available for the rest of your process, or whenever they are overwritten.
Common Errors
Though some error messages are specific to a task in particular, others may apply to any and all tasks because they are
related more to the system than to PlanetPress itself. Some examples would be W3813, W3830, W3991, W4005. These cor-
respond to issues such as not having any space to write files, permission errors on folders or files, etc.
Metadata Sequencer
Although the Metadata Sequencer acts as a splitter, the data file itself remains untouched, as neither the data nor the metadata
are actually being split through this task. With each sequence, the entire data file still gets carried from one task to another.
Metadata records are simply selected/unselected, which has the same effect.
Input
Any data file with accompanying metadata.
Processing
A loop is established and the metadata is separated into chunks, as defined in the rules set forth in the task properties.
Output
The original data file is output once per chunk, along with this chunk's metadata. Note that *all*the metadata is in each of the
sequence, but anything not part of the sequence is disabled and is ignored by all tasks using metadata afterwards.
Task Properties
General Tab
l Metadata level: Select the metadata level to process.
l Sequencing is based on...:
l The following number of occurrences of the level: Determine a sequence based on the number of
instances found for the metadata level currently processed. For example, if the Metadata level is set to Group,
and this value is set to 3, each sequence contains 3 groups (except, possibly, the last one, depending on the
number of groups left in the last sequence). The next loop starts with the next group after this sequence.
l Thefollowing number of sequences in the job:Divides the metadata into a set number of sequences
and equally distributes the number of levels between the sequences. For example, it the Metadata level is set to