Jump to content

Fiona Wiltshier

  • Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About Fiona Wiltshier

  • Rank
    Advanced Member

Contact Methods

  • Website URL
  • Twitter

Profile Information

  • Location
    QSRInternational, 651 Doncaster Rd, Doncaster, VIC 3108, Australia
  1. Dear crwalker, From your message it sounds as though Sets would be a good way of organising your data longditudinally, yes. Once these are set up, you could use them to compare across timeframes in a matrix coding query or scope any query to a particular Set to just focus on data from that particular time period. Hope this helps Warm regards, Fiona
  2. Hi Sara, There are a couple of ways of exporting your coding from NVivo that may help: 1. Coding Summary Reports can be created that report on all the coding done from chosen sources to a chosen group of nodes. To do this: a. Go to Tools>Reports>Coding Summary. Then use the drop down menus to choose the specific Sources and Nodes you would like to see the coding for. Click on the option ‘Coded Text and Content Range’, then click OK. b. If this output is what you are looking for, go to the top left hand corner of the screen and click on ‘Export’. There are options to export the report in a number of different formats. 2. You can also choose to export (or print) the coding at specific nodes by selecting the nodes in the Nodes area; this process will create separate files for the coding of each node you export. To do this, select the chosen Nodes then right click on them and choose Export>Export Tree Nodes. You can choose to export the entire content (this will export all the coded data as a webpage) or just the reference view (this will export the Reference View of the node as a text document). I hope one of these helps, Warm regards, Fiona
  3. Dear Charlotte, NVivo should only ask you for a password either when opening a project which you have created a password for, or when importing a password protected document. Once passwords are removed from password protected documents in Word, NVivo should no longer ask for the password when importing the documents into your project. If you are still experiencing the problem, please contact our Helpdesk through our website at http://www.qsrinternational.com/support_contact-support.aspx so that they can have a look at the documents you are working with and investigate to see what is happening for you. Warm regards, Fiona
  4. Hi Nancy, When you see a + sign next to a hierarchical node in NVivo (tree or case) that means that there are child nodes of that node which are currently hidden. If you click on the + sign, this will show you the next level of nodes down. Autocoding works by either gathering together text which has the same heading, or that is in the same paragraph position as other text. It can be extremely useful if you are working with structured data, such as questionnaires or focus groups, allowing you to gather together all the answers to each question in the questionnaires or all the information from each person in the focus groups. You do need to make sure, of course, that you have the appropriate headings in your data for autocoding by heading to work successfully. For a detailed desciption of how this works please see the relevant sections of the NVivo online help under 'Using the Software>Coding'. Hope this helps Warm regards, Fiona
  5. Dear David, For those wanting to migrate from N6 or NVivo 2 to NVivo 7 there is general information provided on the differences between the products accessible through the NVivo 7 product page on our website. For more detailed help, users who have a maintenance agreement or are part of a site license, can contact our customer service team regarding topics such as how to perform actions in NVivo 7 equivalent to those performed in our previous products. They can be contacted directly through completing a Request for Service. We have found that those wanting more intensive assistance transitioning between N6 or NVivo 2 and NVivo 7 have most benefited from consultancy sessions with either ourselves of one of our listed trainers and consultants, where their queries can be specifically answered within the context of their own projects. Warm regards, Fiona
  6. Dear Daniel, We suggest that the option 'Optimized for project size' is used for projects that have over 500 sources in them so I would not recommend that you use this. You may however find that choosing the 'Enable plain text' option, on the same screen as the optimization option, does enhance the performance for you. Hope that helps Warm regards, Fiona
  7. Dear David, For autocoding to work you do need to use the default heading styles though you are able to modify the look of those headings should you need to and it will still recognise them. It does not however recognise heading styles that you create yourself. Hope that helps Warm regards, Fiona
  8. Hi Betsy, To link cases to attributes within NVivo, first go to the Classifications area, make sure the 'Attributes' folder is selected in the Navigation View then right click in the right hand screen (the List View) and choose the option 'New Attribute'. Fill in the appropriate fields to create both your attribute and its values, then click 'OK'. This creates the attribute within your project. To then assign the appropriate values to each case, go to the 'Tools' menu and choose Casebook>Open Casebook, you can then choose the relevant value for each case by using the menus that appear in each cell when you put the cursor over the cell. Hope this helps Warm regards, Fiona
  9. Hi rdhanda, For your query to return the appropriate results you need to ensure that the data from each person is coded at that person's case. By the sounds of it you are almost there in that you have set up the cases and attributes. Your next step would be to go through each focus group and code the responses from each individual at the case for that individual. As you do not have headings in your documents you either have to go through each focus group and code the relevant responses to the cases yourself or you could try using the text search query to help you. Depending on how your transcripts are set up, you may find that doing a search for the name of each person and asking NVivo return the results including the surrounding paragraph gathers the responses for you. If you do use this method you will need to check through once the results are returned to check all the relevant responses have been gathered. Once you have coded each person's responses at their individual case you should find your query works successfully. Hope that helps Warm regards, Fiona
  10. Dear Christine, QSR International has a network of trainers/consultants worldwide who work independently of QSR with a number based in the US. I am sure you will find one of them will be able to help you. You can access the details of those closest to you through the trainers and consultants pages on our website (http://www.qsrinternational.com/support/consultantstrainers/consultants.asp). Many trainers are also prepared to travel or offer distance education via phone or email so please contact any who may be local to your area and they will be happy to discuss your training needs. Hope this helps. Warm regards, Fiona
  11. Hello, If I understand correctly what you are wanting to do, you would first have to create nodes which contain all the respondents answers to each question, i.e. a node containing all respondents answers to question 1, another node containing all respondents answers to question 2 etc.. Once you have these, you could run a matrix using the 'AND' operator with the nodes you have created as both your columns and rows, the results would then show you the number of sources (which in your project sounds as though would equate to the number of individuals) which had been coded to both nodes. To create the nodes and code all the answers to the relevant questions together you can either create the nodes yourself and then code the answers from each person to the relevant nodes as you go through your documents, or, if the documents have been formatted with headings, you could use the 'autocode' feature to do the same thing. For information on autocoding and formatting your documents please see the online help accessed through the Help menu in NVivo. Hope this helps, Warm regards, Fiona
  12. Dear Chenchen, You cannot reorder the node summary report through the reports function, you can though export or print out a list of your nodes as an excel spreadsheet which does format your tree nodes in their hierarchical format. To do this you need to open your tree nodes folder, expand the trees that you would like to be listed (the export function only exports the nodes showing at the time), then right click and choose Export>Export List. You can also choose to print out the list directly through the 'Print' option on the same menu. Hope this helps, Warm regards, Fiona
  13. Dear Lauren, There are numerous queries that you can run through the query tool, if you are running a text search query looking for certain words or phrases, there are a few things to check if you are not getting the results you expect. The first is that you are only entering the exact word or phrase you are looking for into the 'Search For' field and that it is spelt correctly, the second is that the word/phrase is spelt correctly in your sources. If these are both OK, and you haven't changed any of the other options, when you hit 'Run' it should return you a preview of all the occurrences in your project of the word/phrase you have entered. If it does not give you the expected results, it could be that you have changed either what it is looking through (for instance you can choose to ask NVivo just to search through the text, or the annotations, or both (through the 'Search In' field)) or the amount of sources is it searching (you can specify which sources you want NVivo to include through the 'Of' field). For more information on both the text search query and other queries please see the online help which is accessible through the Help menu in NVivo 7. If this does not resolve your problem, please contact our Help Desk directly for further assistance, Warm regards, Fiona
  14. Hi NVivo 7 Trainer, When you click on 'Add To Project' on the Query, the 'General' screen should then appear which allows you to enter a 'Name' for the Query and a 'Description' if needed. The name you enter here will be the name of the query when it is saved in the Queries folder. As Nicole says, as far as the results of your query go, when you choose the option 'Save Results as New Node' as you're doing, the resulting node will, by default, be saved in the 'Results' folder which is under the 'Queries' folder in the 'Queries' area. You do have the option to save the node to another location through the 'Select' button next to the Location field on the 'Query Options' screen but you need to specify this, if you haven't doing this, you should find the node in the 'Results' folder. When you have entered the information you need, you can either run the query which will save both the query and the result, or choose to just save the query by clicking 'OK' if you want to run it later on. NVivo 7 can handle large numbers of documents so there should be no problem running the query on the number of documents you are working with. If your problems persist, I would recommend that you get in touch with our Helpdesk by completing a Request for Service on the QSR website (www.qsrinternational.com) so they can help you resolve this. Hope this helps Warm regards, Fiona
  15. Dear Trudy, The easiest way to sort through your data by characteristics such as gender, age etc is to create attributes for your cases. These are defined by you and can be attached to the relevant cases, allowing you to then sort through the data you have coded using the attribute values. For instance, to sort through your coding to compare the quotes from female and male cases you would first need to set up an attribute (through 'Attributes' in the 'Classifications' area) for 'Gender' with the value 'Male' and 'Female', then, through the 'Casebook' (accessed through the 'Tools' menu), assign the relevant value for each case. Once this is done, you could then run a 'Matrix Coding Query' (accessed through 'Queries') which would allow you to compare what you have coded at a node or nodes by gender. The matrix would probably be the best way to get a broad comparison using one set of nodes and one attribute, or two sets of nodes on their own, if you want to ask more specific questions e.g. what females of a particular age group have said about something, you will need to have a look at the 'Coding Query'. For more information on both Cases and Attributes, and Queries, you may want to have a look at the online help (accessible through the 'Help' menu in NVivo 7). Hope this helps Warm regards, Fiona
  • Create New...