Rostering data snapshots
Whenever the scheduling engine is run, it will also save a compressed data snapshot of all the data it used to create a particular roster.
The data in the snapshot includes all members' availability and preferences data, all staffing calendar data & duties data, all pre-allocation data, all engine profile data. This data snapshot will not normally be visible, but it will remain as an audit trail of the data used to create a particular roster.
Because Majozi is a dynamic system, I felt it important to have an auditable record of the data used to create a schedule (there were cases where a member changed their data AFTER a schedule had been created).