On-Demand Content Bursting in CMS

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing content management systems face challenges in efficiently reusing content due to difficulties in determining optimal bursting rules, leading to either inadequate reuse or decreased system performance, and users struggle to identify suitable elements for reuse during document creation or editing.

Innovation Solution

The implementation of an on-demand bursting mechanism that allows users to search for and extract specific elements from documents, creating separate documents in the repository and inserting links, while handling both mutable and immutable parent documents through version policies, independent of existing rules-based and user-requested bursting methods.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If system-level bursting rules generate larger chunks, then system performance is improved, but content reusability decreases

Engineering Contradiction:
Improvesystem performanceVSAvoidcontent reusability
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent implements dynamic bursting that adapts the granularity of content chunks based on runtime conditions and user needs. Instead of using fixed static rules, the system dynamically determines whether to burst content into fine-grained or coarse-grained chunks based on the specific context, thereby resolving the contradiction between system performance and content reusability.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system changes the parameter of chunk size dynamically based on user requirements and context. By allowing the bursting granularity parameter to vary rather than remain fixed, the system can optimize for either performance or reusability depending on the situation, thus resolving the technical contradiction.

Inventive Principle:
Principle #35Parameter changes

2Adaptability or versatility

If system-level bursting rules generate smaller chunks, then content reusability increases, but system performance decreases

Engineering Contradiction:
Improvecontent reusabilityVSAvoidsystem performance
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent implements dynamic bursting that adapts the granularity of content chunks based on runtime conditions and user needs. Instead of using fixed static rules, the system dynamically determines whether to burst content into fine-grained or coarse-grained chunks based on the specific context, thereby resolving the contradiction between system performance and content reusability.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system changes the parameter of chunk size dynamically based on user requirements and context. By allowing the bursting granularity parameter to vary rather than remain fixed, the system can optimize for either performance or reusability depending on the situation, thus resolving the technical contradiction.

Inventive Principle:
Principle #35Parameter changes

3Ease of operation

If user-level bursting is used, then author flexibility is improved, but content reuse is significantly reduced

Engineering Contradiction:
Improveauthor flexibilityVSAvoidcontent reuse
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent enables authors to perform intelligent self-service bursting by providing them with tools to identify and burst reusable content elements. The system assists authors in automatically identifying candidate elements for bursting based on analysis of their document structure and content, thereby improving both author flexibility and content reusability simultaneously.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system provides feedback to authors by analyzing their documents and identifying elements that are good candidates for bursting. This feedback mechanism guides authors in making informed decisions about what to burst, improving both the ease of operation and the effectiveness of content reuse.

Inventive Principle:
Principle #23Feedback

4Productivity

If system administrator sets strict bursting rules, then system performance is improved, but content reuse effectiveness decreases

Engineering Contradiction:
Improvesystem performanceVSAvoidcontent reuse effectiveness
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent implements dynamic bursting that adapts the granularity of content chunks based on runtime conditions and user needs. Instead of using fixed static rules, the system dynamically determines whether to burst content into fine-grained or coarse-grained chunks based on the specific context, thereby resolving the contradiction between system performance and content reusability.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS8122348B2On-demand bursting in a content management system
Publication Date: 2012.02.21 SERVICENOW INC
  • US8122348B2 patent drawing
  • US8122348B2 patent drawing
  • US8122348B2 patent drawing

AI summary

When creating or editing a document in a content management system and specific content is needed, documents in the repository are searched for an element that has the desired content. If an element is found in a document in the repository that has the desired content, the element is bursted on-demand by extracting the element from the parent document where it was found and creating a document in the repository for the element. A link that points to the bursted document in the repository is then inserted into the document that needed the element. If the parent document from which the element was extracted is mutable, then the element in the parent document is replaced with a link to the bursted document. If the parent document is immutable, a copy of the content is created as a document in the repository, and a version policy corresponding to the parent document is stored so that if the parent document becomes mutable, the parent document will include information in the version policy to allow linking to the bursted document.