Tag-Based Hierarchy for Document Organization and Retrieval

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data storage systems, such as flat files and relational databases, are poorly structured for data analysis, making it difficult for users to efficiently modify data structures, especially when multiple users access and update them, and current graphical user interfaces complicate the creation and management of hierarchical structures like trees and tags.

Innovation Solution

A system that organizes data using a pre-defined hierarchy of tags, allowing users to navigate and retrieve documents associated with selected tags, with an interface that updates based on user input and supports iterative updates through a Git version control system, enabling distributed workflows and conflict resolution.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If data is stored in fixed, rigidly structured data stores (flat files, relational databases), then data storage is organized and accessible, but data analysis becomes inefficient and difficult to reorganize

Engineering Contradiction:
Improvedata analysis efficiencyVSAvoiddata structure rigidity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent implements a dynamic data structure where tags and hierarchies can be modified, added, or removed without rigid constraints. Users can interactively update tag structures, and the system automatically manages dependencies and relationships, transforming fixed data stores into adaptable ones that respond to user actions and analytical needs.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent segments data organization into independent tag units that can be individually managed. Each tag represents a discrete concept or category that can be selectively applied to data elements, allowing granular control over data classification and enabling flexible reorganization without restructuring entire data sets.

Inventive Principle:
Principle #1Segmentation

2Ease of operation

If users modify data structures in systems with multiple users accessing the same data, then data can be updated, but inadvertently changing properties associated with many entities at once becomes difficult to control

Engineering Contradiction:
Improvedata structure modification easeVSAvoiddata update accuracy
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent implements feedback mechanisms that monitor and track changes to tag structures. When a user modifies a tag or hierarchy, the system provides feedback about which data entities are affected, allowing users to review and confirm changes before they are applied, thus preventing inadvertent modifications to numerous entities.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent performs preliminary actions by pre-calculating and displaying the impact of proposed tag structure modifications before they are executed. Users can see which entities will be affected by a change and adjust their actions accordingly, ensuring intentional and accurate updates to data structures.

Inventive Principle:
Principle #10Preliminary action

3Ease of operation

If graphical user interfaces are used to create and manage trees and tags, then user interaction is improved, but the complexity of creating and managing hierarchical structures increases

Engineering Contradiction:
Improvetag creation and management easeVSAvoidhierarchical structure management complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent implements self-service functionality where the system automatically manages tag hierarchies and relationships based on user input. When users create or modify tags, the system autonomously handles the complex tasks of updating hierarchical structures, managing parent-child relationships, and propagating changes throughout the data structure, eliminating the need for users to manually manage complexity.

Inventive Principle:
Principle #25Self-service

4Loss of time

If a pre-defined hierarchy of tags is implemented for organizing data, then navigation and retrieval of documents becomes efficient, but the system complexity increases

Engineering Contradiction:
Improvedata retrieval timeVSAvoidtag hierarchy system complexity
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The patent creates a universal tag hierarchy system that serves multiple functions: organizing data, enabling search and retrieval, supporting data analysis, and facilitating user interaction. This multi-functional approach consolidates what would otherwise require separate systems into a single integrated structure, managing complexity while delivering diverse benefits.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS11704353B2Systems and methods for organizing and identifying documents via hierarchies and dimensions of tags
Publication Date: 2023.07.18 PALANTIR TECHNOLOGIES INC
  • US11704353B2 patent drawing
  • US11704353B2 patent drawing
  • US11704353B2 patent drawing

AI summary

Computer-implemented systems and methods are disclosed to interface with one or more storage devices storing a plurality of documents, wherein each of the plurality of documents is associated with one or more tags of one or more predefined hierarchies of tags, wherein the one or more hierarchies of tags include multiple dimensions. In accordance with some embodiments, a method is provided to identify one or more documents from the data storage devices. The method comprises acquiring, via an interface, a selection of one or more tags of the one or more predefined hierarchies of tags. The method further comprises identifying one or more documents from the data storage devices in response to the selection, the identified one or more documents having tags that have a relationship with the selected tags, and providing data corresponding to the identified documents for displaying in the interface.