Automatic Asset Versioning via Embedded Metadata
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for tracking and managing electronic assets are inefficient, particularly in versioning and audit history, due to reliance on user discipline, costly document management systems, and integration issues with asset editors, leading to lost or unavailable data when systems are offline.
Innovation Solution
A method that detects new assets, requests advice on tracking, assigns unique identifiers, and records versioning information in metadata, allowing for automatic asset tracking and version management without requiring constant system integration or user intervention, and enabling reconstruction of audit histories even when systems are offline.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a document management system is deployed to track and manage electronic assets, then asset tracking reliability is improved, but device complexity and cost increase
Solution Approach 1:
The patent applies self-service by embedding versioning information directly into the asset files themselves during creation or modification. The asset generating application automatically records version data in the asset's inherent structure (such as file metadata or embedded records), allowing the asset to carry its own versioning information without requiring external document management systems. This eliminates the need for complex separate tracking systems while maintaining reliable version information.
2Ease of operation
If a document management system is integrated with asset editors to enable automatic tracking, then asset tracking capability is improved, but ease of operation deteriorates due to frequent integration requirements with new editors
Solution Approach 1:
The patent achieves universality by creating a versioning mechanism that is independent of any specific asset generating application. The system records versioning information in a standardized format that can be embedded in assets regardless of which application created or modified them. This universal approach allows the same versioning mechanism to work with current and future applications without requiring integration with each specific editor, thereby improving ease of operation while maintaining broad adaptability.
3Ease of operation
If manual naming schemes are used to track asset versions, then ease of operation is improved, but manufacturing precision deteriorates due to lack of automated version control
Solution Approach 1:
The patent replaces the mechanical system of manual naming conventions with an automated digital recording mechanism. Instead of relying on users to manually create and maintain version-specific file names, the system automatically records versioning information directly in the asset files through programmatic operations. This substitution maintains the simplicity of operation (users don't need to remember naming schemes) while dramatically improving version control accuracy through automated, consistent recording by the system itself.
4Measurement precision
If audit history is stored in a separate document management system, then measurement precision of audit history is improved, but loss of information occurs when the system is offline or replaced
Solution Approach 1:
The patent merges the audit history information with the asset itself by embedding versioning records directly in the asset files. Rather than storing audit history separately in an external document management system, the versioning information is combined with the asset in a self-contained manner. This ensures that the audit history travels with the asset and remains accessible even when external systems are offline or replaced, eliminating information loss while maintaining accurate version tracking.
Data Source
AI summary
Assets or the locations where assets may appear are monitored. If a new asset appears within a monitored location or if an existing asset is copied, modified, or moved, a decision is made as to whether to assign a new unique identifier or to assign a new version number to an existing unique identifier. The unique identifiers and version numbers are carried as metadata within the assets and optionally also stored separately within a data store.