Tiered Page Retention With Deletion-Date Mapping
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current data retention methods in knowledge management platforms face challenges such as inefficient storage management, difficulty in finding relevant information, tampering with old data, and lack of robust retention policies, which can lead to data breaches and compliance issues.
Innovation Solution
Implementing a tiered data retention system with live, trashed, and retained pages, along with a block data model that includes metadata for tracking page states and using a deletion database to manage large volumes of data efficiently, and preserving permissions for restored pages.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data is retained indefinitely for compliance and recovery purposes, then data security and compliance are improved, but storage costs and data management complexity increase
Solution Approach 1:
The patent segments retained data into distinct categories (trashed pages, restored pages, permanently deleted pages) with different retention policies and access permissions. This segmentation allows the system to maintain comprehensive data security while managing different data types through standardized, modular processes, thereby reducing overall management complexity.
Solution Approach 2:
The patent implements dynamic retention policies where data automatically transitions between states (live → trashed → retained → deleted) based on time-based rules and user actions. This dynamic approach replaces static, manual data management with automated workflows that adapt to different scenarios, improving security through consistent policy enforcement while reducing management burden.
2Adaptability or versatility
If all deleted data is retained for potential recovery, then data recovery capability is improved, but storage efficiency and accessibility deteriorate
Solution Approach 1:
The patent applies different quality characteristics to different portions of retained data. Trashed pages maintain full recovery capability with user-accessible restoration, while restored pages have limited recovery options and metadata is selectively preserved. This local differentiation ensures comprehensive recovery capability where needed while optimizing storage efficiency and accessibility for commonly accessed data.
Solution Approach 2:
The patent implements a selective discard and recover mechanism where data is not indefinitely retained in its original form. Instead, the system discards redundant copies and detailed metadata for old restored pages while preserving essential information for compliance. This allows the system to maintain recovery capability for critical data while efficiently managing storage resources.
3Reliability
If a comprehensive deletion database is implemented to track all pages, then data retention policy enforcement is improved, but system complexity and processing overhead increase
Solution Approach 1:
The patent implements preliminary action by establishing deletion policies and retention rules in advance, before data deletion scenarios occur. The system pre-configures retention periods, access permissions, and automated workflows that execute automatically when deletion events occur. This eliminates the need for complex real-time decision-making and reduces processing overhead during actual deletion operations.
Solution Approach 2:
The patent uses copying to maintain a simplified representation of deletion data in the deletion database. Rather than storing complete page contents and all metadata, the system copies only essential information (page identifiers, deletion timestamps, retention periods) into the deletion database. This copying approach ensures accurate policy enforcement while keeping the database lightweight and easy to manage.
4Ease of operation
If old data is kept in accessible locations, then information retrieval is improved, but data tampering risk and security exposure increase
Solution Approach 1:
The patent extracts retained pages from the main accessible workspace and places them in a separate, isolated retention storage area. This physical and logical separation removes old data from locations where tampering can occur, while still enabling authorized retrieval through controlled access mechanisms. The extraction principle effectively eliminates the trade-off by decoupling accessibility from vulnerability.
Solution Approach 2:
The patent introduces an intermediary access layer between users and retained data. This intermediary mechanism (the retention management system) mediates all access requests to old data, logging and controlling who can retrieve what information and when. This intermediary layer maintains ease of operation for authorized users while providing security and preventing unauthorized tampering.
Data Source
AI summary
A method includes receiving a request to relocate a page from a first logical location to a second logical location within a first database. The method includes modifying a property of the page to reflect its new logical location. The method includes calculating a duration for the page to remain in the second logical location and, based on this duration and the current date, determining a deletion date for the page. The deletion date, along with the page's space identifier, can be stored in a second database that maintains a mapping between space identifiers and deletion dates. The method can include querying the second database to identify workspaces with a deletion date that matches the current date. The method can include identifying pages with a deletion date matching the current date. The method can update a property of each identified page to indicate its relocation to a third logical location.