Relational Metadata Cards for File Consistency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current data repositories lack the ability to explicitly relate files to each other, leading to inefficiencies in managing and updating files, especially in large repositories with thousands of files and globally distributed users.

Innovation Solution

A method is introduced that uses file metadata cards and a relational metadata map to link files within a data repository. This system allows for the enforcement of rules related to file relationships, ensuring data consistency and triggering actions such as notifications when changes affect related files.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If files are stored as stand-alone files without explicit relationships, then the repository structure is simple and easy to manage, but the ability to track and enforce data consistency across files is lost

Engineering Contradiction:
Improveease of file managementVSAvoiddata consistency
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent segments file relationships into discrete metadata cards associated with each file. Each metadata card independently stores relationship information (e.g., 'This file must be updated when file X is updated'), allowing the system to maintain simplicity while enabling reliable tracking of data consistency across files through structured metadata segments.

Inventive Principle:
Principle #1Segmentation

2Device complexity

If manual tracking of file relationships is used, then the system remains simple, but the time required to identify and update affected files increases significantly

Engineering Contradiction:
Improvesystem complexityVSAvoidtime to identify and update files
Core Design Contradiction:
Device complexityVSLoss of time

Solution Approach 1:

The patent implements preliminary action by pre-establishing and storing relationship metadata cards for all files before changes occur. When a file is updated, the system queries these pre-stored metadata cards to automatically identify all affected files, eliminating the need for manual relationship tracking and significantly reducing update time.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms where updated files automatically trigger notifications to users who need to update their files. This closed-loop feedback system ensures that relationship changes are promptly communicated and acted upon, reducing the time loss associated with manual tracking.

Inventive Principle:
Principle #23Feedback

3Ease of operation

If basic folder organization is provided, then the repository is easy to use, but the ability to validate data and enforce relationships is insufficient

Engineering Contradiction:
Improveease of useVSAvoiddata validation accuracy
Core Design Contradiction:
Ease of operationVSManufacturing precision

Solution Approach 1:

The patent introduces metadata cards as intermediary objects between files and the validation system. These metadata cards carry relationship information and validation rules, acting as mediators that enable accurate data validation while maintaining the simplicity of the overall system architecture.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS12287775B2Smart repository based on relational metadata
Publication Date: 2025.04.29 THE BOEING CO
  • US12287775B2 patent drawing
  • US12287775B2 patent drawing
  • US12287775B2 patent drawing

AI summary

Methods, servers, and computer program products are provided to link files stored in a data repository. A file to be stored in the data repository is received, via a network, from a terminal. The method includes determining whether the file has a file metadata card associated with the file. The method further includes responsive to the file having a file metadata card associated with the file: executing at least one rule responsive to receiving the file being stored in the data repository to validate the file metadata card. The method further includes responsive to a result of the at least one rule executed indicating a successful result, storing the file metadata card associated with the file and the file in the data repository.