{"id":17876,"date":"2014-07-23T13:12:38","date_gmt":"2014-07-23T12:12:38","guid":{"rendered":"https:\/\/www.maxqda.de\/?p=17876"},"modified":"2024-06-14T08:53:33","modified_gmt":"2024-06-14T07:53:33","slug":"boston-youth-justice-forschungsprojekt-von-der-fragestellung-zu-kodierungen","status":"publish","type":"post","link":"https:\/\/www.maxqda.com\/de\/blogpost\/boston-youth-justice-forschungsprojekt-von-der-fragestellung-zu-kodierungen","title":{"rendered":"Boston youth justice Forschungsprojekt: Erstellung eines Codesystems"},"content":{"rendered":"

Matthew Poirier geh\u00f6rt zum Boston Youth Justice Forschungsteam<\/a>. Im heutigen Beitrag erkl\u00e4rt er, wie das Forschungsteam auf der Grundlage ihrer Fragestellungen ein Codesystem f\u00fcr die Analyse erstellte.<\/p>\r\n

<\/p>\r\n

Moving from Research Questions to Codes<\/h2>\r\n
<\/figure>\r\n

by Matthew Poirier<\/em><\/p>\r\n

<\/figure>\r\n

The process of moving from research questions to codes was a deliberative process that occurred in our class setting. When Professor Warren introduced the concept of coding to us, he encouraged us to think about the process as one that was iterative in nature, and realize that our codes would evolve. I think this was to encourage us to realize that codes could and would change as we learned more about our data. As a project team, we had developed our research questions, and created interview protocols looking for data on those research questions. Here, it was important to look at both the research questions and some initial readings of the transcripts themselves to seek to define our codes as part of our process.<\/p>\r\n

\"Boston<\/figure>\r\n

Members of the Research Team<\/i><\/p>\r\n

Coding inspired by interview questions<\/h3>\r\n

By way of example, we really wanted to understand the nature of youth power in Boston during the early 2000s, and so we asked, \u201cHow did youth emerge as leaders and build power?\u201d A direct interview question that resulted from this research question was: \u201cTell me more about your role in the [youth justice] movement.\u201d And so it was natural that one of the codes we developed was called \u201crole in movement\u201d, where we looked at how youth alumni defined their own roles in the movement. We wanted to know if the youth saw themselves as leading the moments that our research partners viewed as significant.<\/p>\r\n

A further research question we developed for this project was to examine how this time impacted the youth who participated. This was a clear part of our research partners\u2019 desire to do this research, and it lead directly to the follow up probe to the above interview question where we asked \u201cDid your participation in the movement change you in some way?\u201d This naturally brought about the code of \u201cYouth Impact\u201d, which we defined as how the movement impacted youth personally through participation in the movement. It\u2019s where we captured some of the most powerful statements of the youth movement beyond the time to a real powerful impact on them as adults and the paths that they chose. We could see the code in action, pulling those key pieces of data from the interview. It was an exciting development, and one that we as a research team could really see across the interviews, and one that we felt really worthy of pursuit.<\/p>\r\n

Refining the code system<\/h3>\r\n

The research questions really were guide posts as we moved through developing the codes. A careful reading and re-reading of select interview transcripts gave us the ability to refine the codes, and ensured that the code system we developed reflected the interview questions we were interested in pursuing. Feeding the codes back into the interviews allowed us to see that our research questions were providing a set of reliable codes. By keeping the research questions ever present, and by developing a coding system largely derived from our research questions, we really strived towards our own form of internal validity.<\/p>\r\n

We all felt that the time and effort that we spent on this part of the project was well spent, and really allowed our research project to open up for us. MAXQDA facilitated this process by allowing us to see our codes in action, and we used MAXQDA to test code several interviews. Re-reading the test interviews, we refined our coding system, completing that iterative coding path that Professor Warren had encouraged us to use. It was a distinct advantage of the approach we learned within this project, and one for which that MAXQDA was enormously beneficial.<\/p>\r\n

Weitere Artikel zum Thema<\/h3>\r\n