← Back to course
1/6
Week 04 · Collecting and Recording

Monday

The collection week
// One row per member, one column per question
⏱ about 20 min

Monday: The Collection Week

The survey is finally live. A sign by the front desk of Starling Commons says: "Commons Count. Seven days. Every question can be skipped."

Comet bursts in waving a stack of printed sheets. "Answers are already coming in! Let's count them all right now."

Wren spreads the sheets on a workbench. Some answers are on one page and some are on another. "What do you notice?"

"They are everywhere," Comet admits. "I cannot tell who answered what."

Keeper Ines looks up from the desk. "The council will want one clear sheet at the end of the week."

Nova hovers over the bench and projects an empty grid. "Would you like a hint?" she asks. "Give every member one line and every question one place."

Comet turns to you. "You are our data analyst. How should the sheet look?"

This week's driving question

How do we record data so it stays useful and honest?

This week the crew runs Commons Count for one week. You will build the data sheet, choose how often to count and label every sheet.

One row, one column

Tables, diagrams, text and other visuals can share what data show. A table is where the crew starts.

The crew's rule is simple. Each member who answers gets one row. Each question gets one column.

The first column holds the member's ID, not a name. That was the privacy pass from last week.

Here are the first five rows. Q3 and Q6 hold written answers, exactly as members typed them.

IDQ1 How oftenQ2 WhenQ3 Add nextQ4 Visits last weekQ5 How answeredQ6 Anything else
M013 or more a weekeveningrepair table4screen(blank)
M021 or 2 a weekafternoonLonger evening hours2screen(blank)
M031 or 2 a weekeveninga quiet room to study2screen(blank)
M041 or 2 a weekweekendlonger evenings1screen(blank)
M053 or more a weekeveninga quiet room to study3screen(blank)

This is made-up data from the Commons Count story. By the end of the week, the sheet has 40 rows, M01 to M40.

READ THE DATA SHEET
  • Read the question.
  • Tap your answer.
How many rows will the finished data sheet have?
How many question columns does the sheet have?
Where do you look to find every answer M03 gave?
Where do you look to see how everyone answered Q2?

Check the total

A common list algorithm finds the sum of a list of numbers. A sum is a quick way to check a data sheet.

If every member answered Q1, the Q1 groups must add up to the number of rows.

On her first count, Comet tallied 9, 16 and 14 for the three Q1 choices. That adds up to 39, not 40.

She recounted the middle group and found 17. Now the total checks out.

Q1 answerMembers
less than once a week9
1 or 2 times a week17
3 or more times a week14
Total40
ADD IT UP
  • Read the question.
  • Tap your answer.
What is 9 plus 17 plus 14?
Comet's first count added up to 39. What did that tell her?
StatementTrue or false?
Each member who answers gets one row on the data sheet.?
Each question gets its own column.?
The first column holds each member's name.?
If the Q1 groups add up to 39 on a 40-row sheet, the count needs checking.?
WHY THIS EXERCISEA clear sheet and a total check keep the data honest from the very first day.
CHECK A COLUMN TOTAL
  • ?If they do not match, recount each group.
  • ?Compare the sum with the number of rows.
  • ?Add the group counts together.
  • ?Count the members in each answer group.
WHY THIS EXERCISEThis simple check catches missed or double-counted answers before anyone uses the data.
On paper, sketch the top of the data sheet: an ID column, six question columns and rows M01 to M05.

Strong start, data analyst. Tomorrow you will decide how often to count people coming through the Commons door.