Nest codes. Create themes or categories.

Group your codes into themes or categories by nesting them into a hierarchy

LaiYee Ho avatar
Written by LaiYee Ho
Updated over a week ago

After creating codes, you may want to group them into themes or categories. You can do this by "nesting" the codes into a hierarchy.

To create a new theme or category, just create it the way you would create a new code. And then drag and drop the relevant codes underneath it.

You can also turn an existing code into a theme or category by dragging and dropping other codes underneath it.

Watch video with voiceover instructions

Click on the code you want to move, drag it to the location you want it to go, and then let go of your mouse.

Tip: Use the light blue line to see where the code will be when you drop the mouse.

Watch a video example of how to group codes into themes and categories.

Frequently Asked Questions About Nesting Codes

How do I unnest a code?

A: Unnesting a code in Delve, or moving it to the top level, can be done easily using three main methods:

Top of the list: Simply click and drag the code you wish to unnest to the very top of the code list. In the example below I am unnesting the Code E by dragging it to the top of the list.

Bottom of the list: Alternatively, you can drag the code to the very bottom of the list. In the example below I'm unnesting Code E by dragging it to the bottom of the list.

Between two top level codes: This requires collapsing all top-level codes first. Once this is done, you can drag and drop the code in between these top level codes to unnest it. In this example below I want Code E to be between Code A and Code D. First I collapse Code A.

Now that Code A is collapsed I can drag and drop Code E between Code A and Code D. Code E will be unnested and between the two codes.

Q: How deeply can I nest codes in Delve?

A: In Delve, codes can be nested up to three levels deep. This means you can have a code within a code within a code, but no further. It's a rule of thumb in qualitative coding to not have a hierarchy more than three levels deep. This ensures the manageability and clarity of your code structure as your analysis progresses, and it helps prevent your analysis from becoming overly complex or unwieldy.

Did this answer your question?