startthat.work home

IS-09 Quantitising and qualitising (data transformation)

Converts one data type into the other, for example by counting coded themes, and produces a single-type dataset of frequencies or profiles.

Integrate across sourcesEvidence: UnconfirmedPrimary technique, runs in step 5.3Strongest statement: describe

What it does

Converts one data type into the other, for example by counting coded themes, so that the two can be compared directly. Artefact: a single-type dataset. Read the frequencies or profiles produced.

When to use it

Use when you need to compare coded text with numeric data directly, or to turn numeric patterns into profiles that can be read.

When it does not fit

Fits when coding is reliable. Misuse: reading theme counts from a non-random sample as prevalence.

Result format

The result is a single-type dataset in which the coded themes have been converted into counts, with one row per case or group and one column per theme. It reports the frequencies or profiles produced and states whether the sample supports reading the counts as prevalence.

Requirements on the material

PropertyRequirement typeRequirement
Content typeAlways appliesrequires=text; requires=tabular
Unit of analysisAlways appliesrequires=document; requires=record
Number of sourcesAlways appliesrequires=two or more
Appraises source credibilityApplies in some casesno

Not restricted on: Structure, Variable types, Time structure, How the sample was chosen, Level of detail available, Whether sources can be joined, Amount of material, Known data problems, Producer interest, Source dependence, Origin, Document genre, Language, Personal information, Security classification, Licence.

Minimum materialnone
Additional sources needednone
Not for (rules)none
Not for (text)Coding is unreliable, or theme counts from a non-random sample are read as prevalence.

Choosing and ordering

Kind of techniquePrimary technique, runs in step 5.3
Phase taganalyse
Other phase tagsnone
Kind of findingpattern
Question answeredwhat; how much
Strongest statement it supportsdescribe
Needs as input
Makes as output
Must exist firstNone
Loop targetproceed with limit stated

Library checks by stakes

Each stakes level includes the checks of the level below it. Checks that need a person apply at high stakes only, so the process leaves them out at lower stakes (decision 38). Repeatability: deterministic.

StakesCheckPerson involvedCounts as a different method
exploratoryinput validationnoneno
decision-informinginput validationnoneno
decision-informingspot checkoptionalno
high-stakesinput validationnoneno
high-stakesspot checkoptionalno
high-stakesindependent reviewneededno
high-stakesprovenance lognoneno

Failure modes and limits

Model suitabilitymodel plus code
Typical model failureCounts themes in prose without code, and presents counts from a purposive sample as population shares.
Error sourcesinput data; coder or rater judgement; data transformation
Certainty limitsCertainty drops with unreliable coding and with samples that do not represent the population (indirectness and risk of bias).

Evidence and tag basis

Unconfirmed. The source names the approach under interpretation and reporting integration and does not describe it, so this description is the note author's. (Fetters, Curry and Creswell 2013, via core.ac.uk)

Tag basis: input profile inference; selection inference; sequencing inference; robustness inference. All tag values are inference unless a source is named.