Looking at the results you’ve uploaded both “A and B” and “A and not B” are 0, which indicates that user A has not coded anything for these source and node combinations.
It might be the case that user A has genuinely not coded to these source and node combinations, in which case a kappa of 0 would be accurate.
Another scenario is that your two projects have not merged as expected, which can happen if NVivo does not detect that project items such as sources and nodes are duplicates. NVivo has certain criteria that need to be met for project items to be automatically merged and if these are not met both copies of the project item will be kept in the merged project. If that’s the case you’ll have 2 separate copies of sources and/or nodes.
If your projects have not been merged successfully, the easiest way to fix this would be to go back to your two separate project files and edit each of these so that they would now merge successfully. Once they have been merged successfully you should be able to run your coding comparison query again and get a more meaningful result.
To merge successfully, you will need to make sure that duplicate project items are named identically and are in the same location within each project. Depending on the type of project item there are some other criteria that will need to be met to be able to merge successfully and you can find details of these at the following link: http://help-nv11.qsr...ring_import.htm
If you’ve gone through this process and you’re still experiencing difficulty with merging or running your coding comparison query, please submit a support request form at the following link as we may need to see a copy of your project to be able to assist further.