Meta Schema Querying for Hierarchical Metadata Search
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Cloud-based content management systems face challenges in efficiently querying metadata due to the need for multiple schemas for different document types, which is impractical for large-scale multi-tenancy systems, and flattening documents loses hierarchical search capabilities.
Innovation Solution
Implementing a single meta schema to generate a query schema dynamically for metadata queries, allowing scalable metadata processing without maintaining separate schemas for each document type.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a separate schema is created for each document type, then hierarchical search capabilities are preserved, but system complexity and scalability deteriorate due to the need to manage millions of schemas in multi-tenancy systems
Solution Approach 1:
The patent merges the functionality of multiple document-type-specific schemas into a single universal schema that can handle diverse document types. This universal schema incorporates field type definitions and validation rules that can be dynamically applied to different document types, eliminating the need to maintain separate schemas for each document type while preserving hierarchical search capabilities.
Solution Approach 2:
The patent creates a universal schema that serves multiple document types simultaneously. This schema is designed with flexible field definitions that can accommodate various document structures through configuration rather than requiring separate schema instances. The schema includes mechanisms for defining repeating fields, nested structures, and field validation rules that can be adapted to different document types without compromising hierarchical query functionality.
2Device complexity
If documents are flattened for searching, then schema management complexity is reduced, but hierarchical search capabilities are lost
Solution Approach 1:
The patent implements a dynamic schema system where the universal schema can adapt its structure and field definitions based on the specific document type being queried. The schema includes configurable field templates and validation rules that are dynamically instantiated when processing queries for different document types, allowing the system to maintain hierarchical awareness without requiring static separate schemas for each document type.
Solution Approach 2:
The patent adds a configuration dimension to the schema system, where field definitions and hierarchical structures are specified through configurable parameters rather than fixed schema definitions. This allows the same universal schema to represent different hierarchical structures by changing configuration values, effectively adding a layer of abstraction that preserves hierarchical search capabilities without requiring multiple concrete schema instances.
3Adaptability or versatility
If a single universal schema is used, then scalability and ease of maintenance improve, but the ability to handle document-type-specific structures may deteriorate
Solution Approach 1:
The patent applies local quality by allowing different sections or fields within the universal schema to have specialized definitions tailored to specific document types. The schema supports field-level configuration where each field can have its own data type, validation rules, and hierarchical relationships defined locally, enabling precise handling of document-type-specific structures while maintaining the benefits of a single unified schema framework.
Data Source
AI summary
Disclosed is an improved approach to implement metadata queries, e.g., for content stored in a cloud-based content management system. Instead of being required to create and maintain a separate schema for each document type stored within the system, a single meta schema can be employed to facilitate processing for the metadata query. The meta schema is used to generate a query schema for processing of a query against metadata.