Wiki Annotation Persistence via Segmented Storage

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In enterprise wiki environments, users face the challenge of maintaining customized documentation that is both up-to-date and personalized, as updates to wiki pages often overwrite local, customized information, forcing users to choose between outdated customized content or updated content without annotations.

Innovation Solution

A method and system for assembling customized documentation by storing annotations to an original version of a document, receiving and updating the document based on differences with the original, and associating these annotations with the updated version, allowing for a personalized version that combines up-to-date content with custom information.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If wiki pages are updated to maintain up-to-date content, then information currency is improved, but local customized annotations are lost

Engineering Contradiction:
Improveinformation currencyVSAvoidcustomized annotations
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The system segments documentation into base wiki content and user annotations as separate components. Annotations are stored independently in an annotation database rather than being embedded in the wiki page structure, allowing them to be preserved separately from content updates.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary actions by storing user annotations locally before wiki content updates occur. This allows annotations to be preserved and reapplied to updated content, preventing information loss during the update process.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If users maintain local customized documentation, then personalization is improved, but content becomes outdated

Engineering Contradiction:
Improvedocumentation personalizationVSAvoidcontent currency
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system implements feedback mechanisms where users are notified when wiki content is updated. Users can then choose to synchronize their local copies with the latest version while preserving their annotations, creating a continuous improvement cycle.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system makes the documentation dynamic by allowing users to selectively update content while maintaining their customizations. Users can control the update process to balance between receiving latest information and preserving their personal adaptations.

Inventive Principle:
Principle #15Dynamics

3Stability of the object's composition

If wiki content is synchronized centrally, then information consistency is improved, but user customizations are overwritten

Engineering Contradiction:
Improveinformation consistencyVSAvoiduser customizations
Core Design Contradiction:
Stability of the object's compositionVSAdaptability or versatility

Solution Approach 1:

The system applies local quality by allowing different versions of content for different users. Each user maintains their own customized version with local annotations while the central wiki maintains the authoritative base content.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system uses a local annotation database as an intermediary layer between central wiki content and user applications. This intermediary preserves user customizations while allowing central content updates to flow through without direct overwriting.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Adaptability or versatility

If users manually maintain annotations during updates, then customization preservation is improved, but time consumption increases

Engineering Contradiction:
Improveannotation preservationVSAvoidmaintenance time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system implements self-service by automatically managing annotation persistence and retrieval. The annotation database automatically stores, retrieves, and reapplies annotations without requiring user intervention during content updates.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs preliminary actions by pre-storing annotations in a persistent database before content updates occur. This eliminates the need for manual annotation management during updates, significantly reducing time consumption.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10210149B2Personalized wiki-book annotation
Publication Date: 2019.02.19 CA TECH INC
  • US10210149B2 patent drawing
  • US10210149B2 patent drawing
  • US10210149B2 patent drawing

AI summary

Assembling customized documentation includes storing annotations to an original version of a document and receiving a new version of the document, wherein the new version of the document is different than the original version of the document. The assembling further includes storing an updated version of the document based on differences between the original version and the new version of the document; and associating the annotations with the updated version of the document, wherein the associated annotations and the updated version of the document form a personalized version of the document.