Recipes & best practices

Step-by-step recipes: structuring a glossary, mapping data, comparing dictionary vs glossary, and more.

10 articles

Model SQL Queries

Model SQL selection and management queries in DataGalaxy while balancing lineage detail and query organization.

[Recipe] Model your glossary

Model your glossary by proximity or by urbanization, and weigh the constraints before you choose.

[Recipe] Build your application catalog

Map the application layer of your information system: describe applications with the Uses module and group them into clusters.

[Recipe] Refining your glossary

A two-step approach to refine a glossary: sequence the classification (flat view, repositories, specific concepts), then manage object life cycle and editing rights.

[Recipe] Compare dictionary & glossary

A short recipe comparing the glossary (business terms and indicators) and the dictionary (tables, files, columns, fields) and how they link in DataGalaxy.

[Recipe] Readability of glossary objects

Tips to keep the glossary readable: limit hierarchy levels, keep 3 to 20 direct children per group, and set naming rules.

[Recipe] Rank and group your data

Organize glossary data with universes and domains to build a clear matrix view.

[Recipe] Organise your glossary

Key object characteristics to respect when structuring a glossary: unique definitions, a single parent and a single path.

[Recipe] Lineage granularity

Choose a lineage granularity that fits your use case, organization maturity, and maintenance capacity.

[Recipe] Document your message broker

A recipe to document a message broker such as Kafka in the dictionary: topics as directories, messages as files, and tracing producers and consumers.