Polymorphic Spreadsheet Interface with Context-Sensitive Field Mapping
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Spreadsheets are ineffective for handling polymorphic data, leading to user confusion and increased risk of database errors due to the need for context-dependent field mapping, which is not intuitively supported by existing spreadsheet interfaces.
Innovation Solution
A method and system for displaying polymorphic records in a spreadsheet table by determining record structure based on discriminator fields, marking unavailable fields as distinct, and supporting user operations across multiple rows and columns while ensuring data type matching, using service metadata to manage global and context-sensitive fields.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If fields are mapped to the minimum number of columns to reduce complexity, then device complexity is reduced, but user confusion increases and reliability decreases due to context-dependent field availability
Solution Approach 1:
The patent segments the field mapping by creating separate columns for different field types (global fields vs. context-sensitive fields). This segmentation allows the spreadsheet to handle polymorphic data by visually separating fields that are always available from fields that depend on discriminator values, reducing user confusion while maintaining operational reliability.
Solution Approach 2:
The patent applies local quality by making field availability context-dependent within the spreadsheet interface. Different cells or columns are enabled or disabled based on the record's discriminator field values. This allows the same spreadsheet structure to adapt its functionality locally for each row, maintaining reliability without requiring complete field mapping for all contexts.
2Reliability
If fields are mapped to the maximum number of columns to ensure all fields are available, then reliability is improved, but ease of operation deteriorates due to user confusion about context-dependent fields
Solution Approach 1:
The patent uses visual differentiation (analogous to color changes) to mark context-sensitive fields distinct from global fields. By visually highlighting or shading cells corresponding to context-sensitive fields, the spreadsheet helps users understand which fields are available and which are not, maintaining reliability while improving ease of operation through better user awareness.
Solution Approach 2:
The patent introduces an intermediary layer between the polymorphic data and the spreadsheet interface. This intermediary mechanism (the field mapping layer with context-aware enable/disable logic) translates the complex polymorphic structure into a simplified spreadsheet view, where users interact with a consistent interface that adapts its behavior based on context, thus improving ease of operation without sacrificing reliability.
3Ease of operation
If context-sensitive fields are always mapped to maintain consistent column structure, then ease of operation is improved, but device complexity increases due to polymorphic data handling requirements
Solution Approach 1:
The patent implements dynamics by making the spreadsheet column availability dynamic rather than static. Columns corresponding to context-sensitive fields are enabled or disabled based on the record's discriminator values. This dynamic behavior allows the spreadsheet to maintain consistent usability (ease of operation) while managing polymorphic data complexity through adaptive field visibility rather than fixed comprehensive mapping.
Data Source
AI summary
A spreadsheet user interface shows polymorphic records. The records include global fields, discriminator fields, and context-sensitive fields. A context-sensitive field is available or unavailable dependent on a discriminator field value. Record fields associate with spreadsheet columns, regardless of field availability. User confusion is prevented by marking a record's unavailable context-sensitive fields as unavailable and visually distinguishing them from available fields. A user-requested operation spanning multiple rows and columns is supported by testing whether a source cell and source data is available, a destination cell is available, and skipping the operation for those records whose source and/or destination cell is required but unavailable. An embodiment supports interfacing with a single record in a spreadsheet form by applying global form templates associated with global fields, and context-dependent form templates associated with specific discriminator field values.