Sheets-Based Data Management Service with Row Links
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Small teams or individuals face prohibitive costs and expertise challenges in developing and maintaining complex data management applications using conventional database systems, while traditional spreadsheet programs struggle with large data sets and hierarchical relationships.
Innovation Solution
A sheets-based data management service that supports dynamically materialized views and row links, allowing for easy creation and management of logical tables, automatic updates, and complex queries without requiring expertise in relational modeling, using a 'web-of-sheets' model for data storage and manipulation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If conventional database systems are used for data management, then data processing capability and handling of large data sets are improved, but development cost and expertise requirements increase significantly
Solution Approach 1:
The patent creates a simplified copy of database functionality through spreadsheet-like interfaces. Instead of requiring users to interact with complex database systems directly, the invention provides a simplified interface that copies essential data management capabilities, allowing small teams to access database-like functionality without needing database expertise or bearing the full complexity burden.
Solution Approach 2:
The patent introduces an intermediary layer between the complex database systems and the end users. This intermediary provides spreadsheet-like interfaces that translate simple user actions into complex database operations, shielding users from complexity while maintaining access to powerful data processing capabilities.
2Ease of operation
If traditional spreadsheet programs are used for data management, then ease of use and accessibility are improved, but capability to handle large data sets and hierarchical relationships deteriorates
Solution Approach 1:
The patent makes spreadsheets universal by enabling them to handle both simple small-scale data and complex large-scale data with hierarchical relationships. The system allows spreadsheets to function as both simple calculation tools and powerful database systems, depending on the needs of the user, thereby eliminating the need to choose between ease of use and data capacity.
Solution Approach 2:
The patent introduces dynamic capabilities to spreadsheets, allowing them to adapt their structure and functionality based on the data being managed. The system can dynamically create hierarchical structures, relationships, and views as needed, enabling spreadsheets to scale from simple to complex data management tasks without losing ease of use.
3Power
If full-fledged data management applications are developed using conventional database systems, then data processing power is improved, but development time and resource requirements increase
Solution Approach 1:
The patent performs preliminary actions by pre-building the complex data processing infrastructure behind the scenes. Instead of requiring users to build data processing capabilities from scratch, the system has already established the necessary database structures, relationships, and processing power, which users can then leverage immediately through simple spreadsheet interfaces.
Solution Approach 2:
The patent enables the system to serve itself by automatically managing complex database operations without requiring expert intervention. The system self-manages data relationships, hierarchical structures, and processing operations, allowing small teams to access enterprise-level data processing power without needing enterprise-level development resources.
Data Source
AI summary
In response to a determination that a first logical table is to be created in a data sheet, a respective row identifier is generated and stored for individual rows of the first logical table. To indicate a relationship between a particular cell of another logical table and a particular row of the first logical table, the row identifier of the particular row is stored. After a modification of a value stored in the particular row, the row identifier is used to determine an updated value to be displayed in the particular cell of the other logical table.