Jump to content

alexquse

Members
  • Content count

    73
  • Joined

  • Last visited

Community Reputation

2 Neutral

About alexquse

  • Rank
    Advanced Member

Profile Information

  • Gender
    Male
  • Location
    Switzerland
  1. My question is simple: does nvivo 9 work with windows 10?
  2. I notice an annoying problem with a big project of 1700 items: shifts appear in the coding! At first I thought it was accident, and I corrected them. But I'm beginning to realize that it is almost systematic. I do not understand what occasioned them, but it's pretty scary to see my coding work deteriorate ... Is there a solution? Uploaded with ImageShack.us
  3. alexquse

    Bug in nvivo 9

    I can't reproduce the problem anymore. I 've sent you anyway the errors log files. Thank you for reactivity Alex
  4. alexquse

    Bug in nvivo 9

    I found a bug on Nvivo 9. I had noticed long ago, but since it is special circumstances and not a very important problem, I had forgotten it. It is impossible to copy more than one node in a node of the window "find result". Nvivo closes unexpectedly.
  5. I worked for years with nvivo. My greatest disappointment is the slowness of the software (I've complained many times here). If you have a dataset of a some size, each operation takes several seconds. This does not seem serious, but when you repeat some coding operations 1000 times, it ended up taking time. The problem actually started with version 8. I went from version 8 to version 9, because the advertising said it would improve the speed. But in fact, the improvement may be 20%, which solves nothing since, for example, from 10 seconds to 8 seconds, it is still 8 times too long! Now we are told that version 10 is faster. But what is it really? is there people working with "normal" corpus of qualitative research (eg, 50 interviews is 1000 pages)?
  6. Here is a solution (by converting classification into nodes) http://forums.qsrint...?showtopic=3436
  7. Hi, I have many classifications of sources. So my question is what and how can I do with these classifications? I want to analyse the distributions of node by source attributes, but it seems very laborious. The only easy features I've found is to visualize sources by attributes. Does anyone have a solution to use these classifications. I should mention that I sought for a long time and the only option I've found is to create node. Does anyone know a way to pass from source classification to node classification. Thank you Alex oopss!! sorry for the multiple post : I received an error message and though that nothing was published
  8. alexquse

    Fix problem that causes corrupt files!

    For a long time I wish that qsr make a more stable, lighter, more practical in terms of usal practice of research (efficiency, flexibility, speed). I lose a lot of hours because nvivo often freezes. But I had only once a corrupted file: am I lucky?
  9. alexquse

    search folder

    search folder is a nice feature I've just discover now .... but the search form miss "not coded at"
  10. I've found my previous issue. It was just the reverse problem (and with nvivo 8) http://forums.qsrint...?showtopic=3436 I'm still looking for a solution to automatically transform attributes which are pointed with a series of nodes to a classification edit: I've solve my problem in ten minutes of manual coding ;-°
  11. Hello, I 've searched for hours, maybe it's easy !!?? I have a series of nodes that I want to turn into classifications. In other words, attribute values are stored in nodes, and I want to stored them in classification. It seems to me that in NVivo 8 it was possible to transform nodes into classification by the way of the collection (set) and then export in an excel sheet and re-import as classification sheet. But I do don't see how to achieve this with nvivo9. Any idea? Thanks Alex
  12. I'm not sure to fully understand your method, but it should work (do you select "automatic select hierarchy"?). Otherwise I have a method which is a bit "prehistoric". I usually often create an "allnode" (with aggregate fonction (nv9) or merge (nv8)). Then with a simple coding query = everything that is not coded at allnode. It's pretty simple, very robust and the "allnode" code is useful for other "administrative operations".
  13. Not an answer but add: it would be great if there was a simple procedure to export in pajek (a powerfull and free tool to visualise network).
  14. Hello, I don't know if your idea really fit to a qualitative perspective,but... I made a proposal some time ago, that goes in your direction. I can developp it here: The principle is to include a timeline, for example to detect the first appearance of a concept (in different interviews/sources/cases), to identify what precedes/accompanies/follows this emergence. This tool could trace the evolution of the concept: the first appearance is accompanied by such a node, second is accompanied by such a node, third... I think you could then realize the kind of analysis you're talking about. But I do not know exactly how to realise this feature. just a first idea: - the user builds a timeline with categories (1-2-3-4-5) , selects a node (N)and select a filter (source xx) - the fonction creates a "time-node" as a sequence of nodes (N1xx - N2xx - N3xx - N4xx - N5xx....) by the timeline and related to the filter. - the user can test what is link to N1, or the difference between different filter N1xx and N1yy... I hope to be not too obscure...
  15. I often read this. I confess that I am not very confident with my technique, but I do precisely the opposite: I distinguish very early between rough concepts and I refine later. I understand that this way is "hazardous", but it seems to me to have heuristics virtues (otherwise, I'm quickly jammed). I practice at the extreme this way of doing but sometimes I wonder if I do not getting lost in such an analytical decomposition when it goes too far (for example: I code the modalities separately, so the negation "a" and "non-a" shares one code: "a"; and are distinguish with another one: positiv/negativ) @Pablo: We are indeed quite agree. I also implicitly raised the idea to discuss structures of nodes here. Once I posted one of mine. But I realized that, if it takes an half day to anyone to understand the study of someone and make relevant remarks about the working technics... there won't be a lot of dicussion. (Another problem is that my studies are in French)
×