Modeling the glossary can be complex at first. Indeed, how can you know exactly which grouping a business term, an indicator or a concept will be classified under?
To keep the mapping process moving forward, we suggest two main steps to model your glossary.
How to sequence the classification operations
Start with a flat view, where you will:
- Identify all the elementary units: business terms, indicators, dimensions.
- Build "large mesh" repositories: universes with generically named concepts to classify indicators.
- Create specific concepts to classify the elementary units according to your context, within the repositories.
How to manage the life cycle of your object
Modeling is one thing; knowing that you are viewing a correctly filled-in object is another. To do this, use the object's life cycle, that is its status. Several statuses are available.
Life cycles are also useful because they let you limit editing rights: any steward with write rights can modify an object with the proposed status, but for validated objects only the owner can make modifications. To learn more, read Object life cycle.
What the refinement process looks like in practice
- Identify the main objects and, if needed, create the first groupings (with the concept object) to limit the "infinite object list" effect. The objects stay in the proposed status to mark the start of the mapping work.
- Build the first repositories. To do this, use the universe object and attach different concepts to it.
- Distribute the objects better by creating more detailed concepts. For good readability practices, see [Recipe] Readability of glossary objects.
- Identify the objects whose definitions are authoritative. For this, you can use comments and MetaBot to run votes.
