Data vs Information

Imagine you pick up a scrap of paper on the floor and it just says:

Is that a good mark on a test? A room that's dangerously hot? A bus number? Someone's age? The number 37 on its own tells you almost nothing — it's just a raw value. This is the whole idea of this page: a bare value is data, and it only becomes useful information once you know what it is and what it means.

Data — raw facts, values or symbols with no meaning on their own. Examples: 37, "blue", 1998, "NW1".
Information — data that has been given meaning and context, so a person can actually use it. Examples: "the temperature is 37°C", "her favourite colour is blue", "he was born in 1998".

Computers are brilliant at storing and moving data — billions of values a second. But the data is only worth something to a human once it has been turned into information. That step — adding meaning — is what databases, apps and spreadsheets are really for.

Context is the missing ingredient

Think of it like a recipe. Data is the raw ingredient — a spoonful of something white. Is it sugar or salt? You can't tell until someone labels the jar. That label is the context, and it's exactly what turns data into information:

\text{data} + \text{context} = \text{information}

The diagram below takes three raw values and adds a label (what the value measures) and a unit or meaning. Step through it and watch the same lifeless numbers become sentences you can act on.

The same data can mean different things

Here's the surprising part. Because meaning comes from context, one identical piece of data can become completely different information depending on what you decide it represents. Take the value 1998:

with the label year of birth → "this person was born in 1998";
with the label price in pence → "this item costs £19.98";
with the label steps walked → "you walked 1998 steps today";
with the label house number → "they live at number 1998".

The bits stored on the disk are the very same — the number nineteen-ninety-eight. What changes is the story we wrap around it. This is why a well-built database always stores the context too: the column name, the units, the data type. Strip those away and you're left with a pile of meaningless values.

Both — it depends where you stand! The text "blue" sitting in a file is just data: a five-letter symbol. The moment you say "the customer's chosen colour is blue", you've added context and it's become information. Nothing about the stored value changed; you simply told it what job it's doing. Data and information aren't two different things so much as two different roles the same value can play.

A tiny example in code

A program stores plain data, but a helpful program presents it as information — by pairing each value with a label and a unit. Press Run and see the difference: the same numbers, first as bare data, then dressed up as information a person can read.

// Raw DATA: values with no meaning attached. const values: number[] = [37, 1998, 12]; console.log("Just the data:"); console.log(values.join(", ")); // Add CONTEXT (a label + a unit) to turn each value into INFORMATION. console.log(""); console.log("Now as information:"); console.log("Temperature: " + values[0] + " degrees C"); console.log("Born in the year " + values[1]); console.log("Shoe size: " + values[2]);

Notice the numbers 37, 1998 and 12 never changed. All the program added was meaning.

A lone number is only data — never assume you know what it means. Before you can call 37 "information", you must know what it measures and its units or context: is it 37°C, 37%, 37 mph, or £37? Getting the context wrong is a real and dangerous mistake — in 1999 NASA lost the Mars Climate Orbiter because one team's numbers were in pounds-force and another's expected newtons. Same data, missing context — and a £100-million spacecraft burned up. Context isn't optional decoration; it's the part that makes data useful and safe.

Where this goes next

Everything you meet in databases builds on this one idea. A field (a column) is really just a label that gives a value its context; a record (a row) collects the data about one thing so it reads as information. Even a graph or a report is just data with enough context bolted on that a human can spot the meaning at a glance. Keep asking of any value you see: "What does this measure, and in what units?" — that question is the difference between data and information.