Don Fraser of QSR  added this comment privately to me about the nature of
work possible with say, video clips as databites in Nvivo - as he hasn't
sent it to the whole list
 I will do it for him, I append his whole comment in below
because to a certain extent it adds to my understanding of the NVivo
'databite' and its implications (rather, a blinding flash on the road to the
wine bar actually Don! thanks)

....to summarise (summarise? - that'll be the day) and add my own
understanding of what he is saying; when
you create a video clip, the whole clip is actually automatically coded
because there may
be codes embedded in the text where the databite link(anchor) is situated -
therefore if you browse the text at a code, or do a search which involve the
code(s) - the browsable
retrieval or results from the search will also give you (and flag up) the
databite anchor - so you can open the clip from the coded position. See?  So
this is rather nice - given that the file in which  the link/databite is
embedded is editable - and this file may be your analysis / commentary on
all your multi media clips: so.... you can be adding commentary to a whole
series of say photo, video clips,  on-line matter from all sorts fo
sources - and know that every time you code the text in the 'commentary
file' if thats what it is - once you put a databite in that bit of text, you
are also, by the back door, coding the whole video clip etc by a code or
codes
(but not bits of the video clip) I hope I have understood what Don said.

Also I woudl like to add the comment - that the usefulness of being able to
code multi-media stuff in itself may not be the answer to everyones dreams -
often  its the ability to be writing and keeping track of your thinking and
being able to annotate new  commentary about the multi-media stuff as you
look at it (and yes, maybe being able code and link new clips to the growing
commentary) - and the
flexibility of this - which may be important - and this particular aspect is
not replicated, YET,
as far as I know in quite the same way in any other software.
.....what I say here really, is all about the ability to edit documents, and
change
their appearance, and the signals in them. Of course - there may be plenty
of files you woudln't want to change too mcuh,if it all - but very nice to
be able to just write new commentaries/summaries and have the same facility
to code and link to other things as you go along. Now, to the wine bar.
Ann Lewins

Don Fraser says....
A comment in regard to your recent posting.  You do actually code a video
clip (databyte) whenever the link is coded.  Thus searches and other coding
display/retrieval forms will retrieve the databyte anchor and thus the video
clip. This of course involves coding the whole media clip with one or more
codes.

The difference with other products is that if you only wanted to code say-
minutes 3 to 5 of the video clip, then with NVivo you need to "snippetize"
it, trimming down the video file to just minutes 3-5 and then linking that.

Of course the proxy file approach allows a combination.  A proxy can have
entries minute by minute - or frame by frame to allow fine and combinational
coding complexity.

It is a tradeoff we recognised in designing NVivo.  One media per
"document"/Hu and you can do complex coding - but multiple media per
document whilst allowing more complex annotation and matching the style used
in non QDA software (printed journals, compound word documents) necessitates
simpler coding (of subordinate media).



-----Original Message-----
From: Ann Lewins <[log in to unmask]>
To: [log in to unmask] <[log in to unmask]>
Date: 19 January 2000 10:21
Subject: Re: Video taped data


>
>>David Smilde wrote:
>>
>>> I would imagine that NVivo does as well.
>
>
>Susanne Friese wrote:
>>You can work with so-called data bites in Nvivo (as I remember the
>terminology correctly). This also included video data bites. However the
>cutting up of the video has to be done in another programm, it can't be
done
>in Nvivo itself. You can then incorporate those video data bites within
your
>data analysis.
>>
>>Susanne
>
>
>There is a  bit of a difference between these two ways of using and
>referring to video in Atlas and Nvivo: - in NVivo as Susanne says - you can
>'link' to  video databites - a flag from a particular point in a text file
> you can code the text file) opens the video clip - but  you are not  able
>to physically code the video clip itself.
>
>In Atlas, and I believe Hyperresearch, as Harald Klein points out, the
video
>clip can be a 'codeable' data file itself.
>
>Both ways are useful - in Nvivo the linked databite approach shifts the
>emphasis to the video clip as 'supporting' a text file(s) where the main
>work/commentary/ etc is going on .  In Atlas and HyperResearch the video
>clip is more of an independent object.
>
>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
>
>
>




%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%