The glossary, like the other DataGalaxy modules, is built around objects.
Which object characteristics should you respect?
Here are some important characteristics of objects to take into account when structuring the glossary:
- Each object has its own characteristics and its own ability to be related to others.
- Each object must have a unique definition.
- An object can only have one direct parent. This gives it its context.
- Objects can be organized in a hierarchy thanks to the path. This is why the primary hierarchy of objects (the
PATH) is unique.
Objects can only have one path.
Why can a definition differ from one team to another?
To illustrate, take the notion of customer. Depending on whether you are in Marketing or Sales, the definition differs:
- The customer from a marketing perspective can be a prospect.
- The customer from a sales perspective is a customer who has already been invoiced.
What does a typical glossary organization look like?
As a reminder, here is a typical example of how the glossary is organized:
