Add repetition schedules to data model
Repetition schedule
- A repetition scheme has a relation to the original scheme.
- The repetition scheme has its own rhythm/schedule, which follows the same procedure like a normal schedule and is independent of the original rhythm/schedule
- A repetition schedule has a start- and optionally an enddate
When creating a rep-scheme the timeslots are marked as repetitions and the episodes from the original schema get associated one by one with the rep-scheme.
Proposal
Creating the repetition scheme
One can choose if the repetition scheme starts with the first original episode or the last upcoming episode before the startdate of the repetition schedule. @kmohrf I thought this might be useful, what do you think?
Rules:
-
The original episode must always start before the episode of the rep-scheme. If this is not the case for a repetion-timeslot, it gets discarded, and the episode will be associated to the next timeslot.
-
The end is reached when all orignal episodes are connected to a repetition-timeslot OR an enddate for the rep-scheme was given and reached.
Updating the original or repetition timeslot
Afterwards their are no automatic updates happening, despite changing length or datetime of the original timeslot, one would have to make the same changes to the associated repetition-episode.
The same applies to the repetition timeslot.
Deleting the original or repetition timeslot
If an episode from the original scheme gets deleted, the repetition-timeslot gets also deleted.
Open decisions
-
What happens when the repetition timeslot is edited or deleted? Is it read-only? Can it be moved? Sandra: It is treated like a normal scheme/timeslot. So updating/deleting is possible. -
Possible inconsistency between deleting (synced with rep timeslot) vs. editing timeslot (not synced). -
End date and extension behaviour for repetitions schedules and normal schedules (see comments)