The idea of the cycle fits the nature of the N-C-T model, where you have seen that qualitative analysis is cyclical rather than linear. I like Saldaña’s idea of first cycle and second cycle coding (Saldaña, 2013: 8). With more coding, they are likely to change and develop further. The first categories that you develop are likely to be provisional, as they are based on very little coding. Instead of being conducive to your analysis, too many codes prevent further analysis. ![]() This is far better than ten codes that only summarize one data segment each. After merging and reorganizing your codes, you will have a single code that might hold ten quotations in their original form. If you are a splinter, you need to stop coding new data at this point, review your coding and begin to merge your codes. ![]() Coders of this type are referred to as splintersin the literature. If you have noticed a lot of things – let’s say you already have 300 or more codes after coding a few interviews – your codes are probably very descriptive. If you do it much later, it will need more work because then you will have to go through all the documents again to apply newly developed subcategories and recheck all other codings. As soon as you reach this point, when you no longer add new codes (or only a few) and mostly use drag-and-drop coding, it is time to review your coding system. You have roughly described the various elements in the data at this stage. In technical terms, you will drag and drop existing codes from the Code Manager or navigation panel onto the data segments. You have reached a first saturation point. Do whatever feels most natural to you.Īt first, you will generate lots of new codes in time, you will reuse more and more of the codes you already have, and you won’t need to create new ones. If, however, after reading some of your data, you already have some ideas for codes, then go straight ahead and start coding in ATLAS.ti. If you feel that it is essential to read all the data first and write down notes on a piece of paper before you create codes in ATLAS.ti, then this is a suitable way to proceed. Duplicating a code can be a useful option to clean up or modify a code system.Unless you want to code deductively using an existing framework, keep an open mind when you begin to code your data, notice as many things as you can and collect them via coding. The duplicated code is a perfect clone of the original code including color, comment, code-quotation links, code memo links and code-code links. It is also possible to duplicate codes with all its linkages. Deleting it will remove all occurrences in the margin (and from all other contexts in which it was engaged, like networks, groups, etc.). Renaming the code will instantly change all the code links in the margin to reflect the new name. The effect of the operation is local.īy renaming or removing a code from a project, you are affecting every occurrence of the code throughout the entire project. All other occurrences of the same code are untouched. It only affects one coding, i.e., one specific occurrence of the code. Removing a coding in the margin area (i.e., unlinking the code) is like erasing a word in the margin of a paper document with an eraser. Technically speaking, these are links between a quotation represented by a blue bar and the code, represented by its name and icon. In fact, you are seeing the codings for this code. In the margin are, you may see the code appear many times while scrolling through your document. For both operations you must understand, that there is only ONE code, for example 'source of happiness: children' in a given project, even if you applied this code many times. ![]() ![]() Renaming and deleting codes are procedures that seem trivial, but understanding the scope of these operations can be a problem for new users. To select multiple codes, hold down the command key.Ībout Renaming, Deleting and Unlinking Codes In the Project Explorer, the Code Browser, or Code Manager, right-click on a code and select Delete.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |