The new version of NVivo, launched by QSR in March 2020, is now available through Chest. Licensor: QSR International (UK) Ltd, registered in England and Wales (company number 6906225), The Innovation Centre, Sci-Tech Daresbury, Keckwick Lane, Daresbury, Cheshire WA4 4FS. This Agreement has been negotiated by Chest in response to a need within the Education community. Higher and Further Education, Research Councils, Associated Sites, Charities in the United Kingdom and Third Level Institutions in Ireland Background Information
This is fully functional software that can be used for a 14 day period.
You can test the latest version of NVivo with a free trial. Institutions will be committed to the licence for a three or five year period. Subsequent invoice date: annually three months in advance of the anniversary of licence start date Licence Type Service packs are available free of charge to all NVivo users, and can be downloaded from the QSR website.Free major software upgrades at the time they are released.Fixed pricing for 3 or 5 years (depending on term you choose).Heavily discounted pricing for the academic community.There are some sample coding systems on my website which might provide some guidance if you're having any issues figuring it out (and a lengthy discussion in my book).New NVivo now available - see Product Information tab Benefits Two 'rules of thumb' to guide you are: you should not ever have to repeat the same node in different trees and, it is very rare to need to go down more than, say, three layers. The key thing to remember is that the coding system is a classification system - a taxonomy of your concepts - not a theoretical model (there are other tools for recording theoretical or empirically observed associations). people associated with an action) rather than subcategories or types of whatever it is. It sounds like you're on the right track with what you are talking about doing - the problems arise when you start putting things that are associated with something as children of that something (e.g. The other danger to be aware of, if you move to trees too early (and especially if you are a bit inexperienced), is that you are likely to create a 'stuffed up' coding system. THe advantage of not starting with a predetermined tree structure is that you often aren't sure what it's going to be until you have worked through a doc or two.
There's actually no reason why you can't start working in the Tree Nodes area and just gradually move/subdivide nodes into trees as you go, leaving some as 'childless' for the time being - it's just been a convention to store initial unstructured coding in Free Nodes (dates back to the way that NUD*IST worked). Presumably I can move the tree nodes around in a hierarchy once I've decided on one? The free node doesn't allow you to break down the data in that way does it? Then I want to break that node down into different aspects that are contained within that node, so I turn it into a tree node that becomes the parent, so that I can make child nodes e.g 'exam results', "confidence and self esteem", "employment prospects". a free node that is about 'student outcomes' contains all the data relating to anything to do with student outcomes. Hi Crispy, yes I'm thinking though that the minute you want to categorise the responses within a free node down to reflect several aspects of the node, that you must have to turn it into a tree node. If you had predetermined headings, then I imagine you COULD just use tree nodes from the start. I'm also new, so this might be a rubbish answer, but I assume it's because with a lot of qualitative work, it's only once you're actually DOING the coding that relationships between groups of data become apparent.