Where Elementary Students Are Starting From
Young students are already data collectors. They count how many students chose chocolate milk versus white milk. They sort leaves by shape. They tally votes for the class pet. What they are not yet doing — and what K-5 CS instruction can introduce — is thinking deliberately about why they are collecting, what the collection is for, and what it means to organize information so that someone else can use it.
The formal vocabulary of this week — relations, tuples, attributes, SQL, data mining — is not the destination at K-5. The destination is a durable intuition: data is collected for a purpose, organization makes data useful, and the way you organize something shapes what questions you can answer with it.
Data vs. Information at the Elementary Level
The distinction between data and information — that data becomes information only when it answers a question — is one of the most teachable ideas in Week 5, and it fits naturally into elementary classroom life.
A Classroom Entry Point
Start with a pile of sticky notes, each showing one student's favorite color. Ask: is this data or information? (It's data — raw facts that haven't answered anything yet.) Then ask a question: "Which color did the most students choose?" Now sorting and counting the sticky notes turns the data into information. The question came first; the organization served the question.
This is the core idea of the data investigation cycle from Topic 5a, scaled to something a first grader can do physically. You do not need to name the five stages — you just need students to experience that collecting without a question produces a pile, not an answer.
What to Avoid
Avoid framing data collection as an end in itself. "Let's collect data!" without a purpose models exactly the misconception the week's readings push against. Even at K-5, the question should come before the collection.
Tables as Organizers at the Elementary Level
The relational model — organizing data into rows and columns where every row represents one thing and every column represents one attribute — has a natural elementary precursor: the class data table.
Unplugged Approaches That Work
- The class roster table: Build a simple paper table together as a class. Columns might be Name, Favorite Subject, and Number of Siblings. Each row is one student. Ask: what questions can we answer from this table? What questions can't we answer? This introduces attributes, tuples, and the idea that table design determines what's possible — without any of that vocabulary.
- The card sort: Give students index cards, each representing one book in the classroom library (title, author, number of pages, fiction or nonfiction). Ask students to sort the cards to answer a question: "Which books are short enough to finish in one reading period?" The physical sort is a concrete version of a database filter.
- What happens when we add a column? After building a simple table, add a new attribute — say, "Has a pet?" Ask: does this change any of the rows we already have? Does it change what questions we can answer? This builds intuition about schema design without the formal term.
The Redundancy Problem, Gently
You do not need to teach redundancy formally at K-5, but the intuition is accessible. If every row in your class table includes the teacher's name and room number, ask: what happens when your class moves rooms? How many places do you have to update? Students quickly see that repeating the same information in every row creates extra work — and potential for mistakes. That's all redundancy is at this level.
Structured and Unstructured Data at the Elementary Level
Elementary students can grasp the distinction between information that fits in a table and information that does not, even if they never use the terms "structured" and "unstructured."
Ask students: could we put a drawing in our table? Could we put a recording of someone reading aloud? They quickly recognize that some kinds of information have a natural box-shape and some do not. The follow-up question — "so where would a computer store those?" — connects to the earlier weeks on how files work, and opens the door to the idea that different kinds of data need different kinds of storage.
Connections to the Broader K-5 CS Curriculum
- Data and analysis standards: CSTA K-5 standards include collecting data, organizing it, and using it to answer questions. Week 5 gives you the CS vocabulary to name what students are doing when they make a bar graph or tally a survey — and to take it one conceptual step further.
- Math connections: Tables, sorting, and categorizing are core mathematical practices in K-5. Connecting the CS concept of a database relation to the math concept of a table helps students see both subjects more clearly.
- Information literacy: The question "where did this data come from and what was it collected for?" is as important in elementary library instruction as it is in CS. Week 5 gives teachers language to connect those conversations.