Usage Information Integration in Content Management Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing analytics data systems do not effectively integrate usage information to enhance the operation of content management systems, such as filtering search results or adjusting retention and backup policies based on user interaction data.

Innovation Solution

The integration of usage information into the operation of a content management system, where usage data is collected and analyzed to filter search results, adjust retention times, crawl policies, backup schedules, and storage tier levels, and provide personalized recommendations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If usage information is collected and integrated into the content management system, then user experience and system operation optimization are improved, but system complexity and data processing requirements increase

Engineering Contradiction:
Improveuser experienceVSAvoidsystem complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The system segments usage information collection and processing into distinct modules: usage data collection from user interactions, usage information storage in databases, usage data analysis engines, and application modules that implement specific optimizations. This segmentation allows the system to manage complexity through modular architecture while still achieving integrated usage-based optimization across search, retention, backup, and storage functions.

Inventive Principle:
Principle #1Segmentation

2Measurement precision

If usage information is collected and analyzed at multiple levels, then personalized recommendations and filtered results are improved, but data processing time and computational resources increase

Engineering Contradiction:
Improverecommendation accuracyVSAvoiddata processing time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system performs preliminary actions by pre-collecting and pre-processing usage information as it naturally occurs during user interactions. Usage data is continuously captured and stored in databases during normal system operation, rather than being collected on-demand. This preliminary accumulation of usage information allows for faster query processing and recommendation generation when users interact with the system, as the data is already organized and ready for analysis.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If usage information is used to adjust system operations such as retention time and backup policy, then content management efficiency is improved, but system control complexity increases

Engineering Contradiction:
Improvecontent management efficiencyVSAvoidsystem control complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system implements feedback mechanisms where usage information collected from user interactions continuously informs and adjusts system operations. Usage data regarding content access patterns, user preferences, and interaction frequencies feeds back into automated decision-making processes that dynamically adjust retention policies, backup schedules, storage tier assignments, and search result filtering. This feedback loop enables automated optimization of content management operations based on actual usage patterns, improving efficiency while managing control complexity through algorithmic automation.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS9466065B2Integrating usage information with operation of a system
Publication Date: 2016.10.11 MICROSOFT TECHNOLOGY LICENSING LLC
  • US9466065B2 patent drawing
  • US9466065B2 patent drawing
  • US9466065B2 patent drawing

AI summary

Usage information relating to interaction with content is integrated with operation of a system, such as a content management system. The usage information is collected, stored and provided to the system. The usage information may be integrated with the operation of the system in many different ways (e.g. recommendations for other content, most viewed content, most “liked” content, content viewed by a type of user, and the like). The usage information may also be used to adjust different operations of the service. For example, the usage information may be used to adjust: a retention time of content (e.g. don't delete a recently viewed document), a crawl policy of content; a backup policy of content; restore schedules; identification of storage tier levels; and the like.