The first step is to clearly define what your application will do and who will use it. Understanding the purpose early on ensures that you focus on the necessary features and elements.
Example:
For this tutorial, we will create an app for recipe management. Its primary functions will be:
- Storing details about recipes, including the creator, steps, and ingredients used.
- Suggesting similar recipes.
- Keeping track of whether ingredients are in stock or need to be replenished.
Why a Recipe App?
We are using a recipe app simply because it is something easy to relate to. It will serve as a simplified version of a relational database, where tables (recipes and ingredients) are linked through relations, and additional context is provided via metadata. By starting with a relatable real-life example, you will learn how to define object types, set up relations, and manage information, which are core tasks in any data governance environment.
Translating the Recipe App to Data Governance
In a data governance environment, we deal with structured data organized in ways that allow us to easily manage, track, and query information. The recipe app, while simple, can be understood in similar terms, as we can draw a one-to-one comparison between its components and a database.
- Cuisine Type / Ingredients List Category: These act as directories that help categorize recipes and ingredients, acting as organizational elements.
- Recipe Table: Holds core information about a recipe, with columns for details like steps, ingredients (linked to the ingredient table), and metadata (owner, difficulty, recommendations, etc.).
- Ingredient Tables: A separate table containing detailed information on ingredients such as stock status, description, and seasonal labels.
In a data governance system, these pieces of information would be managed and structured in a way that allows easy access, reporting, and querying. Just as in the recipe app, data governance involves organizing this data, ensuring consistency, and setting up relations so the data can be used efficiently.
Next Step: Map Your Data Structure
Now that we have established the purpose of your application, the next step is to decide how the data will be structured. This means defining the object types that will form the foundation of your app, as well as how they relate to one another.