File Node Imitation for Container Document Embedding
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Content management systems face challenges in interacting with embedded files and maintaining containment relationships when files are embedded in documents, leading to issues like broken links and loss of functionality during document copying or sharing.
Innovation Solution
The technique imitates file embedding by using file nodes in container documents that point to separate locations, allowing the content management system to provide features like permission management and sharing, while maintaining separate storage of files, thus simulating embedded relationships without actual embedding.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Stability of the object's composition
If a file is embedded in a container document, then the file appears to be part of the document structure, but the content management system cannot interact with the embedded file to provide features
Solution Approach 1:
The patent segments the file embedding relationship into two independent components: a file node within the container document and a separate file stored in the content management system. This segmentation allows the container document to reference the file without containing it, maintaining structural stability while enabling system interaction through the separate file storage.
Solution Approach 2:
The patent introduces a file node as an intermediary element that bridges the container document and the separate file. The file node contains a reference to the file location and maintains the embedded relationship appearance, while the actual file remains separate and accessible to the content management system for feature provision.
2Adaptability or versatility
If a link is inserted into a document to reference a file, then the file can be accessed separately, but the containment relationship breaks during document copying
Solution Approach 1:
The patent merges the advantages of both embedding and linking by combining the visual appearance of embedding with the structural independence of linking. The file node provides embedded-like display within the container document while maintaining separate file storage, ensuring that copying the container document automatically manages the file relationship through the content management system.
3Stability of the object's composition
If a file is embedded in a container document, then the file appears contained, but the file storage location becomes opaque to the content management system
Solution Approach 1:
The patent creates a reference copy mechanism where the file node in the container document contains a reference to the actual file stored in the content management system. This reference copy maintains the embedded appearance in the document structure while preserving the transparency of the actual file location to the content management system, enabling full system interaction.
Data Source
AI summary
A container document can include a file node indicating a file and pointing to a location for the file that is separate from the container document on a server. An embedded relationship between the file and the container document can be imitated. The imitation can include responding to user input by performing the update on the file node, and by requesting that the server perform an update on the file that reflects the update performed on the file node. A request for an update to be performed on the file node can be received from a client at the server. In response to the request, the update can be performed on the file node at the server. A corresponding update, which reflects the update performed on the file node, can also be performed on the file at the server.