Collecting, Organising and Searching Data
Collecting, Organising and Searching Data
Lesson duration is: 50 minItems in this lesson
Collecting, Organising and Searching Data
This item has no instructions
Learning goal
I can collect, organise and search data in a simple database to answer questions.
This item has no instructions
What words come to mind when you hear data?
Use this to activate prior knowledge. Expect ideas such as information, numbers, names, lists, facts, computers and questions. Invite pupils to explain one or two contributions aloud.
Lesson introduction
This KS2 computing lesson explores Collecting, Organising and Searching Data. Pupils design fields, enter records and use sorting and filtering to answer questions from a simple database. It is suitable for classroom teaching, independent practice or a clear recap of the topic.
This slide must remain verbatim as requested. Read it aloud briefly, then move into the lesson sequence.
What is data?
Data is information we can collect and use.
It might be words, numbers, dates or yes/no answers.
In computing, data is often stored so we can find things out quickly.
Link to everyday examples such as class birthdays, favourite fruit or reading scores so pupils see data as organised information, not just numbers.
Why do we collect data?
We collect data to answer questions and spot useful information. For example, a class might collect data about favourite fruits to find the most popular choice, or library data to see which books are borrowed most often.
Keep the focus on computing: data is collected for a purpose, not just written down. Emphasise that useful questions come before collecting data.
Records and fields
A record is one full item of data.
A field is one part of that record.
Example: one pupil is a record; name, class and lunch choice are fields.
This distinction is a common sticking point. Point to a single row as a record and each heading as a field.
Planning the right fields
Before entering data, we choose fields that help answer our question.
For a class pets database, useful fields might be name of pet, type of pet, age and colour. A field like favourite game would not help if the question is about pets.
Stress that good field choice depends on purpose. Avoid adding extra fields that do not help answer the question.
In a class pets database, which field would be least useful?
age
colour
type of pet
favourite game
Checks whether pupils can choose fields based on purpose, not just add random information.
Records and fields
A record is one full item of data. A field is one part of that record. We choose the right fields to help answer a question clearly.
All three words are key vocabulary from this first teaching block.
Why must fields match your question?
Look for answers that mention matching fields to the purpose or question, for example: 'It helps answer the question' or 'You get useful data'.
Entering records carefully
Each record should go in the correct place.
Spellings and formats should stay consistent.
Clear entries make sorting and filtering work better.
You can model why inconsistent entries cause problems, such as mixing 'yes', 'Yes' and 'Y' or writing months in different ways.
Organising data
Organising data means putting it in a clear structure so it is easy to read and use. In a simple database, records are usually arranged in rows and fields are shown as headings. Good organisation helps us search, compare and answer questions.
This item has no instructions
Rows and headings
Headings tell us what each field means.
Each row usually holds one record.
A tidy table makes information easier to check.
Use the exact terms consistently: field, record, heading, row.
Keeping data tidy
Use the same style each time.
Keep numbers as numbers when needed.
Avoid leaving important fields blank.
Check for mistakes before searching.
Examples suitable for KS2: write year groups the same way, choose one date format, and decide whether lunch choices use full words or codes.
Useful and less useful organisation
Missing headings
Mixed-up entries
Different spellings
Hard to search accurately
Clear field names
One record per row
Same format each time
Easy to sort and filter
Well organised
Less organised
This contrast helps pupils see why organisation matters for computing tasks, not just neatness.
What usually goes in one row of a simple database?
one record
one heading
one field
one search
Targets the row/record distinction from the organisation slides.
Keeping data organised
In a tidy table, headings show what each field means. Each row usually holds one record. Using the same format each time makes data easier to check and search.
Echoes the exact phrasing from slides 8 to 11 so pupils anchor key organisation terms.
Which part of organising data needs the most care?
clear headings
one row each
same format
checking mistakes
This item has no instructions
Searching data
Searching data means looking through a database to find records that match what we need. We can search by reading, but digital tools make it much faster when there is lots of data.
Set up the need for search tools by contrasting a tiny class list with a much larger set of records.
Sorting data
Sorting puts data in order.
We can sort alphabetically, numerically or by date.
Sorting helps us find the first, last, highest or lowest values.
Give concrete examples: sort names A–Z, sort ages smallest to largest, sort scores highest to lowest.
Filtering data
Filtering shows only records that match a rule.
Example: show only pupils in Year 4.
This helps us answer specific questions quickly.
Filtering is often confused with sorting. Clarify that sorting changes order, while filtering hides records that do not match.
Sorting and filtering together
A database becomes powerful when we use both tools together. We might filter to show only fiction books, then sort by title to find one quickly. These tools help us answer questions from the same set of data without rewriting it.
Keep examples in familiar KS2 contexts such as books, lunches, pets or sports clubs.
Answering questions with data
Good questions can be answered from the fields collected.
We use sorting and filtering to find evidence.
Our answers should match what the data shows.
Emphasise that data supports an answer; pupils should not guess if the database can show it.
Example: class library database
Fields: title, type, author, borrowed.
Filter type = fiction.
Sort title A–Z.
Now it is easier to answer: 'Which fiction books are listed?'
This is the main worked example. You can adapt it to your own class reading scheme or library system.
Choosing the best search method
Use sorting when order matters.
Use filtering when only some records matter.
Use both when you need a smaller group in a clear order.
A simple way to phrase it for pupils: sort = put in order, filter = show only what matches.
Which tool shows only Year 4 pupils?
sorting
filtering
heading
recording
Tests the common confusion between sorting and filtering.
Searching with data tools
We use sorting when order matters, such as names A–Z. We use filtering when only some records match a rule. To answer questions, our answers should match what the data shows.
This checks the final application block, including choosing the best search method.
When would you use sorting and filtering together?
Look for an applied answer such as filtering first to show a smaller group, then sorting to put that group in order. Accept brief examples linked to books, lunches, pets or pupils.
What is one thing you learned today?
Reflection only. Encourage pupils to name one clear learning point, such as records and fields, tidy organisation, sorting, filtering or answering questions with data.
What helped you understand this best?
Reflection only. Useful for spotting which teaching approach supported understanding best, such as the pets example, the library example or the vocabulary recap.
How confident do you feel about sorting and filtering data now?
This item has no instructions
Glossary
data - information that is collected and used
database - a computer tool for storing and organising data
field - one piece of information in a record
record - one complete set of information in a database
sort - to put data into an order
filter - to show only the records that match a rule
heading - the label at the top of a field
This item has no instructions
