Native Data Dictionary Management for Multitenant Metadata Governance
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current techniques for managing data dictionaries in complex environments are inefficient, leading to confusing, stale, and conflicting data due to inconsistent policies and the inability of metadata to be described in a standard manner for third-party developers, which complicates data governance and compliance with regulations like those for personally identifiable information (PII).
Innovation Solution
Implementing a native data dictionary management system within a platform that provides a central, accessible, and reliable reference for metadata, allowing for efficient management of both standard and custom fields, with features like field-level security, data ownership, and lifecycle management, tailored to meet individual organizational needs, and integrated with on-demand database services for multitenant environments.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a spreadsheet or similar tool is used to manage a data dictionary, then it provides a simple and accessible reference for metadata, but it becomes inefficient as data repositories grow in size and complexity
Solution Approach 1:
The system enables automated self-service through programmatic access to metadata via APIs. Third-party developers can query and manage metadata without manual spreadsheet intervention, allowing the system to serve itself and external applications efficiently while maintaining simplicity for users.
Solution Approach 2:
The patent replaces the mechanical spreadsheet-based manual management system with an automated computational system. This substitution introduces programmatic access, automated data governance policies, and machine-driven metadata management, dramatically improving efficiency while preserving accessibility through standardized interfaces.
2Ease of manufacture
If manual management techniques are used for data dictionaries, then implementation is simple, but inconsistent policies are applied resulting in confusing, stale, and conflicting data
Solution Approach 1:
The system implements universal automated data governance policies that apply consistently across all data repositories and metadata. A single centralized system enforces standardized policies for data creation, modification, and deprecation, eliminating inconsistencies while maintaining ease of use through automated enforcement rather than complex manual procedures.
Solution Approach 2:
The system incorporates automated feedback mechanisms that continuously monitor data dictionary status, detect inconsistencies, and trigger corrective actions. This feedback loop ensures policies are applied consistently by automatically identifying and resolving conflicting or stale metadata, preventing the propagation of errors while keeping the system simple to operate.
3Device complexity
If current techniques are used for managing data dictionaries, then no specialized system is required, but the inability of metadata to be described in a standard manner complicates data governance and compliance
Solution Approach 1:
The system segments metadata management into standardized, modular components with defined interfaces. By organizing metadata into structured elements with consistent schemas and hierarchical relationships, the system enables third-party developers to access and manipulate specific metadata components programmatically, achieving standardization without requiring a completely complex new architecture.
Data Source
AI summary
Techniques for maintaining a data dictionary within a computing platform that provides a multitenant environment in which multiple tenants utilizing the multitenant environment share a single instance of a database. The data dictionary is maintained with referential integrity utilizing custom database objects to provide metadata corresponding to the data dictionary. The data dictionary tracks attributes for the custom database objects utilizing natively supported field attributes and the custom database objects maintain tenant-specific information. The custom database objects are automatically updated corresponding to the data dictionary. A notification to one or more users is generated for custom database objects that correspond to the data dictionary that cannot be updated automatically, if any.