Recurrence Definition Identification for Event Data Storage
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Event management systems face inefficiencies in storage and processing due to frequent reschedules and cancellations of recurring events, especially when transferring data between systems that do not support recurrence rules, leading to degraded storage space and processing efficiency.
Innovation Solution
A method and system that automatically identify a recurrence definition representing a list of dates using a recurrence rule, including exceptions, to efficiently manage event data storage by converting lists of dates into recurrence definitions, which can recreate the dates and store them instead of the original list, thereby improving storage efficiency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If recurrence rules are used to represent recurring events, then storage efficiency is improved, but frequent reschedules and cancellations degrade the efficiency gains
Solution Approach 1:
The system dynamically evaluates whether to represent event dates as a recurrence rule or as an explicit list based on the frequency of reschedules and cancellations. When modification frequency exceeds a threshold, the system transitions from recurrence rule representation to explicit date list representation, and vice versa, allowing the representation method to adapt to changing patterns of event modifications
Solution Approach 2:
The system changes the parameter of representation format (from recurrence rule to explicit date list or vice versa) based on the observed frequency of reschedules and cancellations. This parameter change optimizes storage efficiency by selecting the most appropriate representation method for the current pattern of event modifications
2Adaptability or versatility
If recurrence rules are translated to series of dates for transfer between systems, then compatibility is improved, but storage efficiency is reduced
Solution Approach 1:
The system dynamically selects the transfer format based on the capabilities of the target system. When transferring to systems that support recurrence rules, the original compact recurrence rule format is preserved. When transferring to systems that do not support recurrence rules, the system converts to explicit date lists, optimizing storage efficiency based on the specific transfer scenario
Solution Approach 2:
The system acts as an intermediary that converts between recurrence rule format and explicit date list format depending on the requirements of the source and target systems. This mediation allows efficient transfer of event data between systems with different capabilities while minimizing storage overhead
3Measurement precision
If frequent reschedules and cancellations are recorded explicitly, then accuracy is improved, but processing efficiency deteriorates
Solution Approach 1:
The system dynamically adjusts the level of explicitness in recording reschedules and cancellations based on their frequency. When modifications are frequent, the system maintains explicit records of each change to ensure accuracy. When modifications are rare, the system relies on the recurrence rule with minimal exceptions, improving processing efficiency while maintaining sufficient accuracy
Data Source
AI summary
A solution for managing dates is provided, in which a recurrence definition that represents a list of dates using a recurrence rule is automatically identified. The recurrence definition may also include a set of exceptions, which account for variations from a recurring pattern in the list of dates. In one embodiment, an efficiency measure is obtained for each of various proposed recurrence definitions, and a recurrence definition that most efficiently represents the list of dates is identified. In one application, an event management (e.g., calendaring) program automatically identifies an efficient recurrence rule for a list of event occurrences.