Step 3: evaluate metadata linkage
The pairing between variable and metadata is not always one to one. For each variable we need to specify where each piece of metadata comes from.
- Step 3 template: 📥 linkage.csv
- Codebook field definitions
Description
The goal is to evaluate what type of linkage works best for each metadata field. Details about this step can be found in the documentation for the F3 principle.
linkage.csv
is a table that describes how the linkage for each of the codebook fields. Starting with this template (📥 linkage.csv), for each codebook field (row) you should write a value of ‘1’ in the column cells if any variable falls under that linkage type.
The interactive table below represents how you should fill out for the dataset you are try to process.
Deliverable: linkage.csv
Step 3 template: 📥 linkage.csv
All codebook fields are linkable only by_variable for the APS dataset so we for all codebook fields we only check (fill out the cell as ‘1’) the by_var column.
Most of the codebook fields in the CNS dataset are linkable only be variable except for:
source
vary byvar_name
+iso2
for some variables but other do not for other variables; so this row has bothby_var
andby_var_iso2
filled out.
Most of the codebook fields in the SVY dataset are linkable only be variable except for:
var_def
vary byvar_name
+strata
for some variables but other do not for other variables; so this row has bothby_var
andby_var_strata
filled out.source
vary byvar_name
+iso2
for some variables but other do not for other variables; so this row has bothby_var
andby_var_iso2
filled out.