Signup date: 27 Oct 2011 at 11:05pm
Last login: 02 Nov 2011 at 11:11pm
Post count: 4
======= Date Modified 28 Oct 2011 05:37:03 =======
======= Date Modified 28 Oct 2011 05:35:52 =======
======= Date Modified 28 Oct 2011 00:34:46 =======
It might be more efficient for you to have tree nodes like this:
- since enrolment
- prior to enrolment
- student loans
- full time job
- Social Network
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
Masters DegreesSearch For Masters Degrees
An active and supportive community.
Support and advice from your peers.
Your postgraduate questions answered.
Use your experience to help others.
Enter your email address below to get started with your forum account
Enter your username below to login to your account
An email has been sent to your email account along with instructions on how to reset your password. If you do not recieve your email, or have any futher problems accessing your account, then please contact our customer support.
or continue as guest