Code List Data Lifecycle Management via Segmented Delivery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data processing systems face inconsistencies and inefficiencies due to differences in data delivery mechanisms for configurations, preferences, and upgrades, leading to challenges in managing data throughout its lifecycle.
Innovation Solution
A computer-implemented method and system that processes requests to access data from a table by determining relevant portions of the data using metadata, generating a file corresponding to these portions, creating a repository object, and transmitting a response to update the data, while ensuring authentication, validation, and language translation as needed.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If data is delivered through different mechanisms for configurations, preferences, and upgrades, then data can be managed throughout its lifecycle, but inconsistencies arise that affect operation efficiency
Solution Approach 1:
The patent segments data into different types (configurations, preferences, upgrades) and applies specific delivery mechanisms to each type. Configuration data is delivered through SFTP with checksum validation, preferences through JSON format with schema validation, and upgrades through version-controlled packages. This segmentation resolves the contradiction by enabling versatile lifecycle management while maintaining operational efficiency through type-specific optimized processes.
Solution Approach 2:
The patent introduces intermediary components including a data delivery service that acts as a mediator between data sources and target systems, checksum validation mechanisms that mediate data integrity verification, and schema validators that mediate format compliance. These intermediaries ensure consistent, efficient data delivery across different data types while maintaining the ability to manage diverse data lifecycles.
2Ease of operation
If all data portions are made updateable, then data owners can update any data, but storage limitations and security risks increase
Solution Approach 1:
The patent applies local quality by making different portions of data updateable based on their specific characteristics and ownership requirements. Configuration data may be read-only or updateable with strict validation, preferences may be user-editable with schema constraints, and upgrade data follows version control protocols. This selective updateability maintains security and storage efficiency while providing ease of operation where needed.
Solution Approach 2:
The patent implements dynamic update permissions where data updateability changes based on lifecycle stage, data type, and user role. Configuration data transitions from deployable to locked after initialization, preferences allow dynamic user-level edits with validation, and upgrade data enables version-specific updates. This dynamic approach balances accessibility with security and storage management.
3Reliability
If data validation and authentication are performed for each access request, then data security is improved, but processing time increases
Solution Approach 1:
The patent performs preliminary authentication and validation actions during data delivery and initial access setup. User credentials are verified beforehand, data schemas are validated during the delivery process, and access permissions are pre-configured based on user roles and data types. This preliminary action reduces the validation overhead during subsequent access requests while maintaining strong security.
Solution Approach 2:
The patent creates validated copies of data with embedded metadata including authentication tokens, permission sets, and validation results. Once data is delivered and validated, these copies can be accessed with reduced verification overhead while maintaining security through embedded credentials and permission checks. This copying mechanism reduces processing time for repeated accesses while preserving security.
Data Source
AI summary
A method, a system, and computer program product for managing data are provided. A request to access data from a table including the data and metadata associated with the data is received. The request to determine one or more relevant portions of the data is processed. A file corresponding to the one or more relevant portions of the data is generated by using the metadata. A repository object is generated from the file. A response to the request is transmitted. The response can provide access to update the relevant portions of the data in the repository object.