Search the Community
Showing results for tags 'attributes'.
Beginner here. I am looking for guidance on visualizing change over time among documents. I have a series of documents over a 30-year period, and I'm trying trace changes in the proportion of different codes over time. I need to be able to apply dates to files, and then summarize those proportions for different years. Any guidance on how to do this? Elsewhere I've seen people using "attributes" for this purpose but I can't figure out how to do that consistently. Instructions or pointing toward existing documents/trainings on this would be helpful. I'm using NVIVO 1.2.
Please see below as I've not yet received a response. Jennimh Casual Member Jennimh Members 0 6 posts Report post Posted July 31 Hi, I have just got the new NVivo 12 and am trying to use the new types of queries. Am I correct in saying that you can only use two attributes for a crosstab query? I have a number of documents which each have 4 attributes. Each attribute has a choice of one,two,or three values. I have then coded some material in each of these documents. What I want to produce is something that looks
This seems like it should be a straight forward problem... When I upload my survey data NVivo will not add all of the closed questions (those I assigned in set up process/wizard) as attributes. I need to assign more columns to be attributes and am struggling to work out how. One assumption I have made is that all closed questions will be made as attributes and appear in list under case classifications - is this true? Questions: Why has NVivo not made all closed questions into attributes? Why have some closed questions and not others been made into attributes? How do
Hi everyone, Our project involves qualitative coding of 6 open-ended questions at the end of a long survey of quantitative fields. There are >200 columns of quantitative data in the spreadsheet that we want to keep for attributes (e.g. demographic info) and to crosstab by later on in matrices. There are hundreds of observations in this dataset, which was imported from an Excel spreadsheet. Trying to code the open-response fields in this large spreadsheet is very laggy and we're looking for better solutions. Would it be possible to keep the quantitative attributes in a separate imp