https://padlet.com/umit_aslan/aqm_w3_pairactivity en-us 2021-04-12 19:46:20 UTC 2021-04-14 18:31:48 UTC hello@padlet.com https://padlet.net/icons/png/1f511.png umit_aslan https://padlet.com/umit_aslan/aqm_w3_pairactivity/wish/1409274212 * Pick a color for your group & place your notes nearby.
* You can place a combined note or you can write separate notes individually.
* Check your note to see if anyone left a comment.
* Feel free to add comments to the others' notes (especially questions).]]> 2021-04-12 20:06:30 UTC https://padlet.com/umit_aslan/aqm_w3_pairactivity/wish/1409274212 umit_aslan https://padlet.com/umit_aslan/aqm_w3_pairactivity/wish/1409296545 Before class on 4/14 meet to discuss your coded data excerpts with one another.  Compare your independent coding of each other's data excerpts using the same coding approach.  Discuss:
 

• a) the strengths of the approach given your goal and 
• b) the weaknesses of the approach, and 
• c) challenges you encountered in using the approach with the particular data excerpts. 

Based on your discussion, identify one or two key lessons about data analysis that you took from the exercise to share with the entire class on 4/14. 

]]> 2021-04-12 20:13:43 UTC https://padlet.com/umit_aslan/aqm_w3_pairactivity/wish/1409296545 https://padlet.com/umit_aslan/aqm_w3_pairactivity/wish/1412081315 Strengths - We felt that arriving at similar descriptors helped us feel like we were on to something in a deeper way than arriving at the same code word in say in vivo would. 

Weakness: Potential for disagreement & When you're coding descriptively there's more potential to miss things when you're attending to patterns that you've already seen

Challenges: How big or small  of a phrase do you code and could we be duplicating instances of the code if we break a phrase down into too many minute pieces.

Learnings: This was mentioned in the readings but we truly got to understand how we could easily take 5 or more passes at this data each time looking at it through a different lens and hence capturing something different each time and building on the narrative of the data.

Forrest and Karla

]]> 2021-04-13 14:15:53 UTC https://padlet.com/umit_aslan/aqm_w3_pairactivity/wish/1412081315 daviddeangelis2022 https://padlet.com/umit_aslan/aqm_w3_pairactivity/wish/1414333629 One/Two Key Lessons About Data Analysis:

1) Doing the first pass of codings - no matter which method used (in vivo for one, process for the other) is like a baby first step of developing an iterative analysis and starting point for drawing out the larger concepts

2) Different techniques helped each of us hone in on specific aspects of our interview data to focus on - In Vivo helped David start to make sense of his participants experience through his own words while Process coding helped Leah distinguishing among action, behavior, and the feelings of her participant]]> 2021-04-13 23:52:37 UTC https://padlet.com/umit_aslan/aqm_w3_pairactivity/wish/1414333629 https://padlet.com/umit_aslan/aqm_w3_pairactivity/wish/1414431508 1. As respondents are participating in an interview, they're engaging in live processing/coding/meaning-making (implicitly of our interview protocol)...how is that evident on the page (and code-able by us) and what is not there for us to see--and what does this form of coding-as-tied-to-transcript miss of this? (and/or what approaches to coding engages with between-the-lines, what's implied, the silences loaded with meanings) // qual coding based solely on language fails to take into account what isn't literally on page in words (linguistic coding may be reductive if not combined with other methods)
2. collaboration is key
3. analysis is iterative]]> 2021-04-14 00:34:02 UTC https://padlet.com/umit_aslan/aqm_w3_pairactivity/wish/1414431508 katarzynapomian2025 https://padlet.com/umit_aslan/aqm_w3_pairactivity/wish/1414657412 Key Lessons about data analysis:

1. Need to articulate and clean data more when the data is very foreign to another researcher. Provide coder with more context clues and explanation about the data.

2. The need to brainstorm and try out different conceptual frameworks to see how they inform the research question and how well they fit the data set.


Kasia and Seth

]]> 2021-04-14 01:57:42 UTC https://padlet.com/umit_aslan/aqm_w3_pairactivity/wish/1414657412 https://padlet.com/umit_aslan/aqm_w3_pairactivity/wish/1414913578 Key lessons (still not totally sure):

1. When coding, try to be as comprehensive as possible. For instance, try not to leave any statements or examples uncoded- try to categorize all data and avoid making judgments at this early point in coding about what statements are most relevant.

2. Categorize the data without "over-interpreting" what the interviewee/participant is saying. Try not to make assumptions about the meaning a participant is assigning to something if you are not sure. Ideally, codes should be simple and brief.


Stephanie and Matias]]> 2021-04-14 03:58:37 UTC https://padlet.com/umit_aslan/aqm_w3_pairactivity/wish/1414913578 https://padlet.com/umit_aslan/aqm_w3_pairactivity/wish/1416811685 Key lessons
1. When other people code our data, they could provide novel 'descriptive codes', which opens up new avenues for analysis and collection. This perhaps happen because of the inductive possibilities of facing data without much theoretical baggage.

2. Since all of us were new to data coding, these techniques helped us organise our data in interesting ways. Codes acted as some kind of signposts that could further help us in analyses and collection.

Challenges:
1) As saldana says coding is analyses. So sometimes one is unsure if our code captures the essence or the multiple ways in which the same data can be coded. We guess practice and peer checking is one of the best ways out of this.  ]]> 2021-04-14 14:56:35 UTC https://padlet.com/umit_aslan/aqm_w3_pairactivity/wish/1416811685 https://padlet.com/umit_aslan/aqm_w3_pairactivity/wish/1417928591 2021-04-14 18:24:43 UTC https://padlet.com/umit_aslan/aqm_w3_pairactivity/wish/1417928591