Here is the second part to my “Why Labels?” post.
After this I will move into constructing another code window for my dissertation analysis. I know the task of building a code window from scratch can be daunting, so watching the process in a “think-aloud” can be helpful. As always, if anyone has some specific things they would like to see, including examples of scripting or linking, I would be happy to give it a try for you!
Thank you to those of you who stopped by my presentation at CEC TED in Indianapolis last week 🙂 Between my dissertation, job hunting, and two back-to-back conferences, my Studiocode blogging has been minimal lately. I was excited to be able to talk about my research using Studiocode with so many people at TED!
Beyond research, something in which special education institutions are particularly interested, is documenting and measuring pre-service teaching practices of students. I am going to be working with a local college to use Studiocode software to make a reflective tool for this purpose. In my discussions with people from other institutions about how I use Studiocode to tag behaviors, one question that has come up is why it is so important to be able to add labels inside codes. Other software can tag things in a video, but not all have the layered label within code ability that I frequently use. In this screencast I show Part 1 of my video on why this is important. I didn’t want to make this video too long, so I will post another video soon. 🙂
Many thanks to the detailed comments from Justin 🙂 I focused on a few of his suggestions to finally show you some open coding with the transcription window.
In my next few posts we will compare this same process using the code window and using the transcription window.
Where does the time go? It seems like I blink my eyes and a week has passed since my last post. I guess that is what happens when most of your day is spent writing your dissertation and applying for jobs (I’m sure most of you don’t miss that!) Anyway, thank you for your tip, Mike, but unfortunately I was not able to get it to work yet. I posted a quick video of me attempting to uncheck the box, but what happens is the program automatically checks it again. What I will probably do is move back to some other features that I haven’t discussed yet while we figure this out. Here is that video and hopefully I can free up a little more time in the near future to dive into this more frequently!
This post is aimed at the experts at Studiocode. I have continued practicing the flexible method of creating time stamps in the transcription window I showed you last time so I could show you a more complete example of how I create codes with labels in the timeline from the transcription window instead of from the code window. The problem is I keep running into small hang-ups with creating the start/end points. I am not sure if anyone else is running into the same problems, so I thought I would make a post about it (this method of coding is still pretty new to me as I am much more fluent with the code window). I am sure it is user error, but I cannot figure out what I am doing wrong. I posted my solution as well, but I am sure there is a better one out there 🙂
**TIP** Some people have mentioned my screencasts are blurry and they cannot see the details of what I am doing. Click to enlarge them to full screen and give it a few moments. They look blurry at first, but they will crisp up to a higher definition after a few seconds of play (sometimes it takes up to 30 seconds). You should be able to read everything on my screen when I make a screencast 🙂
In my last post I described how you can make equal interval time stamps to use a grounded theory approach to analyzing videos for the first time. Much thanks to Mike Willard at Studiocode for his wonderful comment about using a similar method with customizable interval lengths. In case you did not see his comment, I thought I would do a demonstration for you.
You will use some keyboard strokes to enter start and stop times for your transcription window instances rather than setting equal intervals. I created this diagram as a reference for you:
Before I focus on what to do after you have a full transcription window, I wanted to show you how to start a transcription window from scratch. The method I will show you in this screencast aligns with a fully grounded theory approach (it is only the first step…pre- open coding even).
This is an extension of my last post. Thanks, Will, for your comment about creating multiple columns in the transcription window. In this screencast I give a few tips about creation and organization of those new columns so you can begin your coding process without a code window. This is a nice option for researchers who are used to coding videos from transcriptions rather than with video software.
Though you can use the transcription window to completely avoid the code window, I still highly recommend using it as a starting point rather than your primary method of coding. If you only use transcriptions to generate codes, you are losing the video dimension that makes Studiocode so powerful. I see the transcription window as an optional starting point and a wonderful ending point to enhance presentations. I’ll discuss this further in future posts.
I had several requests to talk about the Transcription Window, so this screencast will serve as an introduction to give you some ideas. Specifically I describe how to use the Transcription window to take initial notes about your video clips. This should help you come up with some additional codes for your code window. I will continue to explore the transcription window over the next few posts.