I haven't written about it but I'm in data collection for my dissertation, a mixed-method study of teacher perceptions of BYOD. I'll post more on that later, but right now I am learning to use NVivo to code my qualitative data.
Progress this week has been a bit slow as the bug that everyone else was catching finally got to me and laid me out for three days. I even missed two days of work, something that I can't recall doing for illness - ever. (Okay, there was that time back with my skydiving accident,but that was a part time job in college, so maybe it doesn't count.)
I'm up to six interviews as of Monday, five with my target participants. I've looked over the data, and they are still pretty fresh in my mind, although I've been taking better notes. My coding is just the first pass as I make my way to a code book. The goal is to code a few, then consolidate codes, and then recode. I'll ask my co-coder to code a couple of sections so we can check intercoder reliability and clear up the issues that seem clear to me but are just obscure to to others.
I find that I can code a section multiple ways. For example,
"Yeah actually, one project we had in the second six weeks was an English language arts classroom and we were rewriting Antigone and so they were able to Skype with various professionals from [a Shakespeare troupe]. And they talked to them away that they used scripts and stage directions and all this stuff. So then they Skyped. They then wrote the play and then using their device they filmed themselves acting it out. And then we published it onto the Internet."
That ends up with multiple overlapping codes: Lesson example (most of the passage), Tool Use (Skype), Student work (script writing, videoing,Internet publishing, expert collaboration).
Fortunately, NVivo makes this easier.
I'm also about to send out my last round of requests for the surveys.