Moving beyond descriptionĭepending on how you have developed your nodes in NVivo, you might find at this stage that your nodes are quite “low-level” or descriptive. All of these tasks can be quickly and easily completed in NVivo. Viewing your standalone nodes can sometimes reveal that they can be grouped together in a hierarchy. Sometimes the opposite applies and you need to “code on” from a larger node to create more specific categories.
Alternatively, some of the data may have been coded incorrectly to the wrong node, and it pays to find this out sooner rather than later so that it can be corrected.Īt this stage you may also want to check whether any categories can be combined to create broader themes. In some cases, we might adjust the level of coding (is there too much or too little material coded for example). The first thing we usually do is read through the content of each node to check if it’s correct. Once you’ve “finished” coding in NVivo, it pays to review your coding and node framework.
If this applies to you, read on for some tips on moving forward at this stage of the analysis process – some of these are NVivo specific but others require a bit of old-fashioned brain work! Note that this blog post refers to 'nodes' in NVivo – if you're using a more recent version of the software, these have been renamed 'codes'.
#NVIVO TUTORIAL HOW TO#
They know they eventually need to start writing, but they’re not sure how to get there from their coded nodes. A common problem researchers face when they’ve completed their initial coding is knowing what to do next.
0 kommentar(er)
