# Register Metadata While the **ORM models** define how data is stored in the database and the **Pydantic schemas** define validation and API data structures, the OpenG2P Registry platform also requires registers to be defined in **platform metadata tables**. These metadata definitions allow the platform to dynamically: * Discover available registers * Configure UI rendering * Route API requests * Load appropriate service classes and domain models The metadata is also important for the **Registry UI layer**, which uses these definitions to dynamically render register interfaces and workflows. The primary metadata table used for this purpose is **`g2p_register_definition`**. Register metadata can be created either: * Directly through database configuration scripts, or * Through the **Configuration section of the Registry Staff UI** --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.openg2p.org/products/registry/registry/developer-zone/building-a-registry/concepts/registry-and-register-metadata.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.