Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About jonathan_schultz

  • Rank
    Casual Member
  1. OK well no help from QSR but I figured it out by myself and maybe this will be of assistance to other users. First, the silent rejection was caused by not having a full hierarchical name in my classification sheet. Yes, NVivo for Mac does tell you somewhere that you need full hierarchical names, but strangely enough it also sometimes accepts less than full hierarchical names which makes it more confusing. Also some feedback to tell the user that lines from the classification sheets are being ignored because the source/node was not matched with an existing source/node and the 'Create new source/node' checkbox was unclicked would be helpful. Second, the 'Import classification sheet error' was because I had used zeroes and ones to code boolean attributes, just as NVivo does when you export a classification sheet. Changing zero to 'No' and one to 'Yes' made it work. This is really inexcusable, firstly in not accepting as input a file that it creates as output, and secondly in providing no meaningful error report for the user.
  2. Below is the detailed log message. If there is some meaningful information in there I cannot find it. 2014/12/07 17:06:06:825 Error for operation: <NVIImportClassificationOperation 0x600000942aa0> progress: 100; status: "Import Classification Sheet Error"; file: /Users/jschultz/Documents/Classification Assignments-Person.txt (6 KB) Error Domain=com.qsrinternational.error.client.project Code=323 "Import Classification Sheet Error" UserInfo=0x6000004e0c00 {NSLocalizedFailureReason=Import classification failed, NSLocalizedDescription=Import Classification Sheet Error, NSLocalizedRecoverySuggestion=Error importing “Classification Assignments-Person”. Reason: Failed to import classification sheet. , NSFilePath=/Users/jschultz/Documents/Classification Assignments-Person.txt, NSUnderlyingError=0x600001c523c0 "The operation couldn’t be completed. (ImportClassificationMatrix error 1.)"} [{ NSFilePath = "/Users/jschultz/Documents/Classification Assignments-Person.txt"; NSLocalizedDescription = "Import Classification Sheet Error"; NSLocalizedFailureReason = "Import classification failed"; NSLocalizedRecoverySuggestion = "Error importing \U201cClassification Assignments-Person\U201d. Reason: Failed to import classification sheet.\n"; NSUnderlyingError = "Error Domain=ImportClassificationMatrix Code=1 \"The operation couldn’t be completed. (ImportClassificationMatrix error 1.)\""; }]
  3. And, seriously, what is the user to make of a message like this? Import Classification Sheet Error: Error importing “Classification Assignments-Person”. Reason: Failed to import classification sheet.
  4. I'm trying to import a simple classification sheet that I created in Excel, but getting no response. I've tried txt, csv, utf-8, utf-16 - nothing seems to make any difference. I've also checked the log files - nothing there either. How about providing some meaningful feedback to the user instead of silently doing nothing? And while we're at it, automatically detecting file encoding, field delimiters, etc., as has been standard practice for decades? And in the meantime do you have any suggestions for how to make this work?
  5. Generally speaking, are there any log files or ways to enable more verbose logging that could provide more detailed information if the same thing happened again?
  6. Well how about that? I went to test whether check whether there were unusual characters in the filename. NVivo refused to open the project and told me I needed to reboot the computer. I did that and now it imports the files without complaining. Thanks for your help anyway.
  7. I have just begun using NVivo for Mac for the first time. After loading a few sources into a fresh project, I quickly found that some of my sources won't load. The error message states: Import Error: Error importing “<filename>”. Reason: The file cannot be converted to a supported format in NVivo. Just for fun I tried importing the same file into NVivo for Windows and it worked perfectly. I'm not at liberty to attach the source file in question, but it is a transcript of an interview and does not contain anything that is obviously suspicious. Can anyone suggest a next step? Thanks, Jonathan
  8. Why is it that when I try to export the classification sheet from my sources, the option is always greyed out? Thanks, Jonathan
  9. Hello, I am trying to work out if it is possible to have an extract or report present source attributes via a Node view. The reason for this is that our sources include interviews that have as attributes data such as the sex, age, social class and ethnic group of the interviewee. When analysing the coding of those interviews we need to be able to see those attributes alongside the coded interview extracts for a given collection of nodes. So far I can't see any way of doing this, One work-around might be to incorporate those attributes in the Description field of the sources, as the description is available from Node view extracts and reports. However, this constitutes extra work that appears to me to be something that NVivo should be able to handle automatically. Any help would be greatly appreciated. Regards, Jonathan
  • Create New...