Define the record and its fields
See this course’s project requirements
Assemble the fictional equipment register and its operating README from all six lessons.
Keep your working files in your own notebook or software. Save a private description, checklist, and work link in My Proof.
What to include
- Define the record schema, sample rows and quality checks.
- Document filenames, version history and the approved release.
- Justify retained fields and create a purpose-specific export.
- Specify role-based access with review and removal triggers.
- Provide a retention review schedule, hold checks and tested handoff.
Review and revise
Use these criteria to check your work and choose what to improve.
- Meaning: fields and row definitions support consistent interpretation.
- Traceability: accepted changes and the current release are identifiable.
- Proportionality: data and access match stated purposes.
- Continuity: lifecycle decisions and handoff questions are answerable.
Want more background?
The idea in everyday life
A shared file becomes unreliable when different people interpret the same column differently. Before sorting or sharing records, define what is being recorded. Your fictional repair club tracks equipment checkouts by item and session, without identifying borrowers. This course concerns record stewardship: keeping information understandable, limited, versioned and available to the appropriate role.
A schema lists a dataset’s fields (columns) and their rules. It explains what one record means and which values each field can contain.
One step at a time.
Use the sample or information you have permission to use. Keep your work as you go. You can pause between steps.
- 1
Write the record purpose: track whether club equipment returned from each session. Define one row as one item checkout during one session, so the same item can appear in different rows over time.
- 2
Create five fields: checkout_id, item_id, session_code, quantity and status. Use a unique checkout ID, a positive whole-number quantity, and status values out or returned.
- 3
Prepare the sample rows C01,T01,S1,2,returned and C02,T02,S1,1,out. Explain that the identifiers are invented labels for records, equipment and sessions rather than people.
- 4
Write a dictionary giving each field’s meaning, type, allowed values and missing-value rule. Flag a missing status in a separate issue log for review; do not enter unknown as a status or silently interpret the absence as returned.
- 5
Check a planted row C03,T03,S2,-1,returned. Flag its negative quantity and state the verification needed before correction. Save the schema and checks as the first part of your final stewardship packet.
See how it works.
Fictional schema: checkout_id is unique text; item_id and session_code are text labels; quantity is a positive integer count; status is one of out or returned. C01 records two units of T01 at S1, returned. C02 records one unit of T02 at S1, still out. The dictionary says status describes the recorded checkout state, not who possesses an item. A test row with quantity=-1 is invalid because a checkout count cannot be negative under this model. Detecting it does not tell us the correct quantity, so the steward flags it for source verification instead of inventing a replacement.
Did you cover these?
- Row meaning is stated.
- Each field has type and allowed-value rules.
- Negative quantity is flagged without invented correction.
What to finish
A five-field schema, two valid sample rows and one flagged invalid row.
Watch for this
Mixing several record types in one table or assuming unexplained abbreviations are obvious.
How can I tell I understand it?
Another reader can create a valid row using only the dictionary.
Quick knowledge check
Answer all 3 questions. Get at least 2 right and the lesson completes automatically.
You’ll get an explanation for each answer. Signed in? Your results save to your account.
Pass the check. We’ll save the progress.
Answer all 3 questions above and get at least 2 right. You can review the explanations and try again.
Go to the knowledge checkTools, templates, and lesson sources
Tools and templates
Tools open in a new tab so you can keep your place here.
Sources and further reading
Explore the references behind this lesson.
Source & access notes · checked 2026-09-10
Read file naming, sorting, folder hierarchy and README guidance. The public page states CC BY-NC for its own content; no source text or templates are copied here.
Access: Free public reading; no account or certificate is required for this Life Starter course.
Reuse: Linked for reference. Examples, activities and assessments here are original; free access alone does not grant permission to reuse source text or branding.
Source & access notes · checked 2026-09-10
Read purpose-based adequacy, relevance and minimization guidance. UK-specific legal context is identified; the course teaches a practical design principle, not jurisdiction-wide legal advice.
Access: Free public reading; no account or certificate is required for this Life Starter course.
Reuse: Linked for reference. Examples, activities and assessments here are original; free access alone does not grant permission to reuse source text or branding.
Report a problem with this lesson
Tell us what went wrong. Please leave out personal information and private project contents.