Name files and control changes
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 folder containing final, final2 and reallyfinal makes it difficult to know which record to trust. Clear naming and version decisions solve different parts of that problem. You will prepare a compact folder plan and change log for the equipment register, keeping the original fixture distinct from edited working copies and approved outputs.
A filename helps you find a file; version history explains how it changed.
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
Create three conceptual folders: source, working and released. Keep the original sample fixture in source and make edits in a working copy, so the initial data remains available for comparison.
- 2
Choose a filename pattern using project, date and revision: repair-checkouts_2026-10-10_v01.csv. Use a sortable year-month-day date and a fixed-width revision number. This is a local convention, not a universal rule.
- 3
Create a change log with version, date, editor role, change, and reason. Use a role instead of a personal name; for example, steward means the person responsible for maintaining the records.
- 4
Simulate a correction: v02 changes C02 from out to returned after a supplied return confirmation. Keep the reason with the change rather than only replacing the file.
- 5
Simulate two contributors editing v02 differently. Compare both changes before creating v03; do not assume the newest timestamp proves correctness. Save a release pointer naming the approved version and its location.
See how it works.
Fictional version log: v01 is the original two-row fixture. In v02, the steward changes C02 status to returned because a sample session return slip confirms it. A second draft changes quantity from one to two without evidence. The steward accepts the documented status change, flags the quantity proposal and releases v03 with quantity still one. The release note points to repair-checkouts_2026-10-10_v03.csv. This decision uses evidence, not whichever file was saved last. In a real shared editor, version history may provide the revisions, but the reason and approved release still need a clear record.
Did you cover these?
- Source and working copies are distinguished.
- Versions have meaningful change reasons.
- Conflicting edits are reviewed rather than silently overwritten.
What to finish
A folder plan, filename convention, change log and approved-version pointer.
Watch for this
Assuming the newest file or a filename containing final is authoritative.
How can I tell I understand it?
Reconstruct which change was accepted and why.
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.
Report a problem with this lesson
Tell us what went wrong. Please leave out personal information and private project contents.