Context-Aware Issue Reporting Plug-in for Structured Data

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing software programs for structured data presentation, analysis, and management lack effective reporting mechanisms that capture sufficient context for efficiently processing and resolving issues, leading to delayed issue resolution and redundant reporting.

Innovation Solution

A plug-in module automatically captures structured metadata when users report issues within application software, storing records in a database and prioritizing issue resolution by gathering context such as location, user activity, and metadata, and strategically displaying relevant issues to reduce redundancy.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a reporting mechanism is built into application software, then issue reporting capability is improved, but the complexity of the software system increases

Engineering Contradiction:
Improveissue reporting capabilityVSAvoidsoftware system complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

A plug-in module is introduced as an intermediary component that bridges the application software and the issue tracking system. This plug-in captures structured metadata automatically and transmits it to an issue tracking system, enabling issue reporting without significantly increasing the complexity of the core application software.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system automatically captures structured metadata (such as user profile information, application state, and contextual data) without requiring manual input from users. This self-service approach simplifies the reporting process while maintaining comprehensive issue context.

Inventive Principle:
Principle #25Self-service

2Quantity of substance

If limited context is captured for reported issues, then the data storage requirements are reduced, but the ability to resolve complex data issues efficiently deteriorates

Engineering Contradiction:
Improvedata storage requirementsVSAvoidissue resolution efficiency
Core Design Contradiction:
Quantity of substanceVSProductivity

Solution Approach 1:

The system extracts only the essential structured metadata needed for issue resolution (such as location within structured data, user profile, and application state) while discarding unnecessary information. This extraction approach reduces storage requirements while maintaining sufficient context for efficient issue resolution.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

Different types of context information are captured with appropriate levels of detail based on their specific utility for issue resolution. Critical information such as data location and user context is captured in detail, while less relevant information is captured at a summary level, optimizing both storage efficiency and resolution capability.

Inventive Principle:
Principle #3Local quality

3Device complexity

If issues are not displayed to subsequent users, then the system simplicity is maintained, but redundant issue reporting increases

Engineering Contradiction:
Improvesystem simplicityVSAvoidredundant reporting time
Core Design Contradiction:
Device complexityVSLoss of time

Solution Approach 1:

The system implements a feedback mechanism where previously reported issues are displayed to subsequent users viewing the same structured data. This feedback loop prevents redundant reporting by informing users of existing issues, reducing time loss while maintaining system simplicity through a straightforward display mechanism.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10817362B1Automatic contextualization for in-situ data issue reporting, presentation and resolution
Publication Date: 2020.10.27 TAMR INC
  • US10817362B1 patent drawing
  • US10817362B1 patent drawing
  • US10817362B1 patent drawing

AI summary

Structured metadata is automatically captured regarding issues reported by a user when the user interacts with application software for presentation, analysis, or management of structured data. The reported issues correspond to structured data that is displayed by the application software. During user interaction with the application software, a user interface display screen is presented that includes one or more fields for reporting an issue with respect to structured data that is presently being displayed by the application software. Structured metadata is then automatically captured related to the reported issue. The structured metadata includes at least a location within the structured data for the reported issue. Records are stored of each reported issue in a database. Each record includes the reported issue, and the automatically captured structured metadata related to the reported issue.