Content Management System Metadata Update Optimization

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Content management systems face inefficiencies due to repetitive database queries for system configuration information and metadata when handling large volumes of similar content items, leading to redundant operations and potential inconsistencies in cached data.

Innovation Solution

Treating a group of content management system commands as a related set allows for updating content management system configuration and metadata only once within a defined scope, reducing repetitive queries and ensuring consistent data usage across related operations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If database queries are executed for each content item operation to ensure up-to-date configuration information, then data consistency is maintained, but system performance deteriorates due to repetitive queries

Engineering Contradiction:

Improvedata consistencyVSAvoidsystem performance

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The system performs preliminary actions by checking whether configuration information has changed before executing operations. A change detector monitors for changes and sets flags when changes occur, allowing the system to prepare in advance rather than querying the database repeatedly during content item operations.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system serves itself by maintaining local copies of configuration information and automatically detecting changes through a change detector mechanism. This self-service approach eliminates the need for external database queries during routine operations, improving performance while maintaining consistency.

Inventive Principle:

Principle #25Self-service

2Ease of manufacture

If multiple separate caches are used to store different types of configuration information, then data organization is improved, but system complexity increases due to multiple caching policies and maintenance requirements

Engineering Contradiction:

Improvedata organizationVSAvoidcaching system complexity

Core Design Contradiction:

Ease of manufactureVSDevice complexity

Solution Approach 1:

The system implements a universal cache structure that can store multiple types of configuration information (system configuration, metadata, access control lists, policies) in a unified manner. This single cache structure serves multiple functions, eliminating the need for separate caches and their associated complexity while maintaining organized data storage.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

While using a unified cache structure, the system segments configuration information by organizing it into different categories (system configuration, metadata, ACLs, policies) that can be independently managed and retrieved. This segmentation within unity allows efficient data organization without requiring separate physical caches.

Inventive Principle:

Principle #1Segmentation

Data Source

PatentUS8990440B2Reusing system configuration information and metadata for related operations

Publication Date: 2015.03.24 OPEN TEXT CORP

AI summary

Reusing system configuration information and metadata for related operations is disclosed. It is determined that a group of content management system commands may be treated as a related set for purposes of updating content management system configuration information and/or metadata. The content management system configuration information and/or metadata are updated once for purposes of processing the group.