Glossary
The glossary exists to solve a specific problem: people don't talk like database schemas.
For example, your sales team may provide quotes to customers, which are registered in your system as contracts with a certain status. Your sales team doesn’t know the intricacies of the data schema, so when they ask Wobby “How many quotes did we make this year?”, defining “quotes” in the glossary will save Wobby guesswork, and deliver reliable results.
The glossary maps natural business language to technical semantic layer components.
Last updated
Was this helpful?