Before scheduling data collection and configuring outputs, you should understand the concepts behind these tasks. The illustration below shows the following for a sample scenario:
Collections: The thick green vertical lines represent data collections for a single MCU from November 23 through 29. Collection for this MCU is scheduled to run daily at 6:00 am.
Outputs: Broken red vertical lines represent output generations for two output configurations, Output A and Output B, for the same time period. Each output generation is numbered: A1, A2, etc., for Output A; B1, B2, etc., for Output B. Output A generates output file(s)* daily at noon; Output B, daily at 6:00 pm. (An organization may configure multiple outputs if it has multiple systems with different data requirements.)
Conferences included in outputs: Shaded rectangles illustrate the time frames for included conferences. For example, the rectangle labeled "A1 Data" represents the output data for the first generation of Output A (A1). This rectangle indicates that the A1 files include conferences from November 24 through part of November 26.
*Depending on how an output is configured, one to four files may be generated each time the output is run.
Note the following:
The first time the Collector generates files for an output configuration, it includes all collected conference data not previously included in files generated for the same output configuration, starting with the "not before" date specified on the "Configure an Output -- Content" page. The first output files for Output A and Output B, called A1 and B1 respectively, include conference data for a time frame longer than the time frames for subsequent output generations, even though the output files are generated at the same times each day. For example, the "not before" date for Output A is November 24, so A1 includes all collected data for conferences starting November 24 up to the most recent collection time on November 26, the day the output is generated.
When the Collector generates output files, it never repeats conference data from previously generated files for that same output configuration. Therefore, A3 repeats no data included in A2 or A1. However, the files for different output configurations may include the same data. Note, for example, that conference data in B1 is also included in A1, A2, and A3.
Even though files for Output A and Output B are generated at different times each day, A4 and B2 have the same data since the collection times are the same.
The graphic above represents collection for a single MCU. Additional MCUs can be scheduled for data collection at different times. However, during output file generation, the Collector pools collected data from all MCUs.