Relational Database Structure for Multi-Version Form Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current database systems face difficulties in tracking and managing changes to form structures over time, particularly when fields are added or removed, leading to redundancy and inefficiencies, and struggle to provide access to earlier versions of forms and data while maintaining data integrity, especially in large datasets spanning long timelines.
Innovation Solution
A relational database structure that stores both fixed and variable form content, allowing for the creation of tables to store fixed and variable form content, enabling the update of fixed form content to generate new versions of forms and linking data between forms using keys generated by an application communicating with the database, facilitating querying of all form content across multiple versions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional database tables are used to store form data with fixed schemas, then data structure stability is maintained, but flexibility to accommodate form layout changes and multiple versions is lost
Solution Approach 1:
The patent segments form data into three distinct tables: form definitions (storing form metadata and structure), form records (storing instance data), and form field mappings (linking fields to records). This segmentation allows each table to serve a specific function, enabling form version flexibility without requiring complex schema changes across the entire database structure.
Solution Approach 2:
The patent adds a temporal dimension by including version identifiers and creation timestamps in the form definitions table. This allows the database to store and query multiple versions of forms simultaneously, transforming a static single-version model into a dynamic multi-version system without increasing structural complexity.
2Adaptability or versatility
If database tables are modified to add new fields or forms, then functionality is improved, but data integrity and existing query structures are compromised
Solution Approach 1:
The patent establishes a preliminary schema framework with form definitions, form records, and form field mappings tables before any form data is stored. This pre-defined structure includes version tracking capabilities from the outset, allowing forms to evolve over time without requiring schema modifications that could compromise data integrity or existing queries.
Solution Approach 2:
When a form is updated to create a new version, the system creates a copy of the form definition with an incremented version identifier rather than modifying the existing form structure. This copying mechanism preserves the original form's data integrity while enabling the new version to incorporate changes, allowing form evolution without compromising existing data.
3Loss of information
If form data is stored with detailed tracking of changes, then version control is improved, but query performance and data retrieval efficiency deteriorate
Solution Approach 1:
The patent extracts version-specific form structure information into a separate form definitions table, leaving the form records table to contain only the core data. This separation allows version tracking to be maintained in the definitions table without adding overhead to the queryable data in the records table, preserving query efficiency while maintaining complete version information.
Data Source
AI summary
A relational database for storing data used to populate form records fields, wherein a database table structure stores both fixed and variable form content, for multiple form types by creating tables to store the fixed form content and variable form content. Also described is a method for structuring a relational database, the data content of which is used to populate form fields in forms; the forms structured as fixed data content interspersed with form fields for receipt and display of variable data content; the variable data content derived from primary tables in said relational database; said method comprising creating one or more reference tables which store information about said primary tables thereby to permit tracking of changes to said form fields.