Dataset preparation
Dataset versioning: keep a release history
A filename ending in final does not identify a dataset reliably. Give each proposed snapshot a clear identity and explain what changed before discussing a possible licence.
Last checked
Keep the collection period, export date and release identity separate. A new download is not necessarily new data.
Identify the exact collection being discussed
Begin with a simple question: could a colleague identify the same collection next month? If the answer depends on opening whichever spreadsheet happens to be in a shared folder, the description needs work. A potential assessment should refer to a defined snapshot, not a moving target.
W3C's dataset publication guidance recommends a version indicator and a version history. These help a user distinguish revisions and understand changes. That is a documentation principle, not a requirement to publish a private archive on the web.
Our practical recommendation is to choose a release identifier inside your existing authorised system. Record the responsible team, collection boundary and related documentation. Do not create an external copy simply to obtain a convenient file to name.
Separate observations, exports and releases
An observation date describes when something happened. An export date describes when records were extracted. A release date describes when a defined package was issued or approved internally. These dates can differ substantially, and each answers a different question.
For an invented example, a fictional equipment inspection archive might be exported today while containing observations from earlier years. Calling the export current would not establish that the equipment was inspected recently. Write the covered period explicitly, and record whether late entries can still alter it.
If your system overwrites records, say that only the latest state is available unless a reliable history exists. Do not infer historical snapshots from a last-modified column. Ask the technical owner what can actually be reproduced before describing the archive as versioned.
Keep a change note a reader can use
For each revision, distinguish new observations from corrected values, removed records, changed field definitions and new processing. A higher row count alone cannot explain the change. It may include duplicates, newly included categories or a different selection rule.
A useful internal change note can record:
- The previous and new release identifiers.
- The reason for the revision and the person responsible by role.
- Which files, fields or collection periods changed.
- Whether identifiers still connect the same underlying items.
- Known effects on comparisons with earlier versions.
Keep the note descriptive. A correction is not automatically an improvement for every possible task, and removing difficult examples can change the population represented. The quality-check guide helps separate these questions from a single quality label.
Version the explanation with the records
Connect the snapshot to the data dictionary and any selection or processing notes that explain it. If a category changes meaning, the earlier definition should remain understandable. A new dictionary attached to old records can create ambiguity even when the files themselves have not changed.
Ask an authorised colleague to check one internal example against its stated version. Can they explain the fields, the collection boundary and any correction? Keep this check inside the existing system. Use invented examples in an external outline instead of including real records or screenshots.
The provenance guide addresses where material came from. Version history answers the narrower question of which state of that material is being described. Both can be needed; neither should be used as a substitute for a rights assessment.
Describe the history without handing it over
For an initial Fairlode enquiry, state whether you hold a single snapshot, reproducible releases or only a changing operational system. Describe the broad update pattern and a known limitation. Do not promise ongoing delivery or historical reconstruction until the relevant team has assessed what is feasible.
Keep retention, access and licensing decisions separate from version naming. This guide does not recommend keeping information longer, restoring deleted material or transferring a collection. Those decisions need the appropriate internal and professional review.
Fairlode starts with descriptions only. You can explain that versions exist without uploading them. A well-organised release history may make the collection easier to assess, but it is not evidence of buyer demand, a purchase commitment or a particular financial value.
General information, not legal advice, a valuation or a buyer offer. Illustrative examples are not customer case studies.
Sources and further reading
Sources checked 16 November 2026. Historical research is background, not evidence of current buyer demand.