Editing Directed Research Group: The COVID-19 Information Landscape (Fall 2022)
From CommunityData
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
==The Directed Research Group== | ==The Directed Research Group== | ||
The Covid-19 pandemic has required us to navigate a challenging information landscape. How have our institutions responded, and how have people made sense of the information provided to them? What role have search platforms played in shaping this terrain? | The Covid-19 pandemic has required us to navigate a challenging information landscape. How have our institutions responded, and how have people made sense of the information provided to them? What role have search platforms played in shaping this terrain? | ||
In this Directed Research Group, you'll conduct a content analysis on search engine results collected during the pandemic. This work builds from work conducted as part of a previous DRG in [[Directed_Research_Group:_The_COVID-19_Information_Landscape_(Fall_2020)|Fall 2020]] and [[Directed_Research_Group:_The_COVID-19_Information_Landscape_(Winter_2021)|Winter 2021]]. | In this Directed Research Group, you'll conduct a content analysis on search engine results collected during the pandemic. This work builds from work conducted as part of a previous DRG in [[Directed_Research_Group:_The_COVID-19_Information_Landscape_(Fall_2020)|Fall 2020]] and [[Directed_Research_Group:_The_COVID-19_Information_Landscape_(Winter_2021)|Winter 2021]]. The group will be run for 3-5 excellent students interested in engaging in faculty directed research. The research group will be organized by the Community Data Science Collective by Benjamin Mako Hill and Kaylea Champion and will be conducted for UW course credit. We'll analyze the data you collect and reflect on what it can tell us about our response to the crisis. | ||
The group will be run for 3-5 excellent students interested in engaging in faculty directed research. The research group will be organized by the Community Data Science Collective by Benjamin Mako Hill and Kaylea Champion and will be conducted for UW course credit. We'll analyze the data you collect and reflect on what it can tell us about our response to the crisis. | |||
Prerequisites: Strong reading and writing skills in the English language, a computer you can use during the project, ability to attend team meetings through an online conferencing platform, and a commitment to high-quality results are required. Willingness to work both in a team and independently is required. We strongly prefer candidates with experience in social scientific research methods (such as COM 301). Familiarity with content analysis, R, and Python are all helpful but not required. | Prerequisites: Strong reading and writing skills in the English language, a computer you can use during the project, ability to attend team meetings through an online conferencing platform, and a commitment to high-quality results are required. Willingness to work both in a team and independently is required. We strongly prefer candidates with experience in social scientific research methods (such as COM 301). Familiarity with content analysis, R, and Python are all helpful but not required. | ||
Line 25: | Line 23: | ||
'''Preparation''' | '''Preparation''' | ||
* Read through this wiki page! | * Read through this wiki page! | ||
* Read the pre-print of the paper from the previous DRG | |||
* Read the pre-print of the paper from the previous DRG | |||
* Read this description of content analysis: https://en.wikipedia.org/wiki/Content_analysis | * Read this description of content analysis: https://en.wikipedia.org/wiki/Content_analysis | ||
* Bring your questions! | * Bring your questions! | ||
'''Meeting Agenda''' | '''Meeting Agenda''' | ||
* Introductions | * Introductions | ||
* Scope Review | |||
* Commitments and communication ++ time tracking | * Commitments and communication ++ time tracking | ||
* Content Analysis: What is it? | * Content Analysis: What is it? | ||
* Important Issue: Qualitative versus Quantitative | * Important Issue: Qualitative versus Quantitative | ||
** Toy Example: "What's it been like living in | ** Toy Example: "What's it been like living in Seattle this September?" | ||
* Tour and Overview of the Data | * Tour and Overview of the Data | ||
'''After-Meeting To-Do Items''' | '''After-Meeting To-Do Items''' | ||
* Explore the week 1 sample. | * Explore the week 1 sample. | ||
* Brainstorm | * Brainstorm alternate/new research questions. | ||
* Write up one (or more) of your | * Write up one (or more) of your questions in paragraph form (see example). | ||
====Week 2:==== | ====Week 2:==== | ||
Key | Key Questions: | ||
'''Meeting Agenda''' | '''Meeting Agenda''' | ||
* | * Your sample: what trends did you see? Let's talk about the data! | ||
'''After-Meeting Follow-Up''' | |||
* Read pp. 1-2, 18-34 of Ch 1 of the online version of Neuendorf | |||
'' | * Look back at your memos from the first week and read your colleagues' memos. What did they see that you didn't? Given our collective examination, what feels most important, useful, or surprising about this data? | ||
* | * There are 6 new days of data to look at. You might do a memo per day, or all days in a single memo, or some other approach: organize yourself in a way that works for you. | ||
* | * We'll follow our same memo process from last week: free write, immerse yourself in the data, make notes in multiple passes, synthesize and reflect. Remember Mako's comment that it's ok to treat your memo as a journal: cut and paste, scribble, sketch. | ||
====Week 3:==== | ====Week 3:==== | ||
Line 63: | Line 60: | ||
'''Meeting Agenda''' | '''Meeting Agenda''' | ||
* Research Protocol -- what's coming up next? | * Research Protocol -- what's coming up next? | ||
'''After-Meeting Follow-Up''' | '''After-Meeting Follow-Up''' | ||
====Week 4:==== | ====Week 4:==== | ||
Key Question: Is this working? Can we synthesize these codes into themes? | Key Question: Is this working? Can we synthesize these codes into themes? | ||
'''Meeting Agenda''' | '''Meeting Agenda''' | ||
* | * Open codes discussion: what did you see? | ||
* | * Prep for next phase. | ||
'''After-Meeting Follow-Up''' | '''After-Meeting Follow-Up''' | ||
====Week 5:==== | ====Week 5:==== | ||
Key Question: | Key Question: Can we make a codebook out of what we've seen? | ||
'''Meeting Agenda''' | '''Meeting Agenda''' | ||
* Codebook | * Codebook production discussion | ||
'''After-Meeting Follow-Up''' | '''After-Meeting Follow-Up''' | ||
====Week 6:==== | ====Week 6:==== | ||
Line 98: | Line 86: | ||
* Discuss our agreement levels so far | * Discuss our agreement levels so far | ||
* Update codebook as needed | * Update codebook as needed | ||
'''After-Meeting Follow-Up''' | '''After-Meeting Follow-Up''' | ||
* Read Neuendorff, Ch 2., pp. 36-44, and Ch 3. pp 70-84. Skim the rest of Ch3. | |||
* This is Pilot Round 1, and we are entity coding for agreement | * This is Pilot Round 1, and we are entity coding for agreement | ||
====Week 7:==== | ====Week 7:==== | ||
Line 111: | Line 99: | ||
* Discuss our agreement levels so far | * Discuss our agreement levels so far | ||
* Update codebook as needed | * Update codebook as needed | ||
'''Follow-up Items''' | '''Follow-up Items''' | ||
* Read | * Read Neuendorff p. 139-166. | ||
* This is Pilot Round 2, and we are entity coding for agreement | |||
====Week 8:==== | ====Week 8:==== | ||
Line 122: | Line 109: | ||
'''Follow-Up Items''' | '''Follow-Up Items''' | ||
* Keep Coding | |||
* Read Neuendorff p.169-206 | |||
* If Agreement is sufficiently high, this is when we Begin independent coding | |||
====Week 9==== | ====Week 9==== | ||
Line 130: | Line 120: | ||
'''Follow-Up Items''' | '''Follow-Up Items''' | ||
* Keep Coding | * Keep Coding | ||
* Read Neuendorff p. 221-230, 234-248 (through just the first paragraph) | |||
====Week 10:==== | ====Week 10:==== | ||
'''Complete Writing and Coding Tasks''' | '''Complete Writing and Coding Tasks''' | ||
* Read Neuendorf p. 334-340, 394-403 | |||