UCL WIKI

UCL Logo
The Wiki will be upgraded to version 6.3 in early August - exact dates will be announced shortly. Please see the 6.0 Release notes and 6.3 Release notes for info on new features.
Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Code lists for labelling the X (column) and Y (row) axes in grids usually contain a reference to the grid axis the code list creates. For example, for grid question A4 (qc_A4), the label for the Y axis code list would be cs_qA4_Y, and the label for the X axis code list would be cs_qA4_X. The code list labelled cs_dash (containing the single category of '-') is used as the X axis code list for all grids with a single column with no heading label (see Question Grids for more details). When a grid has a corner label, the code list label for either the X or Y axis is the corner label text with the cs_ prefix (see Question Grids for more details). See   How to Construct a label for further guidance.

Assigning code values

...

In a ‘Tick all that apply’ answer, if a respondent doesn’t need to choose a category, cardinality is 0:n, with n the total number of categories the respondent can choose. If a ‘Tick all that apply’ code list contains the category ‘None of the above’ or similar, or is within a condition which assumes that there is an answer, the cardinality is 1:n, with n the total number of categories the respondent can choose, not counting the ‘None of the above’ category. (Examples to be added)

Scales

There are two types of scale response domain which can be found in questionnaires, those which have discrete points which the respondent can select, and those which are a line which the respondent marks. The former are entered as a code list, the latter are yet to be entered into Archivist. Example 1 below shows a question where a code list is used as the response domain to represent the scale.

Example 1 Questionnaire: NCDS What do you think 1991

Questionnaire layout:

Image Modified

Archivist Build / Code lists view:

To be added.

Archivist view: (ncds_91_wdyt)

To be added.

Concatenating categories

Sometimes it is necessary to concatenate code list category text into one category. This could be because extra information is provided along the side of the code list, e.g. Example 2, or it could be because there are heading headings to the categories see , e.g. Example 3. Example 2 has additional text to the side of the code list which applies to certain categories. If this was added as a statement then it would not be clear which categories this text applies to, therefore the text is added the code list categories. The order of this concatenation is dependent on the position of the text next to the categories, in this case the text is positioned before the categories and so it is added before.

Example 2 Questionnaire: NCDS Interview 1981

Questionnaire layout:

To be added.

Archivist view: (ncds_8_i)

To be added.A colon is added in between to denote the two levels. Example 3 below has code list categories which are divided up by headings which apply to some of the categories, again these must be concatenated to the category . In this case however, with a colon is used between the concatenation to signify that the different levels in the category.

...

to denote the levels.

Example 2 Questionnaire: NCDS Interview 1981

Questionnaire layout:

Image Added

Archivist view: (ncds_8_i)

Image Added
 

Example 3 Questionnaire: USoc Youth Self-Completion 2009

Questionnaire layout:

To be added.Image Added

Archivist view: (us1_ysc)

To be added.Image Added