Metadata
- Author: hex.tech
- Full Title:: How to Curate Your Hex Workspace So Business Partners Can Answer Their Questions
- Category:: 🗞️Articles
- Document Tags:: Hex, Metrics layer,
- URL:: https://hex.tech/blog/curate-workspace-for-explore/
- Read date:: 2025-03-23
Highlights
set up a new data connection to house just the right databases, schemas, and tables that are relevant to them. (View Highlight)
Schema filtering (in the Data browser) (View Highlight)
Magic - Include/Exclude toggles and Endorsements (in the Data browser) (View Highlight)
tips to reduce any potential string hallucinations: • Add enumerations - For low cardinality string columns that are often filtered on or used in case statements, try explicitly enumerating or describing options for these fields in the Data Browser (this can reduce hallucination rates down to near 0). This could be useful for a question like: “How many orders have shipped but not yet been delivered?” • Try explaining the pattern in natural language - For high cardinality string columns that have too many options to list but follow a consistent pattern (like a City / State combo), call out the pattern in natural language like “City State pairs, like ‘Memphis TN.’” This can help Magic better understand. • Add custom metadata - Try using natural language to tell Magic when a table should and shouldn’t be referenced. For example, you could write: “only use this table if the prompt explicitly requires raw stripe data, otherwise use
fct_orders.” (View Highlight)