QuQi
ANALÍTICA E INFORMES

Dataset fitness check before analysis

Use when a dataset has arrived and you need to know what it can support before analysing it.

dataset-fitness-check.md
Descargar .md
You are checking whether a dataset can support an analysis before anyone runs it. You are not doing the analysis.

The analysis planned: {{PLANNED_ANALYSIS}}
Dataset description, including row count, date range and columns: {{DATASET_DESCRIPTION}}
A sample of rows: {{SAMPLE_ROWS}}
How the data was collected: {{COLLECTION_METHOD}}

Output:
1. A verdict line: fit for {{PLANNED_ANALYSIS}}, fit with caveats, or not fit. One of those three, first, before any detail.
2. A check table: Check | Result | Evidence from {{SAMPLE_ROWS}} or {{DATASET_DESCRIPTION}} | Effect on the analysis. Cover grain, duplicate rows, missing values by column, date coverage and gaps, placeholder values such as zero or unknown, outliers, any change in collection part way through the period, and survivorship.
3. Columns that cannot be used at all, and why.
4. The minimum cleaning steps, in order, each with what it removes or changes and roughly how many rows that affects.
5. Questions about {{COLLECTION_METHOD}} that must be answered before the result can be trusted.

Rules:
- Do not clean anything silently. Every exclusion is a listed step someone else could repeat.
- If the date range in {{DATASET_DESCRIPTION}} is shorter than the comparison the analysis needs, say that first and say what is missing.
- Where the sample is too small to judge a check, mark it unverified rather than passing it.

Rellena antes de ejecutar

Sustituye cada hueco por tus propios datos. Cuanto más concreto seas, menos se inventa el modelo.

  • {{PLANNED_ANALYSIS}}
  • {{DATASET_DESCRIPTION}}
  • {{SAMPLE_ROWS}}
  • {{COLLECTION_METHOD}}

Cómo sacar mejor resultado

  1. Send a sample of at least a few hundred rows spread across the period, not the first hundred.
  2. Ask who generated the extract and when; regenerated exports rarely match the first one.
  3. Keep the cleaning steps as code, since the analysis will be re-run and the steps will be forgotten.