Incremental Label Storage for Collaboration Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing collaboration systems require redundant storage of label applications for each version and type of object, leading to inefficient memory usage and slower execution due to the need to store multiple copies of the same label applications.

Innovation Solution

Implementing a system where labels are stored incrementally, with a full label application and incremental changes, using unique identifiers to maintain a common repository, allowing efficient storage and retrieval of label applications across multiple types and versions without replicating label applications for each object version.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If label applications are stored individually for each object version and type, then complete label information is available for each object, but memory consumption increases and storage efficiency decreases

Engineering Contradiction:
Improvelabel information completenessVSAvoidmemory consumption
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent merges duplicate label application data across multiple objects and versions into a single shared storage location. Instead of storing complete label applications separately for each tagged object, the system stores one master copy and maintains references to it from multiple objects, thereby reducing memory consumption while preserving label information completeness.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent creates a universal label application storage structure that serves multiple objects and versions simultaneously. A single label application definition can be referenced by multiple tagged objects of different types and versions, making the storage system multi-functional and eliminating redundant storage across different object instances.

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

2Productivity

If multiple copies of the same label application are stored for different object versions, then each object has its own label data, but storage efficiency decreases and retrieval time increases

Engineering Contradiction:
Improvelabel retrieval efficiencyVSAvoidstorage space
Core Design Contradiction:
ProductivityVSQuantity of substance

Solution Approach 1:

The patent uses a reference copying mechanism where instead of storing complete duplicate label applications for each object, the system creates lightweight references or pointers to the master label application definition. This allows rapid retrieval through reference lookup while maintaining only one actual copy of the label data in storage.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent pre-establishes a centralized label application repository that stores master definitions before they are needed by multiple objects. This preliminary organization of label data enables efficient retrieval operations, as the system only needs to resolve references rather than search through or reconstruct label applications from multiple scattered copies.

Inventive Principle:
Principle #10Preliminary action

3Quantity of substance

If label applications are overwritten instead of being incrementally updated, then storage space is conserved, but the ability to track label changes and maintain version history is lost

Engineering Contradiction:
Improvestorage efficiencyVSAvoidlabel change history
Core Design Contradiction:
Quantity of substanceVSLoss of information

Solution Approach 1:

The patent implements a dynamic label application storage system that can track changes over time. Instead of static overwriting, the system maintains the master label application definition and uses incremental updates or versioning mechanisms to preserve change history, allowing the storage structure to adapt between space efficiency and information preservation based on requirements.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS8805785B2Shared storage of categorization, labeling or tagging of objects in a collaboration system
Publication Date: 2014.08.12 ORACLE INT CORP
  • US8805785B2 patent drawing
  • US8805785B2 patent drawing
  • US8805785B2 patent drawing

AI summary

A computer that is programmed with collaboration software receives a new value of an attribute (or property or characteristic) which is specific to a label (or tag or category) as applied to an object managed by the computer. The computer does not use the new value to overwrite a corresponding old value in existing metadata. Instead, the computer is programmed to hold the new value in an incremental label application for the object. The computer is further programmed to respond to a request for the object's label application, by retrieving the incremental label application, and a full application of said label to said object. The computer uses attribute values in the incremental label application to update corresponding attribute values in a copy of the full label application, in a time sequence based on the time of creation of incremental label applications, thereby to generate a current label application.