Jump to content

benmeehan

Trainers
  • Content count

    122
  • Joined

  • Last visited

Community Reputation

1 Neutral

About benmeehan

  • Rank
    Advanced Member
  • Birthday 05/20/1957

Contact Methods

  • MSN
    benm@qdatraining.eu
  • Website URL
    http://www.qdatraining.com
  • ICQ
    0
  • Skype
    support@qdatraining.eu

Profile Information

  • Gender
    Male
  • Location
    Ireland
  • Interests
    Training and consultancy in computer aided methodologies for qualitative research covering the Republic of Ireland and Europe
  1. Just in support of Walter's thread, up to now, the only way to report on annotations was to run a text search that pulled all annotations, or annotations with certain characters into a node which effectively gave you a report of all requisite annotations and their related content. This function is now gone! Nor is there a facility to create an NVivo report using the annotations field which renders annotations as ineffective unless you want to view them one by one in collections or view by coding all your sources to a single node and use the find button to see them one-by-one. We recently worked on a project using Interpretive Phenomenological Analysis (IPA). The first phase of this analysis involves reading and initial noting (Smith, 2008). Our client did this by creating over eight hundred annotations. When she went to report this work to her supervisor, we were fortunate that she was still using version 10 so we could retrieve and report. If she had been using version 11 we would have been in trouble. While this facility may not have been used in great numbers, it is still very important in some methods and I'm sure QSR do not wish to be accused of being too quantitative in their thinking about these matters which would be quite ironic The text search tool defaulted to a standard search so one had to change the "search in" option to include annotations. As users had to make a positive decision to change to annotations It's hard to see how removing this option simplified the query as regular users did not have to do anything to exclude annotations. I would dearly like to see this feature returned and I also agree with Walter that linking memos to more than one item or linking items to more than one memo is a facility that we regularly get asked about in our training workshops and in our online training sessions. This user need will not turn in analytics because it has not been available since version 2. Of course see also links are the workaround but they are just that, a workaround. If one looks at the literature going back into the 40s, it describes three key functions of qualitative data analysis: indexing, annotating and memoing. Indexing is coding in today's terms but annotating and memoing primary data is the only means of putting missing context back during the encoding process where one is effectively taking things out of context. Anything QSR can do to elevate these functions will go to the very heart of best practice in qualitative data analytics.
  2. Coding Stripes Show More Than They Should When Working With PDFs

    Hi Marie-Hélène, Ben Meehan here in Ireland (nice gig in Cork recently - well done). My solution is to obviate NVivo when working with PDFs because to date it simply does not work well despite the recent visual improvements in 9.1. Although the PDF looks okay because it appears to retain its formatting, it is only an aesthetic improvement because it still codes as raw text and can’t, for example, code images at all. Thus your problem with tables or columns! Nvivo does not work right with PDFs and for this reason and you will not be thanked by trainees for recommending it for their lit review as another example of user need. Many academic papers include images and tables and these documents need to be coded in a holistic fashion just like any source. This is currently not possible in NVivo. You can’t even use heading styles for auto-coding because you can’t format a PDF after importation. My solution is to use a PDF editor (Smart PDF Pro is very cheap) and convert the PDF to an editable MS Word document and then format and import. Problem solved!  Hope you are keeping well. Warm regards, Ben www.qdatraining.eu
  3. Coding Stripes Show More Than They Should When Working With PDFs

    Hi Marie-Hélène, Ben Meehan here in Ireland (nice gig in Cork recently - well done). My solution is to obviate NVivo when working with PDFs because to date it simply does not work well despite the recent visual improvements in 9.1. Although the PDF looks okay because it appears to retain its formatting, it is only an aesthetic improvement because it still codes as raw text and can’t, for example, code images at all. Thus your problem with tables or columns! Nvivo does not work right with PDFs and for this reason and you will not be thanked by trainees for recommending it for their lit review as another example of user need. Many academic papers include images and tables and these documents need to be coded in a holistic fashion just like any source. This is currently not possible in NVivo. You can’t even use heading styles for auto-coding because you can’t format a PDF after importation. My solution is to use a PDF editor (Smart PDF Pro is very cheap) and convert the PDF to an editable MS Word document and then format and import. Problem solved!  Hope you are keeping well. Warm regards, Ben www.qdatraining.eu
×