Kleara · Library
Avoid repeated events when cleaning-calendar exports overlap
Two four-week cleaning calendars that overlap share 21 events. Compare event identifiers and dates before importing a second file so the work is not counted twice.
Why overlapping files double-count
Suppose you save a four-week cleaning calendar now and a second one two weeks later, both from the same kitchen and bedroom plan. The two files cover some of the same days, so some occurrences are in both. Adding up the rows of both files overstates how much work is planned.
Each event in a Kleara calendar file carries an identifier built from the room, the task, its position in the room and the date, for example kitchen.taskSink.0.2026-11-10@kleara.vomcore.com. The same occurrence has the same identifier in both files.
The example pair
The first file covers 26 October to 22 November 2026 and holds 46 events. The second covers 9 November to 6 December and holds 44. Twenty-one identifiers appear in both, which leaves 69 distinct occurrences, exactly the number a single 42-day expansion of the same plan produces.
The shared events fall between 9 and 22 November, the two weeks both files cover. Each is an all-day event: an end day of 20261110 after a start of 20261109 means one day, not two days of work.
Check before importing the second file
- Compare the date ranges first; any overlap means shared events are likely.
- Compare identifiers, not titles: two events titled Kitchen: Scrub the sink on different days are different occurrences.
- Keep the original first file until you have seen how your calendar program treated the second import; programs differ in whether a known identifier updates an event or adds a copy.
- If you want no overlap at all, choose a second range that begins the day after the first one ends.
Limits of the identifier
The identifier names a task and a date, not a version of the plan. If you changed a frequency between the two downloads, an occurrence can keep its date and identifier while later dates change; compare task settings as well.
The planner's own preview always covers 28 days from the start date you choose, and every new calculation balances the start days again. Files made from different start dates are therefore not guaranteed to share dates for the same task. The app itself does not export calendars; it keeps one running plan.
An overlapping pair of finite exports
| Quantity | Occurrences |
|---|---|
| First file | 46 |
| Second file | 44 |
| Present in both | 21 |
| Distinct union | 69 |
| Single 42-day preview | 69 |
Inspect a repeated occurrence
| Exported UID | Included day | Exclusive end day |
|---|---|---|
| kitchen.taskDishwasher.3.2026-11-09@kleara.vomcore.com | 20261109 | 20261110 |
| kitchen.taskMop.1.2026-11-09@kleara.vomcore.com | 20261109 | 20261110 |
| bedroom.taskVacuum.1.2026-11-10@kleara.vomcore.com | 20261110 | 20261111 |
| kitchen.taskSink.0.2026-11-10@kleara.vomcore.com | 20261110 | 20261111 |
| bedroom.taskDust.2.2026-11-11@kleara.vomcore.com | 20261111 | 20261112 |
| kitchen.taskTrash.2.2026-11-11@kleara.vomcore.com | 20261111 | 20261112 |