You might define the relationship type to be ‘precedes’ or ‘is conditional on’ for example. If you believed that Node A/child 1 had to be present to influence an outcome as coded in Node B/child 1. So let’s say the nature of the relationship was one of sequencing phenomena. Remember, a relationship is a node in its own right.
NVIVO 12 CREATE TABLE CODE
Then, form the relationships and code content that support the relationship to these new nodes. You would first have to define the relationship type in ‘Classifications->Relationship Types. My response was that I think it depends on the nature of the relationship between the child nodes in parent ‘A’ and ‘B’. anything on 'Links' might be helpful too….many thanks in advance….
I've trying looking up youtube clips re Relationships and can't find anything …. Am I trying to be too 'clever'? Should my question be 'can someone describe how they have used relationships'? Now that I'm starting into the next phase of coding I want to be 'clever' and reflect this in my coding. I'm trying to structure the child nodes in A so that I keep their distinct nature and link them to the child nodes in B using Relationships. I've realised that the content of a Parent Node A broadly comes before Parent Node B. I've finished coding & analysing my pilot data. I responded to a query on the LinkedIn NVivo user group today from someone asking for general ideas and interesting ways of using relationship nodes in NVivo.