The mapping process can be less manual by using .txt files. Please send the files to Hayley Mills to load into Archivist. Once loaded you can then check the mappings. The format specifications are given at below along with examples. A list of the Archivist pages which can be used to check the mappings (and view a list of questions) can be found at the end of the page with examples.
Grid mappings and derived variable mappings currently must be completed using .txt files.
Note: Only one topic can be applied to a grid as a whole- this means that all variables mapped to a grid question must have the same topic.
It is recommended that you create only one topic mapping file first (preferably variable to topic) as the other will be inherited once the question and variable have been mapped. Any gaps in topics can then be filled afterwards. This should prevent topic conflicts.
Format specifications
qv.txt
Mapping file which links questions and variables.
- Tab delimited
- 4 columns:
1. Questionnaire prefix with _ccs01 suffix
2. Question label (with optional suffix grid cell coordinates in the format $X;Y. Please refer to the Grid coordinates table on the condition page for how to reference grid cells.)
3. Dataset prefix (which usually matched the questionnaire prefix but without the suffix)
4. Variable name
tv.txt
Mapping file which links topics and all variables.
- Tab delimited
- 3 columns:
1. Dataset prefix
2. Variable name
3. Topic ID (Uses Colectica topic IDs)
tq.txt (this can be inherited using the qv and tv mappings)
Mapping file which links topics and questions.
- Tab delimited
- 3 columns:
1. Questionnaire prefix with _ccs01 suffix
2. Question label
3. Topic ID (Uses Colectica topic IDs)
dv.txt
Mapping file which links derived variables to source variables.
- Tab delimited
- 4 columns:
1. Dataset prefix
2. Derived variable name
3. Dataset prefix
3. Source variable name
Archivist pages to view mappings
Note: you must be logged into Archivist to view the below pages.
A question list can be saved as a .txt from Archivist by navigating to the instrument view and then adding /cc_questions.txt to the web address e.g.https://archivist.closer.ac.uk/instruments/ncds_65_eq/cc_questions.txt
A question list with sequences can be saved as a .txt from Archivist by navigating to the instrument view and then adding /mapper.txt to the web address e.g.https://archivist.closer.ac.uk/instruments/ncds_65_eq/mapper.txt
A variable list can be saved as a .txt from Archivist by navigating to the dataset view and then adding /mapper.txt to the web address e.g. https://closer-archivist.herokuapp.com/datasets/130/variables.txt
Mappings (once applied) can be viewed in Archivist by navigating to either the instrument or dataset view using the following suffixes. Details of the formats for each can be found at the bottom of this page.
Question to variable mappings add /qv.txt to the instrument web address e.g.https://archivist.closer.ac.uk/instruments/ncds_65_eq/qv.txt
Question to topic mappings add /tq.txt to the instrument web address e.g. https://archivist.closer.ac.uk/instruments/ncds_65_eq/tq.txt
Derived variable mappings add /dv.txt to the dataset web address e.g. https://closer-archivist.herokuapp.com/datasets/130/dv.txt
Variable to topic mappings add tv.tx to the dataset we address e.g. https://closer-archivist.herokuapp.com/datasets/130/tv.txt
Dataset and instrument views
Datasets > search and select the Name of the dataset. Any mapping conflicts will appear in red.
The question-variable mappings can also be checked through Instruments > search and select the Prefix (or view) of the instrument. This will gives the questionnaire view with the variable names listed against them
Note: Variables can be mapped to grid references in the mapping.txt file, but currently these will only be displayed as mapped to the gird as a whole. See table for how to map to grid cells.