Jump to content

QSRSupport

QSR Staff
  • Content count

    2,199
  • Joined

  • Last visited

  • Days Won

    85

QSRSupport last won the day on September 27

QSRSupport had the most liked content!

Community Reputation

76 Excellent

1 Follower

About QSRSupport

  • Rank
    Advanced Member

Contact Methods

  • ICQ
    0

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

19,742 profile views
  1. Collapsing node name column

    Hi Helen, Thanks for giving that a go. I’ve just tried following the workaround steps again with the node list view as the only thing open and I was able to replicate what you’ve experienced. Can you please try following those steps again, but with the list view displayed to the left of the detail view? Customising the list view from here should hide these columns as expected. Another thing that may be helpful to you would be to minimise or hide the navigation view. This would let you have some more screen space to display the list view and might make this problem less noticeable. You can hide the navigation view completely by clearing the “Navigation View” checkbox on the “View” tab. If you would like to minimise the navigation view you can do so by clicking on the “<” arrow at the top of the navigation view. Regards, Heather
  2. Collapsing node name column

    Hi Helen, I’ve passed feedback about this issue to the relevant team. If you’re not interested in the number of nodes or references, as a workaround you can customise the list view to not display the “Sources” and “References” columns. This should stop the list view from automatically resizing columns. To do this: On the “View” tab click “List View” and then “Customize…” In the “Selected columns” list select “Sources” and then click “<<” to remove this column Repeat this process for the “References” column Click “OK” Regards, Heather
  3. Hi Lynn, The options to print “Classification” and “Attributes” are greyed out when printing a theme node and this is the expected behaviour. These options are only available when printing a case node or source that has been classified. The best way to show the information you’re after would be to print your node with coding stripes turned on for each attribute value you are interested in. Please see the following link for how you can display coding stripes for case attribute values: http://help-nv11.qsrinternational.com/desktop/procedures/use_coding_stripes_to_explore_coding.htm?#MiniTOCBookMark9 Regarding how you’re coding your sources, typically, you would code anything relevant to the case to the case node (e.g. their responses to interview questions, etc.) and anything relevant to your theme nodes to the theme node, and it seems like this is what you have done. Regards, Heather
  4. Query results vanish upon coding to a node

    Hi, It is correct that query results disappear when you code from a source. This occurs because query results become obsolete when you code to a node. I have raised this with our Product Team so that user experience can be improved in future. Regards, Bhupesh
  5. Mac OS High Sierra Drag and Drop Coding Issue

    Hi Ruth, I have tested drag and drop coding using Mac OS High Sierra, but so far have not been able to reproduce this issue. Can you please submit a support request form at the below link as we’ll need some more details from you to be able to troubleshoot this problem. http://www.qsrinternational.com/nvivo/contact-us/customer-support Thanks, Heather
  6. Linking a batch of webpages (NCapture)

    Hi Inbal, It is not possible to capture multiple websites at once and I am sorry, we are not aware of any workarounds. Kind Regards, Bhupesh
  7. Hi, In order to link your case attributes to sources, you simply need to code from sources to the cases. When this happens, you should be able to run queries based on attributes across your sources. If you had separate single interview sources for each participant, you could have created each source as a case. Using "Create as Case" option codes whole source to respective case automatically. Kind Regards, Bhupesh
  8. Hi Mackie, You can open the source and turn on Coding Stripes for All Nodes Coding to see the nodes data has been coded to. Refer to the link below for detailed information on Coding Stripes: http://help-nv11.qsrinternational.com/desktop/procedures/use_coding_stripes_to_explore_coding.htm I hope this helps. Kind Regards, Bhupesh
  9. Recovering project from a. nvb file

    Hi Alicja, I have attached a corrupt dummy project with this post to help you recover the project from the nvb file. Download, unzip and extract the attached file to your computer. Then attempt to open it in NVivo. You will be presented with an option to recover from a project recovery file. Select your nvb file to recover the project. I hope this helps. Kind Regards, Bhupesh NV11CorruptProject(for restoring project backups).nvp.zip
  10. Number of Memos per Source

    Hi Doug, It is not possible to link multiple memos to a single source because each source or node can have one memo linked to it and that memo cannot be linked to any other item. Kind Regards, Bhupesh
  11. Import classification sheet Error.

    Hi Betty, To investigate, could you send us your classification sheet via a support request at http://www.qsrinternational.com/nvivo/contact-us/customer-support & we'll get back to you? Kind Regards, Bhupesh
  12. MacOS High Sierra won't let me use NVIVO

    Hi Kate, The latest update to MacOS introduced a new file system that is not compatible with older versions of NVivo for Mac. Support for the Apple file system (apfs) was introduced in the latest update of NVivo for Mac Version 11. Please follow the steps below to update your NVivo for Mac: 1. Make sure the NVivo application is closed before you install the new version. (You may need to right click NVivo icon in the dock and click Quit) 2. Download NVivo for Mac(version 11) from our Downloads page below: http://www.qsrinternational.com/support/downloads 3. Locate and double-click the NVivo.dmg file that you downloaded. 4. Drag the NVivo icon into your Applications folder. 5. During the installation, if you are asked whether you wish to replace the older version of NVivo, click Replace. 6. Go to Finder>Applications, right click NVivo icon and click Get Info. Confirm that it shows version 11.4.2 7. Double click same NVivo icon, paste your license if prompted and activate the software. Once this is done, you should be able to work on NVivo projects. I hope this helps. Kind Regards, Bhupesh
  13. Hi, It seems that your NVivo project has got corrupted. We have responded to you via email and we look forward to your reply. Regards, Bhupesh
  14. NVivo Crash, data lost

    Hi, This data loss issue can occur with projects located on a Network location. By default, if the project is stored on a network drive, when you save, your changes are saved locally and the .nvp project file on the network is not updated until you close the project. If you haven't already tried the steps below, please ensure NVivo is closed then follow the steps below to try to recover lost data: Windows 8 From the Start screen, start typing Explorer and click on File Explorer in the search results displayed A new File Explorer window opens up. Click on the View tab and check the Hidden Items option. Navigate to C:\Users\<your username>\AppData\Local\Temp Look for a file that has the same name as your NVivo project but with a _log at the end, so it would be '<project name>_log'. Rename this file to ‘OLD<project name>_log'. If there are any other files that have ‘_log’ at the end, rename those as well by adding the word old at the start of the filename In this Temp folder, look for a file that has the same name as your NVivo project but with a .tmp file extension, so it would be '<project name>.tmp.nvp'. This project file will most likely contain your most recent changes to your project. To ensure you still have a backup of this version, make a copy of it first. You should rename this project file to '<project name>.nvp'. You can do this by right clicking on your mouse and selecting the Rename option. Try opening this project file. Windows 7/VISTA Right-click on the Start circle -> Open Windows Explorer Click on Organize -> Folder and Search Options. In the Folder Options dialog, click on the View tab and check the Show hidden files and folders option. Uncheck Hide protected operating system files (recommended) option. Click on Apply -> OK. Click on the Start circle -> Computer. Go to C:\Users\<your username>\AppData\Local\Temp Look for a file that has the same name as your NVivo project but with a _log at the end, so it would be '<project name>_log'. Rename this file to ‘OLD<project name>_log'. If there are any other files that have ‘_log’ at the end, rename those by adding the word old at the start of the filename as well In this Temp folder, look for a file that has the same name as your NVivo project but with a .tmp file extension, so it would be '<project name>.tmp.nvp'. This project file will most likely contain your most recent changes to your project. To ensure you still have a backup of this version, make a copy of it first. You should rename this project file to '<project name>.nvp'. You can do this by right clicking on your mouse and selecting the Rename option. Try opening this project file. In regards to NVivo crash, we will need more information besides the crash log to investigate the cause. Could you submit a support request via http://www.qsrinternational.com/nvivo/contact-us/customer-support & we'll investigate further? Let us know how you go. Kind Regards, Bhupesh
  15. Hi David, Yes, cases can be created manually after the interviews have been coded. Refer to the link below on how to create a case manually: http://help-nv11mac.qsrinternational.com/desktop/procedures/Create_cases_manually.htm#MiniTOCBookMark2 When you create a case automatically by selecting an interview & creating it as a case, entire interview is coded to the specific case. If you do not want to code the entire interview, you can create cases manually and code the relevant data from the interview. I hope this helps. Kind Regards, Bhupesh
×