Calendaring Recurring Event Modification via Exception Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional calendaring systems face difficulties in simplifying the process of modifying recurring events, particularly in interpreting and applying modifications to recurrence rules, which can be complex and problematic for users.
Innovation Solution
A method and system for applying ordered modifications to recurring event instances by identifying event exceptions, modifying specific properties, and purging stale exceptions, utilizing a recurrence event expander, modifier, and modification rule reducer to optimize storage and calculation of event instances based on recurrence rules.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If modifications to recurring events are applied internally to the recurrence rule itself, then storage space is optimized, but interpreting and applying modifications becomes difficult and problematic
Solution Approach 1:
The patent segments the modification application process into distinct phases: first expanding the recurrence rule to generate individual event instances, then applying modifications to specific instances rather than to the recurrence rule itself. This segmentation separates the storage-optimized recurrence representation from the user-friendly modification process, allowing both goals to be achieved simultaneously.
Solution Approach 2:
The patent introduces an intermediary expansion process that acts as a mediator between the compact recurrence rule storage and the user-facing modification interface. This intermediary generates temporary event instances that serve as the actual target for modifications, bridging the gap between space-efficient storage and ease of operation without requiring modifications to be applied directly to the recurrence rule.
2Ease of operation
If all event instances are stored explicitly, then modifications can be applied easily, but storage space requirements increase significantly
Solution Approach 1:
The patent performs preliminary expansion of the recurrence rule to generate event instances only when needed for modification, rather than pre-storing all instances. This preliminary action allows the system to maintain compact storage while providing full modification capability when required, as instances are generated on-demand and can be modified before being discarded or stored minimally.
Solution Approach 2:
The patent creates temporary copies of event instances from the recurrence rule when modifications are needed, rather than storing permanent copies of all instances. These copied instances serve as workspaces for applying modifications, allowing easy operation while maintaining space efficiency, as the copies are transient and derived from the compact recurrence representation.
3Reliability
If event exceptions are accumulated over time, then all modifications are preserved, but storage efficiency decreases and stale exceptions remain
Solution Approach 1:
The patent implements a mechanism to discard stale event exceptions that are no longer needed after their modifications have been applied to the recurrence rule or event instances. By identifying and removing these obsolete exceptions, the system maintains complete modification history for active events while freeing storage space, achieving both reliability and storage efficiency.
Solution Approach 2:
The patent employs feedback mechanisms to monitor the state of event exceptions and determine when they have served their purpose. By tracking whether modifications have been applied and whether exceptions remain relevant, the system can automatically identify stale exceptions for removal, ensuring modification completeness while optimizing storage through selective retention based on actual need.
Data Source
AI summary
A method and system for the ordered modification of a recurring event in a calendaring application. A method for applying ordered modifications to recurring event instances, can include identifying an event exception which corresponds to a separately defined recurring event instance. Subsequently, at least one property of the recurring event instance can be modified based upon the event exception. Additional event exceptions corresponding to the recurring event instance can be further identified in accordance with a preferred aspect of the present invention. For each further identified additional event exception, at least one property of the recurring event instance can be further modified based upon the further identified additional event exception. Notably, each of the identifying and modifying steps can be repeated for additional recurring event instances.