Jump to content

Recommended Posts



I’m working on a project with several coders, and when merging their projects prior to running a comparison query, I’m finding that some coders reorganized the nodes, and therefore Nvivo recognizes them as discrete and they become duplicates rather than merged.


Of course this will cause inaccuracies in Kappa when we run the comparison query for inter rater reliability. Might you have a suggestion for correcting the node organization issue?


I’m trying to make folders in the Nodes in the hopes that I can aggregate the discrete nodes. Perhaps there is a better way…

Thank you in advance,


Link to post
Share on other sites

Hi Chelsea,


As you are already aware, the nodes need to have the same name and hierarchical location in each project to be deemed as duplicate nodes. When merging Merge into existing item needs to be selected at For duplicate items in the 'Import Project' dialog box.


If feasible, you could adjust the nodes and hierarchy to be identical in each project and then re-perform the merge into the previous un-merged project. If not feasible, then you could merge each duplicate nodes, by right-clicking the node and selecting Cut and then click the node you want to merge into and select Merge into Selected Node.





Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...