Centralized Metadata Repository with Relevancy-Scoped Retrieval
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems face challenges in efficiently accessing and managing metadata across multiple clients due to varying relevance and complexity, especially during data replication or federation, leading to resource wastage and increased error risks.
Innovation Solution
A central metadata repository with relevance identifiers allows clients to specify and retrieve relevant metadata subsets, using scoping functions and relevance information to control access and ensure efficient metadata management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If all metadata is stored in a centralized repository for multiple clients, then metadata availability and accessibility are improved, but resource usage and processing overhead increase due to retrieving irrelevant metadata for each client
Solution Approach 1:
The patent segments metadata by associating relevancy identifiers with specific clients, schemas, products, or other contextual entities. This allows the centralized repository to organize metadata into distinct segments that can be selectively retrieved based on client-specific needs, rather than retrieving all metadata for every client request.
Solution Approach 2:
The patent implements local quality by customizing metadata retrieval for each client based on their specific relevancy identifiers. Each client receives a tailored subset of metadata that is locally optimized for their particular needs, schema, or product context, rather than a uniform set of all metadata.
2Loss of information
If complete metadata sets are provided to all clients, then comprehensive information availability is improved, but error risks and processing complexity increase
Solution Approach 1:
The patent extracts only the necessary subset of metadata for each client by filtering based on relevancy identifiers. This extraction process removes irrelevant metadata from the retrieval set, providing clients with comprehensive information about what they need while eliminating extraneous data that could introduce errors or confusion.
3Measurement precision
If metadata retrieval is customized for each client with different relevancy identifiers, then relevance-based accuracy is improved, but system complexity and query processing time increase
Solution Approach 1:
The patent applies preliminary action by pre-associating relevancy identifiers with metadata during the data organization phase. This preliminary tagging and classification work is done in advance, so that when clients make requests, the system can quickly filter and retrieve relevant metadata without performing complex real-time analysis, thus reducing query processing time while maintaining high relevance accuracy.
Data Source
AI summary
Techniques and solutions are described for storing and retrieving metadata for database artefacts. A client request is received that includes a relevancy identifier. The relevancy identifier is useable to determine a subset of metadata that should be provided in response to the request. Metadata, including in metadata objects or database artefacts, can be reviewed to determine whether it is relevant to the request, such as if the metadata is associated with the relevancy identifier. Different requests from the same client can specify different relevancy identifiers, as, for example, a first set of metadata may be relevant to one client process and another set may be relevant to another client process. While some metadata can be specific to a particular client, at least some of the metadata can be accessed by multiple clients, and at least in some cases different clients can specify the same relevancy identifier.