Scene Description Database for Digital Asset Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current computer graphics systems face challenges in efficiently managing and modifying digital assets due to complex file system hierarchies and limited search capabilities, making it difficult to handle large numbers of inter-related data files and perform specific modifications.
Innovation Solution
Storing digital production assets and their attributes directly in a scene description database, allowing for database queries to retrieve and modify assets without loading entire data files, and using layering and caching to improve performance and enable complex queries.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If digital assets are stored in complex hierarchical file systems, then data organization is achieved, but managing and modifying individual assets becomes difficult and time-consuming
Solution Approach 1:
The patent introduces a database as an intermediary layer between the file system and the application. The database stores metadata about digital assets and enables queries without requiring the application to navigate complex file hierarchies or load entire data files. This mediator simplifies asset management operations while the underlying file system maintains its organizational structure.
2Measurement precision
If entire data files are loaded to search or modify assets, then complete data access is achieved, but processing time increases significantly
Solution Approach 1:
The patent extracts only the necessary metadata from complete data files and stores it in a database. When searching or modifying assets, the system queries this extracted metadata rather than loading entire data files. This extraction principle enables precise searching based on asset attributes while avoiding the time cost of processing complete file contents.
Solution Approach 2:
The system performs partial action by loading and processing only the metadata portion of digital assets that is necessary for searching and identification, rather than loading the complete asset data. This partial processing achieves the search function with significantly reduced processing time, and only loads full asset data when actually needed for modification or rendering.
3Adaptability or versatility
If metadata summarizes digital asset contents, then search capabilities are enabled, but unrestricted modification of arbitrary attributes is limited
Solution Approach 1:
The database schema is designed to be universal and flexible, accommodating various types of digital assets with different attributes. The system uses a standardized metadata structure that can represent diverse asset types while maintaining consistent query and modification operations. This universal structure enables both flexible searching across different asset types and unrestricted modification of any attributedata.
Data Source
AI summary
Digital production assets and their attributes are stored directly in a scene description database, without any association with a specific enclosing asset data file. Software applications perform database queries to retrieve assets and attributes from the database. Changes to assets or new assets are stored in the database. Query results may be cached to improve performance. Heterogeneous opinion sets including sparse opinions of attribute values may be used to specify scene description data. The database stores heterogeneous opinion set data in association with attribute values. Database-aware applications may change the scene description data in the database without loading, parsing, and instantiating scene description data. An application generates database queries and instantiates scene description data from query results for access and manipulation by other applications.