Working with Codes
Before we work some more with Codes, create two more codes called “Energy Efficiency” and “Water Consumption”.
Next, code at least 5 small text fragments to each new code.
You can see now there are useful counts associated with our codes to see how many files have content that has been coded in that code, and how many text snippets or references have been coded into that code.

You will notice that all of our codes are top-level or parent codes, meaning we haven’t established a hierarchy, none of our codes are nested under other codes. NVivo can help you organize your codes in a hierarchical structure. You are often, in the end, trying to create a hierarchical codes list to group common codes together into broader categories and themes to help make sense of your coding. Create a new code and call it Sustainability.

You could use this code to group some of your existing codes. Drag Energy Efficiency and Water Consumption onto the Sustainability code (First click on a code to highlight, wait a moment, then drag it on).

Now you can see that they are grouped beneath. Codes grouped beneath another code are called Child Codes.

You can use Sustainability as its own broader code now in coding, or just keep it as a heading in the hierarchy. Double click on Sustainability. You should see an empty window pop up as there are no references coded to that code right now.

Right click on Sustainability and select Code Properties.

Click the box next to Aggregate Coding from children. Then click OK.

Now you should see all the references to Sustainability’s code, plus its children codes, show up in the window that popped-up before (and is still open). You will need to decide how to want to handle your code hierarchies in terms of this aggregation for your own projects. In some cases, this is very useful, but it may affect queries where references are double counted for the parent and the child. We will talk more about queries later in the tutorial.

In the window with all the Sustainability references, highlight all the text. A quick way to do this is to click anywhere in that window and press CTRL and “A” on your keyboard at the same time to select all.

Then go to the menu at the top of the document, select the Content drop-down menu and pick Broad under Coding Context.

You will see that the references have changed. There is grey text that isn’t coded, but comes directly before or after the coded text to give you more context for what you have coded. This is useful when examining small snippets of coded text. You can apply this Broad context (or explore the other options in the menu) any time you are presented with a list of references. Close the tab for now.

Another way to get a better idea of how your files are coded is to use coding stripes and highlighting. First, go to your interviews folder. You can see how many codes have been applied to the content and how many references in the document have been coded.

Double click on an interview that has some coded references.

From the menu at the top of the Document, select the Coding Stripes drop-down menu and pick All.

It will automatically select colours to differentiate the codes. You should see coloured stripes along the right to tell you what parts of the document have been coded and how. Note: You can customize the colours by right clicking on each code and selecting Color, and then picking your colour of choice. After you’ve set up all your colours, click anywhere on the text of the interview, select the Coding Stripes drop-down menu, and pick Item Colors instead of leaving Automatic Colors selected.


Next, from the menu at the top of the Document, select the View drop-down menu and pick All Coding under Highlight.

You will see the coded text in yellow highlighting.

Technique: Qualitative Data Analysis | Tools: NVivo