Hi RLD

Hope your reorganization went well. I'm happy to help out - the QSR forum (http://forums.qsrinternational.com/) is also a good place to go to get help from other NVivo users.

Cheers,
Kath

======= Date Modified 28 Oct 2011 05:37:03 =======
======= Date Modified 28 Oct 2011 05:35:52 =======
======= Date Modified 28 Oct 2011 00:34:46 =======
Hi RLD,

It might be more efficient for you to have tree nodes like this:

Positive outcomes
Negative outcomes
Attending university
- since enrolment
- prior to enrolment
Financial
- student loans
- full time job
Mental Wellbeing
- Social Network
- Confidence

Then when you are coding a passage, you can code it at all the relevant nodes. For example -when you find content about 'positive financial outcomes since enrolment' - you code it at 'positive outcomes' AND 'since enrolment' AND 'financial'.

Then you can use queries to bring the fragments back together - for example, run a Coding Query to find all the content coded at 'postive outcomes' AND 'since enrolment' or all the content coded at 'since enrolment' AND 'financial'. You can put the data back together in all sorts of combinations without drowning in your node pool!

Hope this helps. You are not alone in this dilemma - there is a discussion about structuring nodes on LinkedIn - http://linkd.in/sBZXJF

Cheers
Kath