Content Visualization System for User Interaction Tracking

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Popular content repositories and social collaborative networks face challenges in tracking and comprehending user interactions, such as commenting and rating, due to the vast amount of content and activities, making it difficult to visualize and manage these interactions effectively.

Innovation Solution

A system that includes a preference system with a web module and database infrastructure to collect, manage, and visualize content contributions and user interactions, allowing users to submit, digg, bury, and comment on content, with features like promotion thresholds, friend activities, and visualization interfaces to display real-time preference events.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If users can freely comment and rate content on social collaborative networks, then user engagement and content quality improve, but tracking and comprehending user interactions becomes difficult due to the vast amount of activities

Engineering Contradiction:
Improveuser engagementVSAvoidtracking user interactions
Core Design Contradiction:
Adaptability or versatilityVSDifficulty of detecting and measuring

Solution Approach 1:

The patent transforms the tracking of user interactions by adding a visual dimension. Instead of presenting interaction data in traditional tabular or textual formats, the system uses graphical visualizations such as heat maps, bar charts, and network graphs to represent user activities. This dimensional transformation makes it easier to comprehend and track interactions across vast amounts of content by converting abstract data into intuitive visual patterns that can be quickly analyzed.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Quantity of substance

If the system collects and stores vast amounts of content and user interactions, then comprehensiveness of data improves, but system complexity and difficulty of management increase

Engineering Contradiction:
Improvedata comprehensivenessVSAvoidsystem management complexity
Core Design Contradiction:
Quantity of substanceVSDevice complexity

Solution Approach 1:

The patent extracts and separates the visualization function from the data storage and management functions. The system maintains a comprehensive database of content and user interactions, but the complexity of managing this vast data is reduced by extracting the analytical and presentation layer into dedicated visualization modules. This allows the core storage system to remain simple while the visualization layer handles the complexity of processing and displaying comprehensive data.

Inventive Principle:
Principle #2Taking out (Extraction)

3Reliability

If promotion thresholds are implemented to promote relevant content, then content quality improves, but spam and inaccuracies still persist requiring additional filtering mechanisms

Engineering Contradiction:
Improvecontent qualityVSAvoidspam and inaccuracies
Core Design Contradiction:
ReliabilityVSObject-generated harmful factors

Solution Approach 1:

The patent implements feedback mechanisms where user interactions (such as comments, ratings, and shares) are continuously monitored and fed back into the content promotion system. Promotion thresholds are dynamically adjusted based on this feedback, allowing the system to learn from user behavior patterns. This feedback loop helps identify and filter spam and inaccurate content by detecting anomalies in interaction patterns, thereby maintaining content quality while reducing harmful factors.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10067662B2Content visualization
Publication Date: 2018.09.04 MICROSOFT TECHNOLOGY LICENSING LLC
  • US10067662B2 patent drawing
  • US10067662B2 patent drawing
  • US10067662B2 patent drawing

AI summary

Displaying a preference by a user of a content contribution is disclosed. A preference event by the user is detected. A plurality of detected events is stored. In response to a query from a client, at least a portion of the stored detected events is stored. At least a portion of the received events is displayed in an interface.