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

Hi Liz, Printing coding stripes seem to be the best option. You can open a source, turn on Highlights & Coding Stripes and then print this to a PDF. This will show you entire source with names of your nodes along with highlighted sections in the source that have been coded. Here is detailed information on Highlights and Coding Stripes: https://help-nv.qsrinternational.com/12/mac/v12.1.86-d3ea61/Content/coding/highlight-coding.htm https://help-nv.qsrinternational.com/12/mac/v12.1.86-d3ea61/Content/coding/coding-stripes.htm Kind Regards, Bhupesh

Hi Leslie, You can right click on your cases, click Create As>Create as Code/Node to convert the cases back to nodes. Thereafter, you can delete the cases. I hope this helps. Regards, Bhupesh

Hi Asterinidae, Case attributes and values can be imported by using a classification sheet, see the following link for more information: https://help-nv.qsrinternational.com/12/win/v12.1.86-d3ea61/Content/classifications/classification-sheets.htm Hope this helps. ^NVivoSup

Hi Peter, Thank you for contacting NVivo Support. Unfortunately, there is no way to exclude specific excel rows/columns after you have imported the dataset in your project. You will need to edit the excel file outside of NVivo and then import the excel file in your project. I hope this helps. Regards, AKshay

Hi, If all 5 interviews are in a single document, you can create 5 nodes based on interviews and code respective interview text to those nodes. Then you run a Matrix Coding query between interview nodes and your theme nodes. The resulting matrix will show the number of common coding references across interviews and themes. The other solution which you've already tried is to have these interviews in separate documents. You can then run a Matrix Coding query between interview documents and nodes. Kind Regards, Bhupesh

Hi, There are 2 scenarios when duplicate entries can occur in a framework matrix: 1. If you have previously created a framework matrix in your project, the summaries are not deleted from the project even when you delete the framework matrix. If you then create another framework matrix which contains the same intersection (I.e same combination of themes and cases) this summary will be automatically added to your framework matrix. 2. When the auto summarise function is run, it adds a new copy of the summaries, rather than updating the existing summary. So if the auto summarise feature is used more than once, the summaries will get duplicated. A workaround for now would be to manually erase these summaries from your matrix (backspace or select all the text and delete). In regards to the issue about matrix not picking the data, the framework matrix cells have a character limit of 8000. This can result in missing data in cells where character limit is exceeded, when you use Auto-Summarize feature. Kind Regards, Bhupesh

Hi mhraymond, you can find references that were coded after a certain date by running a custom report. You can find information on how to run a custom report at the following link: https://help-nv.qsrinternational.com/12/win/v12.1.86-d3ea61/Content/projects-teamwork/create-reports.htm#CreateareportusingtheWizard To find all the references coded to a node after a certain date select the following criteria for each step of the report wizard: Step 1: Select to create a report from the 'Code' view. Step 2: Include the following fields: • Code.Name • Coded File.Coding Reference.Coded Text • Coded File.Coding Reference. Modified On Step 3: Add the following filters: • 'Code.Name' 'In' • 'Coded File.Coding Reference.Modified On' 'On or after' Step 4: Group by Code.Name For steps 5-7 you can click next to accept the defaults. On step 8 you will need to set a name for your report and then click 'Finish'. When running your report tick the check boxes next to both of your filters, and use the Select buttons to choose the codes and date ranges you are interested in. The output should show the code name, the coded text and the date it was coded. Regards, Heather

Hi Gail, I have attached a corrupt dummy project with this email to help you recover the project from the .nvb file. Please follow the steps below to recover your data from NVB file: 1. Download and unzip attached file(based on your NVivo version) to your computer. 2. Open NVivo, click on Open Other Project, then browse and select the dummy file saved in step 1. 3. You will be presented with an option to recover from a project recovery file. Select your .nvb file from the list to recover the project. If your project does not appear in the list, you can try searching your computer for any .nvb files, these are project recovery files. 4. The project should open once recovery is complete. I hope this helps. Kind Regards, Bhupesh NV12CorruptProject (for restoring project backups).nvp.zip NV11CorruptProject(for restoring project backups).nvp.zip

Hi Audrey, We've sent you an email with some more information on this. Regards, ^NVivoSup

Hi ellisjen, If you are merging two projects, each with coding on a document, that source document will duplicate if both copies do not have the same name, folder location and content. In this case you would need to undo the edits or add these to the unedited version so that both match before merging the projects. The below page has some information on how NVivo determines duplicates and how they are handled when a project is merged: https://help-nv.qsrinternational.com/12/win/v12.1.86-d3ea61/Content/projects-teamwork/import-items-from-another-nvivo-project.htm ^NVivoSup