Thank you so much for your help - I feel it has taken me quite a bit
further. Best regards, Jens Kjaerulff
On Tue, 4 Jan 2000, Lyn Richards wrote:
> Jens,
>
> Your questions re NVivo: I'll answer them here since they are all methods
> type questions, but note the QSR-Forum handles N4 and NVivo technique issues
> fulltime, and [log in to unmask] is a free helpline for specific queries.
>
> 1) yes you can print from the document browsers - and also node browsers -
> with coding stripes in NVivo 1.1, but at the moment it will indeed come in
> small print to allow for the complexity of stripes. We'll work on
> customizing it: comments of course noted and appreciated. As are details of
> particular printer configurations that do odd things - pls send to
> [log in to unmask]
>
> 2) >I don't understand the difference between "node sets", "case-nodes" or
> "case-type-nodes".
>
> They're for different purposes. Sets of nodes (or documents) are groupings
> that you create for any purpose; the set editor allows you to filter them
> finely, ask questions about the characteristics of the set etc. and the
> search tool allows you to scope your search exactly to any set or sets. Sets
> of nodes don't necessarily have any logical relationship. I might have a
> set for all the nodes I'm working with for this paper, or all the nodes that
> have something to do with cartoon characters. You can code with a set or
> look at a set or profile a set or search just the text coded by a set of
> nodes.
>
> Case nodes are there for researchers who want to manage data from many
> sources for a case. If you had material on Bart Simpson from several
> documents and a couple of interviews you'd want to be able to ask questions
> about all the Bart material. If you code it at a case node for Bart, you can
> retrieve or search everything about Bart by nominating that node. Since you
> can store attributes for any node, everything you know about Bart can be
> attributes of his node, and then when you find something else about him, and
> code it with his node, all that information is just "piggy-backed" with the
> coding. Now you can ask questions about all the data on characters with hair
> color yellow etc.
>
> Case type nodes are there for those of us who have several types of cases -
> e.g. cartoon characters and cartoonists and readers. Helps housework, and
> makes searches more rapid (scope my search to anything coded at any of the
> characters.) If you give values to attributes for a case type node (e.g.
> readers) all the cases will inherit those attribute values. Saves time -
> e.g. all the readers I am interviewing may be teenagers in a given city and
> hair color unknown. (If you imported case nodes from N4, they appear in
> the hierarchical trees because N4 doesn't have the ability to store
> attributes).
>
> 3) >both to Nvivo and Nudist, it appears that it is not possible to browse a
> parent node, and then have included in the report "hits" of the child nodes.
>
> Can do in both - just it doesn't automatically do that since you mightn't
> want to. You might want to store coding about the Simpsons as a family at
> the parent node, then about Bart in particular at his node.
>
> If you want to browse the text at the parent and the children, you just ask
> for that. (In N4 you collect at that node, in NVivo you can do it more
> finely - specify the union of the coding at all child nodes or any
> particular ones you want to gather together for browsing.) In either case
> what you get is all the coding merged seamlessly (no duplications) at a new
> node, so you don't have to lose the particular coding you've done at
> Simpsons.
>
> Hope this helps,
> cheers
> Lyn
>
>
>
> Lyn Richards,
> Research Professor of Qualitative Methodology, University of Western
> Sydney,
> Director, Research Services, Qualitative Solutions and Research.
> (email) [log in to unmask]
> (Ph) +61 3 9459 1699 (Fax) +61 3 9459 0435
> (snail) Box 171, La Trobe University PO, Vic 3083, Australia.
> http://www.qsr.com.au
>
>
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|