A well-structured code list is important for further analysis, where you look for relationships and patterns in the data, with the goal of integrating all results to tell a coherent story. If, as in a survey, you only have questions with the answer categories "yes" and "no" in your questionnaire, your data will only consist of nominal variables. This means that the analysis is limited and does not go beyond the descriptive level. This is like a code list that consists of a set of codes whose analysis level remains indefinite.
- it creates order
- it brings conceptual clarity for yourself and others
- it provides a prompt to code additional aspects as you continue to code
- it will assist you in identifying patterns
- Each code is distinct, its meaning is different from the meaning of any other code.
- The meaning of each code is described in the code comment.
- Each category can be clearly distinguished from other categories.
- All sub codes that belong to a category are similar as they represent the same kind of thing. Nonetheless, each sub code within a category is distinct.
- Each code appears only once in the code system.
- The code system is a-theoretical. This means the code system itself does not represent a model nor a theory. The codes merely describe the data, so that the data can easily be accessed through them.
- The code system should be logical, so you can find what you are looking for.
- The code system contains between 10 and 25 top-level categories.
- The code system has no more than two to three levels. Thus, it consists of categories and sub codes, and possible a dimension like positive / negative, or a time indicator like before / during / after. If dimensions apply to many codes in the code system, it is better to create separate codes and double-code the data with the content code plus the dimension.
The aim of building a code system is that you can access your data through the codes and that you can make full use of the analysis tools. For example, knowing you can cross-tabulate codes using the code co-occurrence table helps to understand why it is important to code in an overlapping fashion.
You start by creating codes to catch ideas, the list of code grows. You then begin to sort and order codes into categories and sub codes making use of the merge and split functions. It is recommended to develop categories that contain only one level of sub codes (two if necessary). This allows you to flexibly combine different aspects when querying the data, and to avoid unnecessary long code lists and code labels.
You will find that you have different types and levels of codes:
- Structural codes that code speaker units in focus groups
- Attribute codes that code sociodemographic attributes of speakers or persons within a document
- Codes that indicate a category and codes that are sub codes of a category, and so on.
As there is only one entity for all of these different things - the code - you can indicate different types and levels using the code label. The table below proposes a syntax that you can use as guideline:
|What||Syntax for Code Label||Example|
|Initial concept||Lower case||personal growth|
|Category||UPPER CASE, colored||EFFECT|
|Sub code||Lower case, same as category color||Effects pos: personal growth|
|Concept that does not fit any category||asterisk (*) label in lower case||*scientific evidence|
|Dimension||Lower case + special character, coloured||/time: during|
|Sociodemographics||prefixed with #||#gender: female|
|speaker units||prefixed with @||@Tom|
# gender: female
# gender: male
*single code 1
*single code 2
*single code 3
category A: sub 1
category A: sub 2
category A: sub 3
category B: sub 1
category B: sub 2
category B: sub 3
You see that the prefixes divide your code system into different sections. This helps you to keep organized and to quickly find what you are looking for. It also allows you to flexibly combine the codes of the different categories or categories with speakers, attributes and dimensions when querying the data.
To sort documents by attributes like gender, age, family status and the like if you have interview data, you use document groups.
Organize your code structure based on conceptual similarities, not observed or theoretical associations, nor according to how you think your will want to write the result chapters.
Use a separate code for each element of what the text is about, i.e., each code should encompass one concept only. If there are multiple aspects, the passage can be coded with multiple codes.
Don't worry if not all of your codes can be sorted into a category. Some codes will remain single codes. In order not to "loose" them in the categories, use a special prefix, so they show up in their own section in the code system.
Users are often tempted to use code groups as higher order categories. This defeats the purpose somehow. Code groups are filters and codes can be assigned to multiple code groups. A code of one category can however only belong to one and not to multiple categories. This is why code groups do not serve well as higher order codes. If you want to build categories and sub codes, the recommendation is using the above suggested syntax instead. Indicate a category by using capital letters.
Once you have developed categories with sub codes, you can create a code group for each category for the purpose of using it as filter (see image above). Code groups will allow you to filter by categories, and for further analysis, you can use the code groups to analyse on the category level rather than the sub code level. If you have a lot of low frequency code that you want or need to merge, then code groups are a good way to collect them. After you have added all low level codes that belong to the same theme / topic / idea, you can set this code group as filter. This makes it easier to merge the codes. You can then add prefixes, and the category code in capital letters.
Video Tutorial: Merging Codes
Once the data is coded, you have a good overview of your material and can describe it. You can then take the analysis a step further by querying the data. The tools that can be used include the code co-occurrence table, the code document table, the query tool, and the net
The goal is to delve deeper into the data and find relationships and patterns. Writing memos is very important at this stage as much of the analysis does not just happen because you apply a tool. The insights come when reading the data resulting from a query, and when writing summaries and interpretations.
The recommendations in this section are based on the following authors:
Bazeley, Pat (2013). Qualitative Data Analysis: Practical Strategies. London: Sage. Friese, Susanne (2019). Qualitative Data Analysis with ATLAS.ti. London: Sage. Guest, Greg, Kathleen M. MacQueen, and Emily E. Namey (2012). Applied Thematic Analysis. Los Angeles: Sage. Richards, Lyn and Janice M. Morse (2013, 3ed). Readme first: for a user’s guide to Qualitative Methods. Los Angeles: Sage. Saldaña, Jonny (2015). The Coding Manual for Qualitative Researchers. London: Sage.