To: [log in to unmask] <[log in to unmask]>
Date: 06 July 1999 11:15
Subject: Practical tips for exploratory research using NUDIST
>Ann,
>
>I hope you remember me from my attendance at the NUD*IST training on 12th
>May. I have started a part-time PhD at the sociology department of LSE into
>the "Spirituality of Work". This will be very much an exploratory study and
>one employing unstructured interviewing extensively. I plan to use NUD*IST
>also extensively.
>
>I have already imported and coded 8 interviews to gain experience and to
>develop a personal approach/methodology. This experience gave me insights
how
>I could expect theory to emerge from my analysis; or to be more precise,
that
>it wasn't going to spring automatically from using the software tool!! As a
>consequence I explored your web site (http://www.soc.surrey.ac.uk/caqdas/)
>and have just read the following:
>Barry, C. A. (1998). "Choosing Qualitative Data Analysis Software: Atlas/ti
>and Nudist Compared." Sociological Research Online 3(3).
>Buston, K. (1997). "NUD*IST in Action: Its use and its Usefulness in a
Study
>of Chronic Illness in Young People." Sociological Research Online 2(3).
>Coffey, A., B. Holbrook, et al. (1996). "Qualitative Data Analysis:
>Technologies and Representations." Sociological Research Online 1(1).
>Kelle, U. (1997). "Theory Building in Qualitative Research and Computer
>Programs for the Management of Textual Data." Sociological Research Online
>2(2).
>Lee, R. M. and N. Fielding (1996). "Qualitative Data Analysis:
>Representations of a Technology: A Comment on Coffey, Holbrook and
Atkinson."
>Sociological Research Online 1(4).
>
>I found these invaluable as an engineer/part-time novice social scientist!
>Moreover, they reinforced my own experience. Consequently, the reason for
>this note is to seek more specific advice on the use of NUD*IST on
>"exploratory" research: how I should allow theory to emerge from data; how
>many more interviews I should code before detailed analysis commences;
>suggestions for balancing detailed and broad-brush coding; any ways to
avoid
>a simply hierarchical/linear approach to theory construction.
>
>I realize that these questions are probably a lot easier to ask than
answer.
>Nonetheless, I hope that I can at least learn a little from others; and not
>to repeat past mistakes or bad practices!
>
>I'm particularly looking for practical tips or 'rules of thumb' at this
stage
>before I commit my self too deeply in a particular approach. I would also
>welcome any recommendations you could make for readings in this area
>(especially those available through the web).
>
>Thanks in anticipation,
>
>Tim Bowman
>Room 15/2A-W03-E E-mail: [log in to unmask]
>Tel: 44-1268-403917 Fax: 44-1268-405747 Internal tel: 738-3917
>
Hallo Tim - nice to hear from you again
NOT MUCH tIME tIM TO ANSWER THIS - BUT i'D SAY - always use the hierarchy
(where, like in Nudist you have a 'naturally' occurring hierarchical
system)to do the balancing act between broad brush and detail
you can use the Collect Index system search to go backwards to broad brush -
if you used detailed approach to start with - (or you can selectively
create a collection of some of yr codes in a temporary hierarchy) then do a
Collect on those (Index system search/Collect)
or while you are 'browsing' the broad brush stuff you can develop the
hierarchy below a broad brush approach by 'coding-on' (Lyn Richards' term)
i.e. recoding (straight into a hierarchy) - Nudist is excellent for this
approach.
When lookign at broad brush coded ouptut (make report) you coudl also
include the detailed codes in a code stripe report - so you see the broad
stuff as a whole (thats all you see in terms of text retrieval - but you see
the detailed codes recorded in the margin) - don't know whether I had time
to show you that in the workshop -sometimes I do - sometimes I don't.
send me yr address and I'll send you the relveant supplement if I forgot to
include it in your pack
Don't see codign process as a stage you have to do before analysing -
I think personally your theory shoudl grow and be tested all the way thro.
and of course you won't see s/w as doing the thinking for you I am sure !-
that all comes from you -
but thats all a bit vague - no time to help with further references at
moment - but others on qual-software might come up with plenty of
suggestions - so I am copying it to the list?
cheers
Ann Lewins
Resource Officer, CAQDAS Networking Project
Dept of Sociology
University of Surrey
GUILDFORD GU2 5XH
email: [log in to unmask]
CAQDAS web site: http://www.soc.surrey.ac.uk/caqdas/
Tel +44 (0)1 483 259 455
Fax +44 (0)1 483 259 551
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|