QSRSupport

Hi Di Feng, The Group Query doesn't calculate the common coding references, it finds out the common items. Whereas the compound query can be used to find common coding references using AND criteria. This is the reason results are different. For example, if you code the first paragraph from a source to Node A and second paragraph from the same source to Node B, the Group Query will show 1 reference each. On the other hand, Compound Query will result 0 references because there isn't any common text which has been coded to both nodes. Kind Regards, Bhupesh

Hi BMY, Please refer to "Merge or Copy Classifications" section in the link below for instructions on merging classifications in NVivo: https://help-nv.qsrinternational.com/12/win/v12.1.90-d3ea61/Content/classifications/manage-classifications.htm Kind Regards, Bhupesh

Hi Di, The compound and group queries are quite different and if they are needed in a project would depend on the data you are working with or research goals. Below are some links from our online help with more information on both queries: https://help-nv.qsrinternational.com/12/win/v12.1.90-d3ea61/Content/queries/compound-query.htm https://help-nv.qsrinternational.com/12/win/v12.1.90-d3ea61/Content/queries/group-query.htm Regards, ^NVivoSup

Hi Di, Instead of a set, you can try running a Coding query and for each attribute value, add a criteria row to search for coding linked to cases with that attribute value, for example: Coded At - Any Case Where Township = Smyrna After this query has run, you can then save the results to a node by right clicking on the node, selecting Store Query Results and selecting to save to a new node. Once the node is saved, this node can then be used in other queries, such as a row input for a matrix coding query. Hope this helps. ^NVivoSup

Hi Amir, Thank you for contacting NVivo Support. To investigate the issue, can you please provide me with the screenshot of the details you have entered in the query criteria? Once I have the above information, I will be able to assist you further. I look forward to your reply. Regards, Akshay

Hi gracespring, I see that you've also contacted us directly via email and one of our support team members has been in contact and is trying to resolve this for you. ^NVivoSup

Hi, Our technical team is working on resolving compatibility issues with Mac OS Catalina and hope to release an update in 2-3 weeks. You'll be prompted by NVivo to install the update as it is released. Kind Regards, Bhupesh

Hi Valerie, We have been communicating to you via email. Please provide us your file for further investigation. Kind Regards, Bhupesh

Hi Audrey, The ‘Compact and Repair Project’ button is greyed out because the project may be open in NVivo. Please close the project by clicking File tab > Close and then try Compacting and repairing your project. Can you please open the sample project in NVivo and see if the same issue persists? If the issue does not persist in the sample project, we will need access to your project to investigate the issue. I hope this helps. Regards, Akshay

Hi, Please see below the responses to your queries: 1. You may wish to create a classification called Groups and also give Attribute values such as Group A and Group B. Then a Case called Interviewees, school, lecturers etc. based on your project. Open each case and assign classification Groups and attribute values A or B. Once you have done that, you should be able to run Mate Coding query. Please see the link below for more information on Matrox Coding query: https://help-nv.qsrinternational.com/12/mac/v12.1.86-d3ea61/Content/queries/matrix-coding-query.htm 2. In regards to your query, each user will need to code the transcript in the same project but different copies using their own user profiles. Once all the users have finished coding in their individual projects, you will need to merge all the projects for e.g. Merge Project 1 with Project 2 and project 2 with Project 3. Once the merge is complete, you should be able to run Coding comparison query in the project. Please see the link below for information on merging projects: https://help-nv.qsrinternational.com/12/mac/v12.1.86-d3ea61/Content/projects-teamwork/import-items-from-another-nvivo-project.htm Also, please see the link below for information on Coding Comparison Query: https://help-nv.qsrinternational.com/12/mac/v12.1.86-d3ea61/Content/queries/coding-comparison-query.htm 3. In relation to the third query, you should be able to add the unwanted words to the ‘Stop Words’ list by following the steps in the link below: https://help-nv.qsrinternational.com/12/mac/v12.1.86-d3ea61/Content/queries/text-content-language-and-stop-words.htm Please see the link below for information on contact numbers and submitting a support request: https://www.qsrinternational.com/nvivo/contact-us Also, you may reach out to our NVivo certified trainers who should be able to assist you with your project related queries and give one on one guidance: for additional cost https://www.qsrinternational.com/nvivo/nvivo-training/certification/find-a-trainer-near-you I hope this helps. Regards, Akshay

Hi cogden, Changing the name of a source document will not impact the coding, however if you are sharing a project and intend to merge copies of a project file, the names of documents must be the same in both to prevent duplicates. Hope this helps. Regards, ^NVivoSup

Hi Cassie, This report unfortunately cannot show both the theme node, coded text and the classification attributes of intersecting nodes. However, as a workaround you can use the coding stripes feature. To do this, open theme node in detail view and turn on a coding stripe for the attribute required. The below link has more information on coding stripes. https://help-nv.qsrinternational.com/12/win/v12.1.86-d3ea61/Content/coding/coding-stripes.htm The node detail view with coding stripes can be exported by printing the node references but selecting to print to a file instead of a printer, you may see an option to use Microsoft Print to PDF or similar. Hope this helps. Regards, ^NVivoSup

Hi Cara, You can try making a copy of your project then deleting the case classifications in the copy of the project and see if that helps. You may also like to look at the literature review workflow outline on the following link, this is an example of how such a project may be set up: https://help-nv.qsrinternational.com/12/win/v12.1.86-d3ea61/Content/concepts-strategies/using-nvivo-for-qualitative-research.htm If this does not resolve the problem, we would suggest someone take a look at the project to understand what is required and suggest a solution. QSR Support are not trained to provide guidance in situations like these however we can provide the contact details of nearby NVivo trainers and consultants who can who can provide this service at a cost. If you would like us to arrange this please send your details to our team via info@qsrinternational.com. Regards, ^NVivoSup

Hi Angela, Cases will act as the link between the source documents and the theme/auto-coding nodes. Typically these cases would be a unit of analysis in a project and only one reference would be coded to them, the source document. References from interview participants would be coded against the theme/auto-coding nodes. As long as the theme node is coded from the same source attached to the cases, there is a link. Hope this helps. Regards, ^NVivoSup

Hi Mandy, A codebook is a document that has names of your nodes along with their description. NVivo 12 supports importing codebooks in qdc format and you can have two codebooks in a project. If you are referring to exporting separate codebooks, you can select the codes and export them to separate codebooks. Refer to the link below: https://help-nv.qsrinternational.com/12/win/v12.1.86-d3ea61/Content/nodes/export-nodes.htm Kind Regards, Bhupesh