Sitemap

Notes On Data — Context

2 min readAug 28, 2025

A series of remarks for a data architect to pay attention to when designing data management systems.

Let’s imagine a dialog below:

— John, what’s the value ?
— 25.20
— 25.20 what ?
— what value ?

This dialogue is remarkable as it demonstrates the importance of context for any value we use. It does not matter where and how the 25.20 will be stored in a database, file or an object store. And storing it does not move us closer to understanding on what it actually is. We simply do not know why we need this number and how to use it. To solve the context issue we can create a database table and name a column as “exchange rate”. This will bring some context and by looking at just a column name we can perform checks on the data we store in the column.

Let’s say we created a table with 3 columns:

“from currency”, “to currency”, “exchange rate”

Get Sergey Meshkov’s stories in your inbox

Join Medium for free to get updates from this writer.

Just naming columns properly bring a lot of context into the picture, and we can start working with the data in this table.

On the other hand, if we name the “exchange rate” column as “room area”:

“from currency”, “to currency”, “room area”

The context is completely ruined. It is an extreme example but anyone looking at this table will not be able to figure out why currencies have room area. Sometimes “small” correction to naming can destroy context in a big project and cause a lot of misunderstanding.

This brings an important requirements to the context definition.

Context has to be consistent and clearly defined.

There re multiple ways to define context to data, i.e. schema, table structure, etc. Context (or metadata) has to be present and be available along the data.

An example of clearly defined context:
25.20 is an exchange rate of pound sterling to mexican peso taken on the 28th of August 2025 at 18:40 BST.
Source: https://share.google/2g0CCnuImOUoycHRI