7.1

The task enables users to merge data pages into Documents and/or merge Documents into Groups, based on conditions. Unse-
lected Data pages are ignored, but are moved with others Data pages if the action is applied to the current parent node.
Metadata Level Creation task properties are as follows:
General Tab
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
154) page for more details.
On Error Tab
The On Error Tab is common to all tasks. Details can be found on "Task Properties Dialog" (page 51).
Metadata Sequencer Action Task Properties
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.
Each chunk created by the Metadata Sequencer Action task is called a "sequence". The properties of each sequence determine
how many sequences will occur and what each sequence contains.
Metadata Sequencer task properties are as follows:
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
Document, and this value is set to 5, a 100 document job file will be divided into 5 sequences of 20 documents
each.
l Thefollowing rule: Determine if a new sequence starts or if the current one ends. For each metadata level,
the current value of the specified metadata attribute/field is compared with the one in memory. If they are dif-
ferent, either a new sequence starts or the current sequence is ended. The next sequence starts with the next
metadata level being processed. For details see the "Rule Interface" (page 154).
Metadata Sorter Task Properties
The Metadata Sorter Action task allows metadata to be sorted sequentially on three different levels, alphabetically or numer-
ically. It also allows sorting in ascending and descending order.
Metadata Sorter task properties are as follows:
©2010 Objectif Lune Inc - 152 -