Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About ekociole

  • Rank
    Casual Member
  1. Hi there, I often create matrix coding queries where the rows are autocoded nodes for each value in a column of a dataset and the columns are content nodes. Running a matrix coding query in this way creates a matrix where each row represents a response in the dataset, and each column is a flag variable representing whether or not a response was coded to a given content node. As an example, a typical query has about 150 row nodes and 25 column nodes. The row nodes have 3 "levels": a top-level node under which all mid-level nodes sit; these mid-level nodes contain auto-coded nodes of a p
  2. I wholeheartedly support both of these suggestions and would appreciate hearing what is being done to address this. In my mind this is one of the biggest shortcomings of using NVivo. I work almost exclusively with datasets in NVivo and when I realize that I've imported a dataset to which I need to add a column of additional data or have imported data with errors that need to be addressed, it is so frustrating. I have to make fixes in other other programs, re-import, and lose of all of my coding. It would be so helpful to have the ability to both add data (either rows or columns) and edit d
  • Create New...

Important Information

Privacy Policy