Template File Sharing via Encoded Link Distribution

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional content management systems require time-consuming processes for sharing documents with multiple recipients, such as generating separate folders and sharing each folder individually, which is inefficient for non-collaborative purposes like distributing worksheets to students.

Innovation Solution

A system that allows a template sharer to distribute a single template file by generating a link encoding a template file identifier, enabling each recipient to access and modify their own template instance file independently, with the sharer able to access all instance files in a shared folder.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a teacher generates separate folders for each student and shares each folder individually, then each student can receive their own copy of the worksheet, but the process becomes time-consuming and inefficient

Engineering Contradiction:
Improveease of sharing documentVSAvoidtime required for sharing process
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The patent merges multiple separate sharing operations into a single unified action. Instead of creating separate folders and sharing each individually, the system allows a user to select multiple recipient accounts and share the document with all of them simultaneously through one operation, thereby reducing the time and effort required

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The system automatically generates and distributes copies of the document to multiple recipients at once. When a user shares a document with multiple accounts, the system creates individual copies for each recipient and delivers them simultaneously, eliminating the need for manual folder creation and individual sharing steps

Inventive Principle:
Principle #26Copying

2Productivity

If a user shares a single template file with multiple recipients, then distribution is efficient, but each recipient needs to modify their own copy independently without affecting others

Engineering Contradiction:
Improvedistribution efficiencyVSAvoidsystem complexity for independent modification
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system segments the shared document into individual copies for each recipient. When a document is shared with multiple accounts, the system creates distinct instances of the document that are associated with specific recipient accounts, allowing each recipient to modify their own copy independently while the system manages the segmentation automatically

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system acts as an intermediary that manages the relationship between the original template and multiple recipient copies. It automatically handles the creation, distribution, and synchronization of document instances, freeing recipients from managing the complexity of independent modifications while ensuring each works on their own copy

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10078433B2Sharing a template file
Publication Date: 2018.09.18 DROPBOX INC
  • US10078433B2 patent drawing
  • US10078433B2 patent drawing
  • US10078433B2 patent drawing

AI summary

A method for sharing one file with many. To share a file, a template sharer selects a file in a shared folder to share as a template file and enters a template share command. In response to the entered command, a template file identifier is encoded and an email message is sent to recipients associated with the shared folder. The email message contains a link encoding the template file identifier. The email messages are sent to the recipients who can then access the link in the email message to retrieve their template instance file. Any modifications to a template instance file are saved. Each template instance file is saved in the collection folder. Thus, the template sharer has access to all of the template instance files.