User guide

Chapter 6: Output 93
Output file sizes
If you define unit or subunit breaks, the sizes of your output files may differ.
That’s because Label Studio forms a new subunit whenever it reaches the number
of specified labels or the end of a unit, whichever comes first.
For example, let’s suppose you need to prepare a large national mailing. You
choose to group your records by changing entry point (DB.Ent_Pt_No) values
because your West-Coast-bound trucks leave first.
Because you also have two bindery
lines ready to generate the labels,
you limit the output files to, for
example, 2,000 pieces. That way
each bindery line can handle pieces
from the same job.
Within the large units, Label
Studio forms many subunits, each
subunit containing 2,000 pieces—
except possibly the last subunit in
each unit. The last unit varies
because Label Studio must end the
subunit when the unit ends (see the Flagstaff entry point). For a unit that has
fewer than the specified 2,000 pieces, Label Studio ends the subunit when the unit
ends. Consequently, that smaller subunit never reaches 2,000 pieces in size (see
the Prescott entry point).
.
Note: The subunit breakdown for the Denver or Phoenix entry points are
not shown. The program would create them similarly to the Flagstaff
subunits.
Denver
9,231 pcs.
Flagstaff
7,762 pcs.
Phoenix
10,436 pcs.
Prescott
641 pcs.
Subunit 1
2,000 pcs
Subunit 2
2,000 pcs
Subunit 3
2,000 pcs
Subunit 4
1,762 pcs
Subunit 1
641 pcs
(5 subunits)
(6 subunits)