1. Kate West University of Washington October 24, 2012
Atlas.ti Workshop
Kate West
University of Washington
October 24, 2012

2. Learning Objectives
To understand the fundamentals of qualitative analysis, so you know why you’re doing this whole Atlas.ti thing in the first place.
To identify the basic coding functions in Atlas.ti that correspond to the analytic steps covered in part 1.
To apply basic coding functions in Atlas.ti to a sample transcript
References to fill in the details are available.

3. Part 1: Introduction to Qualitative Analysis

4. Qualitative Research
Research that involves analyzing and interpreting texts in order to discover meaningful patterns descriptive of a particular phenomenon (Auerbach and Silverstein 2003).

5. Definitions
Grounded theory: developing hypotheses based on what your data tells you (Strauss and Corbin 1994…). Builds higher and higher order categories from bits of text to develop a theoretical narrative.
Coding: Assigning labels to textual data to help organize into categories and themes.
Open coding– I prefer by hand
Emergent/axial coding– I prefer using software

6. Steps, in very, very brief
DISCLAIMER: There are many ways to conduct qualitative analysis.
Reading all transcripts, memoing about first impressions, hunches, questions.
Open coding: line by line, noting all identifiable bits of text, for 1-3 transcripts or so…by hand.
E.g. “This recipe originally called for beef, but I started using elk, and no one knows the difference, not even my kids, and they are very picky eaters! I serve this over hot cooked rice or wide egg noodles.”
Recipe beef
Elk no one knows
Kids
Picky eaters
Rice egg noodles

7. Steps…
Developing emergent codes: Categorize open codes by semantic relationships.
E.g. Cats, dogs, rats, iguanas EMERGENT CODES:
ARE TYPES OF pets Pets Sickness, no transportation, no childcare
ARE CAUSES OF missing work. Missing work Stress relief, flexibility, strength, nice shoulders
ARE REASONS FOR doing yoga. Doing yoga

8. Steps…
4. Drafting codebook: Determine which emergent codes are relevant to your research concern. Define them with statement, examples, inclusion and exclusion criteria (MacQueen et al. 1998).
Load into Atlas.ti code manager.
SAMPLE
Code abbreviation: MissWork
Code name: Missing Work
Definition: mentions of incidents of missing work with reasons for doing so.
Examples: Sickness, no transportation, no childcare
Notes on when to use: Do not use code for mentions of vacations, etc. Use code “travel” instead.

9. Part 2: Using Atlas.ti Qualitative Analysis Software
Spoiler alert: You still have to do the work.

10. Atlas Functions to Cover
Setting up your workspace; preferences, views, managers, saving, backing up
Launching and saving a new HU; loading primary documents
Entering the codebook/creating new codes; Sorting codes through naming; commenting
Creating memos
Many ways to do each function, I will only show 1-2 for each; save you craziness.
View file extensions; don’t delete .log files, ok to delete .lok files.

11. More Steps…
5. Coding all transcripts using emergent codes… in Atlas.ti. -New open codes as necessary. -Do it again.
6. Developing themes by higher order categories, families, etc. Use Atlas outputs for examining specific codes; Network drawing can be helpful- either in Atlas or by hand.
7. Creating theoretical narrative: the story you will tell. Test it with textual data.

12. More Atlas Functions to Cover
Assigning codes to text: increasing/decreasing quote sizes, unlinking vs. deleting
Team-specific considerations: Project administrator, naming conventions, copy bundles, merging HUs, version management, calculating kappas; Team libraries (add not assign)
Creating outputs: different types, uses of each
Network tool
Atlas’s best feature
Changes in the new version: no need to keep P docs in same order when merging HUs;
Uploading doc in old version; now can upload docx, etc.
Using PDFs
Do not modify a doc once it’s uploaded because it screws with your coding; edit only within Atlas; if added to the library (managed file) then you can; but especially in team-based coding, can’t edit doc unless it’s in a shared library space- or else you get 2 versions that can’t be merged. Best just not to.
Atlas 7 can not be read by older versions, but older versions can be read by Atlas 7. – upward but not downward compatible.
New copy bundle: atlcb  all docs added to the target computer’s library.
Team library (p.33 What’s New manual): DOCUMENTS / DATA SOURCE MANAGEMENT / OPEN LIBRARY MANAGER.
In the Library Manager, select EXTRAS / MANAGE LIBRARY LOCATION.
--Send new Master HU out; all team members assign library: DOCUMENTS / DATA SOURCE MANAGEMENT / OPEN LIBRARY MANAGER.
In the Library Manager, select EXTRAS / SET LIBRARY LOCATION.
--Use the one the admin told you to use. Name your own version of the Master HU and save it anywhere.
Work flow diagram on p. 35

13. Honorable Mentions
Families/Supercodes
Hyperlinks
Building queries

14. Review Emergent codes Emergent codes Emergent codes Emergent codes
THEORETICAL NARRATIVE
THEME
THEME
Emergent codes
Emergent codes
Emergent codes
Emergent codes
-Here I present a simplified overview of one method of qualitative analysis, which I used, Grounded Theory.
-Small boxes represent text bits from interview transcripts. These become “codes,” which are used to develop categories based on repeated ideas. These repeated ideas (emergent codes) are grouped into higher order categories, and then more higher order categories, eventually getting to categories called “themes” (bigger boxes).
-Tie your themes together with a theoretical narrative, or metaphor.
-Aided by qualitative analysis software program.
TEXT
TEXT
TEXT
TEXT
TEXT
TEXT
TEXT
TEXT

15. Notes
1: Keep memos and comments on everything to keep track of themes and ideas you have as you analyze.
2: This is a long, time-consuming, but kinda fun iterative process.
Questions?