Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About elizabeth.goodfellow

  • Rank
    Casual Member
  1. I've been looking out for similar info on the autocoding process lately and the only description of how the thematic coding works I've been able to find is in the Nvivo manual here: http://help-nv11.qsrinternational.com/desktop/concepts/how_auto_coding_themes_works.htm. This identifies that the process as per text pasted below and then explains a little further. Anyone found any other assessments (peer reviewed or otherwise?) of the autocoding process yet? Having used it myself for a couple of months now it seems to find all the things I would search for myself (and a lot I don't need, but that doesn't matter) and seems to just save doing a lot of frequency and text queries rather than addling loads more smarts or anything like artificial intelligence yet (here's hoping for AI one day...). Cheers, Elizabeth G What makes a theme? The process detects significant noun phrases (for example, real estate development) to identify the most frequently occurring themes. The process collects the themes and counts their mentions across all sources in the set being processed. NVivo actively filters the themes—only the most relevant themes are presented in the results. You can choose which themes to create as nodes at the end of the process. The automated insights process may produce different results in different languages. For example, if you have a translated version of the same source, analyzing the French version in French and the English version in English may produce different result
  2. Just in case anyone else finds this issue. QSR did some fault finding (thanks Heather and Bhupesh) and it turns out there was a special character in the title of one of the items in the reference list of one article/.pdf. The steps in the workaround to correct this at the moment are as per the below. For information, it looked like it was 2 .pdfs (out of about 100 I am working with) that were problematic, but it turned out to only be one as the autocoding stopped when it hit the problem in the one problematic .pdf. Hope this saves some searching and befuddlement for someone else as well. Cheers, Elizabeth G In Adobe Acrobat (Pro?): Open the offending .pdf in adobe acrobat (I have Acrobat Pro version). Export as ms word document. In MS Word: Open the document exported from adobe. Delete the page/s with the special characters (whole reference list removed in this case, just removing the special character was not enough somehow). Export as pdf from ms word and save. Go back to Nvivo and: Import the .pdf back into Nvivo and link to relevant case and case classifications on import. Go to the new .pdf in Internals and select the classification it should belong to using the right-click menu (Reference in my case), Go to the explore tab and view reference classification data sheet and update classification data for new .pdf by copy and pasting entries in classification sheet from old pdf to the new one, Delete memo link from old .pdf that had special character in it, move the old .pdf to junk folder (or delete if you are brave), go to the new pdf (that is minus the reference list) and add memo link to the correct memo. Now the new .pdf will autocode and the meta-data and memos are also attached to it.
  3. Yes, I agree with JSG. I've tried the solutions you've mentioned above Jennifer, and these seem to be set up to do analysis within a source or node, not between sources or nodes. For example, in the data set I am working with, I have autocoded a series of journal articles and it would be helpful to be able to visualise the frequency and intensity of overlap between nodes. When any source is coded for "change" for example, it would be helpful to see how often sources are coded to other nodes. I've tried cluster analysis but haven't got it to quite do this yet. I suppose what I am looking for is correlation or co-occurence of coding between nodes to understand not only the concepts/themes in the data but also the potential relationships between these and other project items...maybe there's a way to connect nodes with relationships and chart/vizualise these? My first thought would be something like a Venn diagram or a variation of the tree-form cluster diagram where each of the branches of the tree is labelled (unless this exists and I just could not find it??), but maybe some sort of frequency or distribution curve of nodes in sources so I can see that most people talk about these issues together, but there are others that talk about different groups of issues. This makes me think a network diagram or explore diagram that combines with cluster analysis and queries any item in the project rather than just cases or nodes or attributes might be more likely to present what JSG and I have in mind (presuming that's similar). I've had a go at using the sociograms to do this briefly but haven't come up with anything workable yet. JSG - what are your thoughts? Hope this helps. Cheers, Elizabeth G
  4. Hi Team, I am using autocoding as the first step in my analysis of a range of literature (.pdf Internals), and running the autocoding both within sources from a journal and then across multiple journals to check the consistency of coding and variation between journals. I have 4 journals, each with a number of articles (ranging from 4 to 47 per journal) which totals 100 internals for the analysis across all the journals. All records were exported from Endnote as .xml and then imported to Nvivo through the endnote import functionality, and classified and coded accordingly. I have run the autocoding on the items from 3 of the journals without any issue. With the last journal (Journal of Organisational Change Management), I am getting the following error if I try to autocode all 38 items in the list for this journal: "Unable to identify themes - An error occurred when coding your sources. Please try again.". Having tried several times, it appears there is an issue with one or two of the .pdfs and that Nvivo cannot read and therefore code them, so the whole autocoding stops. I've run the autocoding on all but the items except for the offending 2, and then the coding will complete, so it appears to be an issue with these .pdfs. So in trying to diagnose why this is happening I have: 1. checked the .pdfs are not secure/locked etc in adobe acrobat - correct, no security is applied to them. 2. opened the .pdfs in Nvivo and tried to manually code sections of the text in these documents - yes this is possible and the coding appears in the coding stripes immediately.3. tried to run the autocoding from within the .pdf/internal by opening it, right-click and selecting autocode and then choosing the use existing coding option and selecting the codes created when the autocoding succeeded when these two internals were excluded from the set - the autocoding still fails (all codes in the set come up under "no coding" in the results of analysis list) and then I get an error that says "The autocoding wizard was unable to code the selected source(s) based on existing coding patterns. Make sure that your sources contain text and select nodes that already contain sufficient content coding references to determine new coding". 4. to check if in Nvivo the .pdf are text sources I copied and pasted text from the .pdf internal into my project memo - successful, copy and paste worked, the section appeared correctly in the memo and so would seem to be text. 5. run the autocode on one of the offending sources, using the existing codes from the autocoding of the remainder of the set from that journal, but this time only with the 3 of the 5 top level nodes (which have 160-760 references each coded to them) and none of the child nodes (which have many with less than 10 references coded to them) - coding failed and got same error as in step 4 above. 6. converted the .pdfs to .docx and imported as internals and then repeated 5. above - same result, no coding and same error. 7. ran autocode on entire .pdf data set (ie across all journal items together) - same "unable to identify themes" error resulted. 8. ran autocode on entire .pdf data set less the two offending sources - autocodes fine when the offending two sources are excluded. So by now, I am about out of ideas as to what is going on here, especially because the same happened in the .pdf and the .docx. Appreciate suggestions on what might be wrong with these two .pdfs/internals and what to do about it so I can do the analysis on my full data set. Cheers, Elizabeth G
  5. Hi dBane, Actually, the fact that there is double the entries probably tells you the import has worked correctly. When you import from Endnote (EN) Nvivo creates an Internal OR external AND a memo based on an individual EN record. Nvivo then adds the bibliographic data to all the source items created as classification attributes - so you don't actually see a reference record or source in Nvivo that looks the same as what it does in Endnote unless you look at the source classification sheet for the Reference source type. This means that as Heather said above, if you have abstract/keywords etc in the EN data, then you should end up with at least two Nvivo sources for each EN record. This also means that tracking the numbers exported/imported etc is important to ensure your data remains complete. The easy way to check the match is go to the Export tab, open the Source Classification Sheet for reference, and right-click on the first column in the classification sheet. If you change the 'source classification name format' to hierarchical instead of name, then you'll see for each title in the list, there'll be an internal or external and memo. Scan through the list to make sure it is consistent all the way through to make sure everything has imported correctly. I am doing a systematic literature review using Nvivo and I have found that I need to carefully track the completeness of my data from search results, to downloaded articles, to import to endnote, to import to Nvivo, and then within Nvivo as well. I have a spreadsheet I use to track this and you can use it as a start or as a basis to make your own, there's a sample copy here: https://drive.google.com/file/d/0B9rqEM5EQcqDSHBfbGh5QVRXOUE/view?usp=sharing. Hope this helps - this reference management stuff looks quick and easy but it still seems to take me quite a bit of time to get my head around how it works and to maintain the quality control of the data. Cheers, Elizabeth G
  6. Thanks Andrew, this is a reasonable work around though quite time consuming and takes a bit of practice to get consistently right. I've found for small numbers of updated references it's easier to import a new internal (.pdf), classify it as a reference and link it to the relevant memo and external manually. Cheers, Elizabeth G
  7. A quick update here. I have discovered that you can at least see the record number in Nvivo if you import references using the Author (Year) format for the references (not the Title format), which results in references with attached internals etc that look like what's in the attachment . This inclusion of the EN record number in the title is handy for checking the consistency of the data imported and distinguishing easily between sources by the same author/s. This still does not result in a classification attribute of EN record number. I've also tried including the EN record number as data in a custom field in an output style in endnote but for some reason the record number data still does not appear in the classification sheet even though other custom field data does. Odd. What this means though is if I/you want to link other items to endnote record numbers, there still is not a direct way, so I cannot for example create a case list of individual authors and link these to sources via EN record numbers easily...as far as I know :-). I'm still working on this occassionally so will post updates when I have more info to share. Cheers, Elizabeth G
  8. Hi Team, My second question for today is also about endnote - my bibliographic records are central to the design of my systematic literature review, which means that I need to set up each endnote reference as an individual case node in Nvivo and code/link other items about the same article to that case. This is partly because I need to export multiple versions of my data from Endnote to Nvivo to separate out the abstracts from other 'notes' and to identify individual authors etc. So my question is - where can I find the Endnote record number in Nvivo after import so that I can use it to create unique cases and code/auto-code to cases? I have checked the .txt/xls and .xml files that I can export from endnote and I can see that the record number is included in the export from endnote when the right filters are used for the export, but the record number seems to disappear in Nvivo post-import (see attached screenshot). Mysterious. Appreciate it if anyone can help me find these as I am sure I can make a work-around but it would be better to have a more reliable-repeatable process. Cheers, Elizabeth G
  9. Hi Team, I have many references with both endnote bibliographic data and associated .pdfs. I have been trying to import both together through the Data/FromOtherSources/Endnote wizard, and I think I am following the instructions/set up correctly from here: http://help-nv11.qsrinternational.com/desktop/procedures/exchange_data_between_nvivo_and_reference_management_tools.htm?rhsearch=endnote&rhsyns=%20#Understand_how_files_associated_with_references_are_handled and here: http://help-nv11.qsrinternational.com/desktop/concepts/about_document_and_pdf_sources.htm. I have also checked the Endnote file location so these should be accessible but there's a possibility this is still not right. It is important to my research that the attributes from the bibliographic data are attached to the external reference as well as the pdf so I can see how the issues and arguments in the field have developed over time. Advice appreciated, I think/hope this is something simple I've missed as it looks like this is what the wizard is set up to do. Cheers, Elizabeth G P1 EN w Att Test.xml
  • Create New...