Micro Objects for Context-Dependent Content Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing content management systems are limited in their ability to modify or extend functionality without requiring significant resources and time, as they are restricted to pre-defined constructs and methods for accessing and manipulating content.

Innovation Solution

The use of micro objects that can be associated with objects in a content management system, allowing actions to be applied based on the context of the request, enabling dynamic modification and extension of system functionality by executing specific operations or modifying metadata and content.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If pre-defined constructs and methods are used for content access and manipulation, then system stability is maintained, but adaptability and ease of modification deteriorate

Engineering Contradiction:
ImproveadaptabilityVSAvoidcomplexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the content management system into discrete, independently modifiable components called micro-objects. Each micro-object represents a specific functionality or operation that can be individually created, modified, and associated with content objects through metadata, allowing the system to adapt without requiring changes to the core pre-defined constructs.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces dynamic associability between micro-objects and content objects through metadata relationships. This allows the system to dynamically configure which micro-objects apply to which content objects based on contextual metadata, enabling flexible adaptation while maintaining the stability of the underlying pre-defined constructs.

Inventive Principle:
Principle #15Dynamics

2Ease of operation

If pre-defined constructs and methods are used for content management, then system reliability is maintained, but ease of operation and modification deteriorate

Engineering Contradiction:
Improveease of operationVSAvoidreliability
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent introduces metadata as an intermediary layer between the pre-defined constructs and the micro-objects. This metadata layer provides a simple interface for associating micro-objects with content objects, making the system easier to operate while the underlying pre-defined constructs maintain system reliability through their established validation and execution frameworks.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If micro objects are introduced for dynamic modification, then adaptability is improved, but system complexity increases

Engineering Contradiction:
ImproveadaptabilityVSAvoidcomplexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent creates a universal micro-object framework that can be applied across different content types and management scenarios. The standardized micro-object structure and metadata association mechanism provide multi-functional capabilities, allowing the same framework to handle various adaptation needs without proportionally increasing system complexity.

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

Data Source

PatentUS11630809B2Method and system for using micro objects
Publication Date: 2023.04.18 OPEN TEXT CORP
  • US11630809B2 patent drawing
  • US11630809B2 patent drawing
  • US11630809B2 patent drawing

AI summary

In general, embodiments of the technology relate to a method and system for using micro objects to manage content. More specifically, embodiments of the technology relate to using micro objects to change and/or extend the functionality of the content management system such that the manner in which actions are applied to objects varies based the context of the request that specified an action to be performed on an object.