# Week 9 ## Content Analysis and NVivo Z616: Comic Books and Their Readers --- ## Week 9 in context This week we move from automated text analysis to **hands-on coding of fan mail as interpretation**. Today you will: - apply a shared coding scheme - use NVivo at a basic level - compare coding decisions - revise the coding scheme as a class - reflect on how coded texts become data --- ## Learning goals By the end of class, you should be able to: - explain qualitative coding as an interpretive method - apply a predefined coding scheme to fan letters - use NVivo to code and organize textual data - compare coding decisions across readers - evaluate and revise coding categories - recognize how coded texts can become structured datasets --- ## Our schedule today <!-- - 12:45–1:00 opening and framing - 1:00–1:20 codebook and category distinctions - 1:20–1:45 guided demo - 1:45–2:00 NVivo setup - 2:00–2:35 coding activity - 2:35–2:50 break - 2:50–3:10 comparison and discussion - 3:10–3:20 codebook revision - 3:20–3:25 wrap-up --> - opening and framing - codebook and category distinctions - guided demo - NVivo setup - coding activity - break - comparison and discussion - codebook revision - wrap-up --- ## What is coding? Coding is the practice of marking meaningful passages in a text with labels. A code can mark: - evaluation - emotion - identity - participation - requests or demands - personal experience - social concerns Coding is not neutral. It is an **interpretive act**. --- ## A key principle A passage can have **more than one code**. That is often where the best discussion begins. Examples: - praise + emotional response - criticism + request - fan identity + participation - creator/editorial awareness + social context --- ## Our corpus today Selected letters from **Amazing Spider-Man** letter columns. They give us a strong mix of: - praise and fandom - campus readership - parent-reader perspective - drug discourse and social relevance - anti-Code praise - proposals for future stories - editorial replies --- ## Starter codebook - Praise - Criticism - Emotional Response - Character Discussion - Plot and Story Discussion - Creator and Editorial Awareness - Fan Identity - Participation and Community - Request or Suggestion - Personal Connection and Social Context --- ## Distinctions to watch ### Fan Identity vs Participation / Community - **Fan Identity**: how the writer presents themself - **Participation / Community**: fandom as social or collective action ### Character Discussion vs Plot / Story Discussion - **Character**: focus on people/figures/relationships - **Plot**: focus on events, direction, continuity, outcomes ### Personal Connection vs Social Context - **Personal Connection**: links to the writer's life - **Social Context**: links to broader public issues --- ## What counts as a strong coded passage? A passage is worth coding when it does interpretive work. Look for places where the writer: - evaluates - reacts emotionally - identifies as a certain kind of reader - connects comics to life or society - asks Marvel to do something - reflects on what comics should be for --- ## Demo letter Steven Pearlman on **Amazing Spider-Man #121** What we will notice: - congratulations + anger - strong fan identity - emotional investment in Gwen Stacy - evaluation of a specific issue - direct appeal to Gerry Conway - readers imagined as a collective force --- ## Demo passage 1 > "I have just finished Spider-Man #121 and I am unable to contain my congratulations and anger." Possible codes: - Emotional Response - Praise - Criticism --- ## Demo passage 2 > "O.K., so I've read every Spider-Man mag" Possible code: - Fan Identity Question: Does this also suggest participation, or is Fan Identity the better fit? --- ## Demo passage 3 > "But why pick on Gwen???" Possible codes: - Character Discussion - Emotional Response --- ## Demo passage 4 > "When Gwen was first introduced into Peter's life, it appeared as if Marvel did have a heart, but now I have my doubts." Possible codes: - Character Discussion - Criticism - Creator / Editorial Awareness --- ## Demo passage 5 > "All I can ask is that you, Mr. Conway, create one HECKUVA story and return the only good thing that Marvel has ever given..." Possible codes: - Request / Suggestion - Creator / Editorial Awareness - Character Discussion - Plot / Story Discussion --- ## Demo passage 6 > "...us college guys will just have to burn you in effigy, Mr. Conway..." Possible codes: - Participation / Community - Fan Identity - Emotional Response - Request / Suggestion --- ## NVivo setup 1. Open NVivo 2. Create a new project 3. Import the letter files 4. Open a letter 5. Highlight a passage 6. Code to a new or existing node 7. Reuse nodes consistently 8. Review coded passages if needed Keep it simple today. --- ## Your task In pairs or small groups: - read and code 2–4 letters - code at least 10 passages total - use at least 5 different codes - identify 1 difficult passage - identify 1 code that needs revision A single passage may receive multiple codes. --- ## Letters in play Examples from today's set include: - ASM #42: campus fandom, Marvel identity, community - ASM #23: parent-reader perspective, educational value, race and bigotry - ASM #97: drugs, public responsibility, Marvel as influence - ASM #101: anti-Code praise, educational mission, social intervention - Vietnam proposal letter: reader suggestion, politics, future story direction --- ## Questions to ask while coding - Why this code? - Why not another code? - Is this passage evaluative, emotional, persuasive, or self-presentational? - Is the writer talking about a character, a plot event, Marvel, or society? - Does this passage need two or more codes? --- ## What to watch for - fan identity and self-presentation - readers trying to influence Marvel - emotional investment in characters and stories - comics as education or social intervention - editorial replies shaping the exchange - disagreement over what comics should do --- # Break ## 2:35–2:50 Come back ready to compare coding decisions. --- ## Compare your coding As a class, we will sort examples into three buckets: - codes that worked well - difficult passages - codes that need revision --- ## Discussion questions - Which codes appeared most often? - Which passages produced disagreement? - Which definitions were too broad or too narrow? - Which new code, if any, did you want? - What do these letters suggest about comics readers and participatory culture? --- ## Codebook revision As a class, revise 2–3 categories. Most likely trouble spots: - Fan Identity vs Participation / Community - Character Discussion vs Plot / Story Discussion - Personal Connection / Social Context vs Creator / Editorial Awareness --- ## Exit reflection Before you leave, be ready to answer: 1. What pattern did you notice? 2. What passage was hardest to code? 3. Which code should be revised? 4. How does coding differ from computational text analysis? --- ## Big takeaway Coding helps us move from: **close reading** to **systematic interpretation** to **structured data** Interpretation does not disappear. It becomes visible.