1. Latest Release Home
  2. Guides
  3. Concepts
    1. Aggregate filter
    2. AI App
    3. AI Containers
    4. Alias
    5. Apache Avro™
    6. Apache Kafka™
    7. Applied filter
    8. Base table
    9. Bookmark
    10. Business schema
    11. Business schema view
    12. Business schema view column
    13. Business schema view formula column
    14. Column
    15. Connector
    16. Dashboard filter
    17. Dashboard folder
    18. Dashboard runtime filter
    19. Data agent
    20. Data alert
    21. Data destination
    22. Data purge
    23. Data retention
    24. Date system variable
    25. Derived variable
    26. Direct query
    27. Distinct filter
    28. Dynamic field
    29. Expression
    30. External data source
    31. External session variable
    32. External table
    33. Filter expression
    34. Filter expression session variable
    35. Filter option
    36. Formula column
    37. Formula expression
    38. Full load
    39. Global variable
    40. Incorta Analyzer Table
    41. Incorta Analyzer Table column
    42. Incorta Analyzer Table formula column
    43. Incorta Analyzer View
    44. Incorta Analyzer View formula column
    45. Incorta RAG
    46. Incorta Spark SQL View
    47. Incorta SQL Table
    48. Incremental Load
    49. Individual filter
    50. Insight filter
    51. Internal query expression
    52. Internal session variable
    53. Join
    54. Join condition
    55. Join condition column
    56. Join filter
    57. Join filter column
    58. Level-based measure
    59. Load filter
    60. Local data file
    61. Local data folder
    62. Log-based incremental load
    63. Materialized View
    64. Materialized View column
    65. Materialized View formula column
    66. Measure filter
    67. Metadata Precedence
    68. Miscellaneous system variable
    69. Multi-source table
    70. On-demand loader
    71. Physical schema
    72. Physical schema table
    73. Physical schema table column
    74. Physical schema table formula column
    75. Physical schema table runtime security filter
    76. PostgreSQL (Incorta SQL) View
    77. Presentation variable
    78. Prompt
    79. Query system variable
    80. Remote table
    81. Runtime business view
    82. Runtime business view formula column
    83. Runtime security filter
    84. Schema evolution
    85. Service Status Observability
    86. Session variable
    87. Shared Storage
    88. Snowflake result set
    89. Snowflake view
    90. Upgrade Readiness
    91. Variable
    92. Visualization
  4. Tools
  5. References
  6. Integrations
  7. Data applications
  8. Data Governance
  9. Release Notes
  10. Incorta Premium
  11. Release Support Policy
  12. Release Model

Concepts → Metadata Precedence

Incorta Nexus follows a defined order of precedence when multiple sources provide information about a column.

Order of precedence

Nexus processes column metadata and evaluates available metadata sources according to the following order of precedence:

  1. Business View column description: User-provided description.
  2. Metadata Tune: Automatically generated metadata.
  3. AI Container instructions: Instructions provided for an AI Container, if applicable.

Metadata Tune also considers the existing Business View column description when generating metadata. If the description provides sufficient context, Metadata Tune uses it instead of generating new metadata.

For more information, refer to Incorta Nexus Metadata Tune.

Example

Consider a Customer Health Score column that rates customer health from 0 to 100:

  • Business View column: 0 = Low customer satisfaction; 100 = High customer satisfaction
  • Metadata Tune: Customer Health Score measures customer satisfaction on a scale from 0 to 100 and can be used to identify accounts with lower or higher levels of customer satisfaction.
  • AI Container instruction: Percentile rank of customer satisfaction

If a user asks: “Show me the highest-performing customer accounts this year.”

Nexus uses the Business View column description to interpret the Customer Health Score because it takes precedence over the Metadata Tune output and AI Container instructions. Therefore, Nexus interprets higher Customer Health Score values as indicating higher customer satisfaction and returns the accounts with the highest scores.

If you modify a Business View column description after Metadata Tune has generated metadata, the updated Business View description takes precedence. The previously tuned metadata is invalidated and is no longer considered.

Important
  • If you modify a Business View metadata after Metadata Tune has generated its metadata, the previously generated Metadata Tune value is invalidated. The system uses the updated Business View column description instead.
  • If you edit a Metadata Tune value, the edited value is automatically locked and is preserved in subsequent automatic enrichment cycles.
  • To permanently override tuned metadata, update the Business View column description directly.