Link Document Synchronization for Enterprise Content Sharing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing content management systems do not support seamless sharing of content across repositories, requiring manual downloading and uploading, which is inconvenient and inflexible, hindering cross-repository business processes.

Innovation Solution

A method for generating a link document in a second repository that is synchronized with a source document in a first repository, allowing users to interact with content from different repositories without manual transfer, using a content management system with a content sharing controller to manage synchronization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If users manually transfer content between repositories by downloading and uploading, then content can be moved between repositories, but the process is inconvenient and time consuming

Engineering Contradiction:
Improvecontent transfer convenienceVSAvoidcontent transfer time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The system creates a link document that is a copy of the source document, establishing a reference relationship between repositories. This allows content to be accessed across repositories without manual downloading and uploading, resolving the contradiction by enabling automatic content sharing while maintaining the original in the source repository.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The link document acts as an intermediary between the source document and users in different repositories. It provides a mechanism for cross-repository content access without requiring direct manual transfer, thus improving convenience and reducing time loss.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If users store all content in a single consolidated repository, then content access is simplified, but the system becomes inflexible and hard to maintain

Engineering Contradiction:
Improvecontent access simplicityVSAvoidrepository flexibility
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The link document mechanism provides multi-functionality: it maintains separate repository structures while enabling cross-repository content sharing. Users can access content from different repositories as if it were consolidated, preserving flexibility and maintainability while achieving simplified content access.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system segments content into source documents and link documents across different repositories. This segmentation allows each repository to maintain its own structure and purpose while still enabling unified content access through the link document mechanism, resolving the contradiction between consolidation and flexibility.

Inventive Principle:
Principle #1Segmentation

3Adaptability or versatility

If content is shared across repositories without synchronization mechanism, then access is enabled, but content consistency cannot be maintained

Engineering Contradiction:
Improvecross-repository content sharingVSAvoidcontent consistency
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The synchronization mechanism establishes a feedback loop where changes to the source document are detected and automatically propagated to the link document. This ensures content consistency across repositories while maintaining the ability to share content, resolving the contradiction between versatility and reliability.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS11087082B1System and method for content sharing in enterprise content management
Publication Date: 2021.08.10 VEEVA SYSTEMS INC
  • US11087082B1 patent drawing
  • US11087082B1 patent drawing
  • US11087082B1 patent drawing

AI summary

Systems and methods for re-using content in a content management system. The content management system may have two or more repositories. A link document may be generated in a link repository for a source document in a source repository. The link document may be a copy of the source document, and synchronized to the source document in a number of different ways, dynamically or statically. When the source document is updated, the source repository may notify the link repository about the change, receive a pull request from the link repository for the change, and generate an updated link document.