Respondents who evaluated the game negatively did not mention any benefits (green bars). You can see very quickly that there is a difference. In the second image, the data have been filtered a) by respondents who evaluated the game positively and b) by respondents who evaluated the game negatively. In the first image below, you see the distribution of three categories: benefits, downsides and features of the computer game Minecraft across all documents. Which topics were mentioned more or less frequently, by whom, is there a difference between different groups of respondents? How are the topics distributed? Code Distribution across Documents Within the bar you can see how the codes are distributed in the document.Īfter you've encoded the data, a look at the code distribution gives you a feel for the data. In the Code Manager each bar stands for a document. The higher the bar, the more often the code was used. In the document manager you will see a bar for each code. Another option is to right-click on a code and select the Edit Comment option from the context menu, or to click on the Edit Comment button in the ribbon of the contextual Code tab.Code distributions are displayed in the Document Manager and in the Code Manager in the form of bar charts. In the margin area, you can double-click on a code to open the comment editor. In the Code Manager is open, you can use the comment field at the bottom of the window. There are several ways to write a code comment. ![]() You can also use it to write up summaries of all segments coded with this code and your interpretation about it. If you work inductively, you can use code comments to write down first ideas of how you want to apply this code. If you work in teams, you may also want to add a coding rule, or an example quote. The most common usage is to use them for a code definition. Writing Code CommentsĬode comments can be used for various types of purposes. This option is also available in the Network Editor. The clone has the same name as the original code plus a consecutive number, i.e. To duplicate a code, open the Code Manager, select one or more codes, right-click and select the Duplicate Code(s) option from the context menu, or select the Duplicate Code(s) button in the ribbon. Duplicating a code can be a useful option to clean up or modify a code system. 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. unlinking the code) is like erasing a word in the margin of a paper document with an eraser. Removing a coding in the margin area (i.e. 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. About Renaming, Deleting and Unlinking Codes In the Code Manager, you can also click on the Delete button in the ribbon. ![]() In the Project Explorer, the Code Browser, or Code Manager, right-click on a code and select the Delete option.
0 Comments
Leave a Reply. |