Taylor, Lewins, and Gibbs (2005) discuss the debate over using CAQDAS packages for data analysis. In their article, they discuss the many concerns over using digital tools, one of which is the worry that using a digital tool may not allow the researcher to stay "close to the data." The authors define this as the physical handling of transcripts to make their discussion clear.
This discussion always interests me, and the way Taylor, Lewins, and Gibbs discuss the issue of closeness made me think about what digital tools generally and CAQDAS packages specifically afford in terms of allowing a researcher to get close to the data. The authors explain that one may move away from the data by not handing the transcripts and hand coding, but they also discuss that digital tools afford the opportunity to add new codes in an easy way. Tools also allow a researcher to look at their codes in the aggregate and make links between codes and excerpts in a fairly simple and streamlined way. This could be a very laborious task if one was hand coding, and there may be inaccuracies because it may be difficult to see all of the excerpts with the same code.
Furthermore, CAQDAS packages allow for the manipulation and refinements of codes. Because the researcher can see the codes and the excerpts to which they are attached at a glance, they can look for consistencies in language and make sure that their word choice connotes the meaning they intend. This may be particularly useful for revealing underlying biases and assumptions.
It seems to me that CAQDAS packages actually allow the researcher to be more intimate with their data because they allow the researcher to code in a non-linear fashion if they so choose, and then visualize the data in accessible ways that reveal consistency across coding and may focus analysis.
Yes! I believe CAQDAS creates opportunity for closeness. My belief is that when CAQDAS is positioned as something that creates distance, there is a fundamental misunderstanding of how to use the package and/or lack of experience with CAQDAS packages. For instance, creating a synchronized transcript is something that has radically changed how I have come to know my data. I'm continually working with NOT just the written transcript, but the audio file as well. There is a closeness that ensues. Herein, from my perspective, lies one of the key (powerful) attributes of CAQDAS. :)
ReplyDelete