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/deselected, which has the same effect.
For more information about Metadata see Metadata.
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
- Metadata level: Select the Metadata level to process.
- Sequencing is based on
- 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.
- 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.
- 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 different, 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.