Gwen<div><br></div><div>I am not an IT expert but what I have learned is that you should NOT use periods within the filename but rather use just one period followed by the MIME extension (that indicates the file data type), like .wav, .eaf, .prj etc. at the end of the filename. So basically DON'T use <span class="Apple-style-span" style="color: rgb(31, 73, 125); ">KS2009.09.19.01.wav, as opposed to KS2009_09_19_01.wav</span></div>
<div><br></div><div>Also, the advice I have heard is to avoid spaces, avoid periods, avoid punctuation (like: # , > < : * ( !) and avoid non-ASCII characters.</div><div><br></div><div>Best,</div><div>Peter <br><br><div class="gmail_quote">
On 4 May 2010 15:49, Gwendolyn Hyslop <span dir="ltr"><<a href="mailto:glow@uoregon.edu">glow@uoregon.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div lang="EN-US" link="blue" vlink="purple">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Dear RNLDers,</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Thanks so much for this discussion; I have appreciated following
it. I’d like to add to it by asking one small question. There has been
discussion about not using capital letters or spaces in files names, but I am
wondering about the use of periods (.) as a way to separate information in file
names, as opposed to an underscore (_) or hyphen (-). In other words, is there
any known problem with doing something like: KS2009.09.19.01.wav, as opposed to
KS2009_09_19_01.wav?</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Best,</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Gwen</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Georgia","serif";color:#1F497D">=====</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Georgia","serif";color:#1F497D">Gwendolyn Hyslop</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Georgia","serif";color:#1F497D">Department of Linguistics</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Georgia","serif";color:#1F497D">1290 University of Oregon</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Georgia","serif";color:#1F497D">Eugene, OR 97403, USA</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Georgia","serif";color:#1F497D">+1-541-505-1594 (USA)</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Georgia","serif";color:#1F497D">+975-1776-2177 (Bhutan)</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Georgia","serif";color:#1F497D"><a href="http://www.uoregon.edu/~glow" target="_blank">http://www.uoregon.edu/~glow</a></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt">From:</span></b><span style="font-size:10.0pt"> Peter Austin
[mailto:<a href="mailto:pa2@soas.ac.uk" target="_blank">pa2@soas.ac.uk</a>] <br>
<b>Sent:</b> Monday, May 03, 2010 10:28 PM<br>
<b>To:</b> Alex Francois<br>
<b>Cc:</b> Resource-Network-Linguistic-Diversity; <a href="mailto:munanga@bigpond.com" target="_blank">munanga@bigpond.com</a></span></p><div><div></div><div class="h5"><br>
<b>Subject:</b> Re: Labelling and metadata</div></div><p></p>
</div><div><div></div><div class="h5">
<p class="MsoNormal"> </p>
<p class="MsoNormal">Alex</p>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">Here's a possible solution.</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">In your Excel metadata sheet add a column called 'file' and
for each row go to the Insert Menu > Hyperlink and you can insert a
hyperlink to the relevant file (with its short unique ID) -- in Windows
Control-K is the shortcut for this. Save your Excel file. When you click on
this cell now the file will be opened by the software that you have associated
with it (eg. 2010-05-04.prj will open with Toolbox etc -- you might get a
warning from Excel about the dangers of opening the file but that's just
Microsoft being helpful). </p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">So, Excel has a function that does what you said you do
manually: "<span><span>try and identify the string of digits which I'm looking
for, write it down, then try and access the recording among hundreds of files,
essentially in a non-automatic way". This is the solution David Nathan was
alluding to in his post. (You can also do this in HTML if you prefer that over
Excel.)</span></span></p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal"><span><span>If
you set up your Excel columns with the semantic fields that are useful to you
(ie. the ones you listed out for us) then simply sort on whatever column you
like. find what you're after and click the hyperlink to open the file. You can
easily add new columns, like "Have you transcribed this file yet?" or
"Date of last checking of this file" etc. and then use them to sort
and access you data files.</span></span></p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal"><span><span>As
David suggested in his post, this is an information management system solution
to the problem. The SIL promise-ware that was mentioned in an earlier post is a
packaged application solution.</span></span></p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal"><span><span>I
think this kind of "dirty laundry confessions" is really useful for
us to share experiences and solutions that work for each of us, so thanks Alex.
It's the kind of "bottom up" development of good practice ideas that
I find valuable from a forum like this one.</span></span></p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal"><span><span>Best,</span></span></p>
</div>
<div>
<p class="MsoNormal"><span><span>Peter</span></span></p>
</div>
<div>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal">On 4 May 2010 14:43, Alex Francois <<a href="mailto:Alexandre.Francois@vjf.cnrs.fr" target="_blank">Alexandre.Francois@vjf.cnrs.fr</a>>
wrote:</p>
<div>
<p class="MsoNormal"><span style="font-size:13.5pt">dear Greg, dear all,<br>
<br>
Useful thread indeed. <br>
I am especially curious about the contrast suggested in the earlier discussion,
between trying to include semantics in filenames, vs using opaque filenames and
then search a database.<br>
<br>
The reason is, during the last decade, I have experienced the two ends of the
spectrum, and I'm not sure where I should stand now. <br>
<br>
For many years, I had taken the habit of naming my audio files with maximally
informative (and therefore rather long) names, such as:</span></p>
<ul type="disc">
<li class="MsoNormal"><b><span style="font-size:13.5pt;color:#6600CC">BD04-24
Veraa Harold ch Jesus mtp-vrs.wav</span></b></li>
<li class="MsoNormal"><b><span style="font-size:13.5pt;color:#CC0000">DD04-13
Lovoko Mamuli leg Laperus2 tnm.wav</span></b></li>
<li class="MsoNormal"><b><span style="font-size:13.5pt;color:#006600">ED10-30
Yaqane Edwad-Bilis conv chamanisme hiw.wav</span></b></li>
</ul>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">[NB: At that time I would use spaces in filenames (I'm
not doing this anymore), but this can be easily changed to underscore with some
file utility. Sometimes I even used non-Ascii characters, I confess! ]</p>
</blockquote>
<p class="MsoNormal"><span style="font-size:13.5pt">These file names would begin
with a unique alphanumerical ID, so that the chronological order of recordings
would be easily retrieved by automatic sorting. The other reason for
starting a long file name with an id, was that, should some software truncate
the filename to the first 8 characters, it would still remain unique.<br>
Here is how my (customised) system worked:</span></p>
<ul type="disc">
<li class="MsoNormal"><span style="font-size:13.5pt">first letter is a
code for a whole collection = a single fieldtrip [A for my first
fieldtrip, B for my second.... F for my 6th]; </span></li>
<li class="MsoNormal"><span style="font-size:13.5pt">second letter is a
code for the support (D for digital audio recording, P for photo, V for
video…)</span></li>
<li class="MsoNormal"><span style="font-size:13.5pt">then 2 digits for
a subcollection (in the olden days this was the number of a
minidisc); This subcollection ID is also the name of the folder in
the folder-tree.</span></li>
<li class="MsoNormal"><span style="font-size:13.5pt">then hyphen plus 2
digits for item in this subcollection (never more than 99)</span></li>
</ul>
<p class="MsoNormal"><span style="font-size:13.5pt">and then the <i>Homo Sapiens</i>-friendly
stuff came in:</span> </p>
<ul type="disc">
<li class="MsoNormal"><b><span style="font-size:13.5pt;color:#6600CC">location
of recording</span></b><span style="font-size:13.5pt">, spelled out
— usually a village in Vanuatu: e.g. Veraa (=Vera'a, a village in
Vanua Lava), Yaqane (a hamlet in Hiw); or in the Solomons (Lovoko,
Vanikoro);<br>
</span></li>
<li class="MsoNormal"><b><span style="font-size:13.5pt;color:#6600CC">name
of main speaker</span></b><span style="font-size:13.5pt">, spelled out<br>
("Harold"; "Mamuli"; "Edwad-Bilis" as this
was a conversation between two men); <br>
names also uttered in full in the recording itself.<br>
</span></li>
<li class="MsoNormal"><b><span style="font-size:13.5pt;color:#6600CC">genre
of recording</span></b><span style="font-size:13.5pt">, using a limited
set of abbreviations: <br>
ch= chant (song), ct='conte' (tale), leg='legend', conv='conversation',
etc.<br>
</span></li>
<li class="MsoNormal"><span style="font-size:13.5pt">a very <b><span style="color:#6600CC">short title</span></b>: <br>
"Jesus" (a church song on someone with a name like this); <br>
"Laperus2" (the legend of Lapérouse's wreckage — second
version by same speaker that day); <br>
"chamanisme" (a conversation on shamanism);<br>
</span></li>
<li class="MsoNormal"><span style="font-size:13.5pt">a 3-letter <b><span style="color:#6600CC">id for the language</span></b> <br>
=> Very useful as several languages can be spoken in the same village,
and sometimes the very same person would tell me the same story in 2
different languages. <br>
e.g. tnm=Tanema, hiw=Hiw; <b>mtp-vrs</b>= Mwotlap and Vurës, because
this church song was exceptionally mixing the two languages. </span><br>
[I'm not using ISO codes because they are opaque, and poorly designed for
my area; but the equivalence between the codes I use and ISO codes is made
easily accessible in my publications & <a href="http://alex.francois.free.fr/AF-field.htm#Vanuatu" target="_blank">homepage</a>
anyway.]</li>
</ul>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:13.5pt">Admittedly
some info is missing, e.g. my own name, or the date: but the date is
usually retrievable from the collection & subcollection, and I always
uttered it orally in the recording itself. Maybe one day I should hardcode it
in the filename. <br>
<br>
These (relatively) transparent long names have proven very useful to me as I
was working on all these files, whether to transcribe them, compare different
versions of similar stories, or whatever. Because I have 1150 different
sound files in my corpus, it proved also convenient to perform automatic search
queries on filenames, say, to easily retrieve all recordings with the same
storyteller over the years, or to filter all recordings of the same
language. I don't know if I would recommend such a system (maybe not) but
at least I found it convenient for myself: the file name says it all. The good
thing was also that most of these filenames were easily interpretable to people
other than myself, with a minimal amount of abbreviations or codes. The initial
id (BD04-24…) doesn't really need to be interpreted anyway (it's an id),
but the village & speaker's names (+title) are explicit, and a simple Txt
file can help make sense of language names or genres (and collections).
In parallel I've always used spreadsheet for metadata, with full name of
speaker, their age, precise location, date, full name, etc.<br>
<br>
And then a few years ago, I wanted to archive these hundreds of files into our
open archive</span> (LACITO's <a href="http://lacito.vjf.cnrs.fr/archivage/presentation_en.htm" target="_blank">Archivage</a>)<span style="font-size:13.5pt">. <br>
When they saw these long file names, our IT people were horrified. They
insisted that they should all be shortened to a simple id, as short as
possible, getting rid of all the semantics. They thought it would be much
more convenient, or more elegant perhaps, to handle filenames like "<b><span style="color:#6600CC">AF03-05-02.wav</span></b>" </span><i>[AF03=my
initials + 3rd field trip, etc.]</i><span style="font-size:13.5pt">, coupled
with some metadata file. Fair enough, they were surely right. (my earlier
use of spaces and occasionally non-Ascii was probably at fault, together with
the sheer length of each string).<br>
<br>
So I created a copy of my 1150 audio files, and renamed them all (manually)
with these elegant numbers, which are now opaque even to myself. Took me
ages (weeks? months?). In parallel I would fill a metadata sheet for each
item, and send it to the IT people for them to encode in Xml/Xsl format onto
the server. (I didn't know Xml/Xsl/Php well enough to create the search
interface myself.) This was several years ago, and it never became as
convenient as I was hoping it would be. In fact a fair part of the metadata is
still awaiting to be format-converted & transferred to a new server, which
was stopped halfway due to shortage in funding… but this is another
story.</span><span style="font-size:18.0pt"><br>
</span><span style="font-size:13.5pt"><br>
In the meantime, I now have my whole audio archives (37 Gb) in two versions:
exactly the same sound files, but one set has the old filenames, one has the
numbers. This is very silly, and was meant to be temporary, yet has lasted for
some reason. <br>
Finally what happens is, every time I want to quickly retrieve a file from my
archives, I basically have the choice between accessing the set of files with
the long, transparent names which are visually readable, easily searchable, and
instantly clickable <br>
— OR accessing my metadata spreadsheet, try and identify the string
of digits which I'm looking for, write it down, then try and access the
recording among hundreds of files, essentially in a non-automatic way.
Now guess which solution I end up choosing. (*grin*)<br>
<br>
There's probably something I've done wrong (as always) but I'm still wondering
what the ideal combination would be. It seems that different usages
(working on one's own files vs long-term archiving…) may warrant
different decisions, but of course this is not a good answer to Greg.<br>
I am especially trying to identify the best procedure in terms of archiving for
the future, and making access easy for other prospective users.<br>
<br>
regards,<br>
Alex.</span></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="100%" align="center">
</div>
<div>
<div>
<p class="MsoNormal"><br>
Margaret Carew wrote: </p>
<pre>Useful thread, and I am now looking back at my various drives with one eyebrow raised...</pre><pre> </pre><pre>I'm wondering, what is the role of folders in all this?</pre><pre> </pre><pre>I have an almost well organised system of audio recordings that is in the main not archived (although carefully backed up!), from various years and places. I have established a folder for each year that has passed since I commenced recording in digital (ie. 2006 2007 etc). Within each of these year folders is a recording session folder with a name that includes the year and month (sometimes day) the place and the event or key topic. Within each of these secondary folders are the recordings that are part of that session, with a date, speaker and other semantic info (eg. 20100209_BP_kurdu_wita.WAV). The metadata files (marked up text files) are stored within each folder, and the name of the folder is entered as a field in the metadata.</pre>
<pre> </pre><pre>Like my erstwhile colleague Greg I'm probably closer to the hodge-podge end of things, doing lots of recordings with students, sometimes in a bit of a random fashion, multi-tasking like crazy, yet trying to keep some order in it. I'm now wondering whether the folder based system is going to be a problem when it comes to archiving - one thing that has popped up is the existence of these lots of folder based metadata files - this might need to be consolidated into one file.</pre>
<pre> </pre><pre>I might also add that I've become fond of using itunes to make playlists of recordings - usually edited ones - and to use as a secondary database (a kind of partial mirror if you like). You can use the file info to point back to the folderised filenames as described. And it's great for making CDs for students of their recordings, to repatriate materials quickly etc. Also good for compiling files that will be used in a resource (eg. a set of clips for a voiceover) Am I committing an archiving crime by using itunes in this way?</pre>
<pre> </pre><pre>Regards</pre><pre> </pre><pre>Marg Carew</pre><pre> </pre><pre> </pre><pre>-----Original Message-----</pre><pre>From: Claire Bowern [<a href="mailto:clairebowern@gmail.com" target="_blank">mailto:clairebowern@gmail.com</a>]</pre>
<pre>Sent: Tue 04/05/2010 00:49</pre><pre>To: David Nathan</pre><pre>Cc: Resource-Network-Linguistic-Diversity</pre><pre>Subject: Re: Labelling and metadata</pre><pre> </pre><pre>David, that would work at the end of the documentation (in fact I'm</pre>
<pre>doing something pretty close to that right now for One Arm Point</pre><pre>School for Bardi stories) but while working on the collection, doing</pre><pre>searches, transcribing, etc, I'm constantly using the underlying</pre>
<pre>files, and I'm not sure that creating another layer of reference would</pre><pre>solve the problem. It would be useful for managing collections where</pre><pre>there are several numbering systems though (e.g. I have tapes that</pre>
<pre>have 3 references - the AIATSIS archive tape number, the internal</pre><pre>collection number, and the number they'd get if I put them in my</pre><pre>scheme...)</pre><pre>Claire</pre><pre> </pre><pre>On Mon, May 3, 2010 at 6:58 AM, David Nathan <a href="mailto:dn2@soas.ac.uk" target="_blank"><dn2@soas.ac.uk></a> wrote:</pre>
<pre> </pre>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><pre>Dear all</pre><pre> </pre><pre>About the filenames, there are some excellent suggestions in this</pre><pre>thread, but I think that there is a tendency to conflate the function</pre>
<pre>of filenames as identifers with the functions that enable retrieval</pre><pre>and access to resources. This conflation remains invisible only while</pre><pre>we all keep imagining that documentation materials are merely "data" -</pre>
<pre>without some genres, granularities, interface considerations etc. that</pre><pre>relate to the presentation and usage of the resources. In that sense,</pre><pre>you might think (even hypothetically) of the interface by which you</pre>
<pre>might wish people to access them, and it is probably likely to be some</pre><pre>kind of link. As those familiar with HTML and related technologies</pre><pre>know, a link has a target as well as a "display text" (and other</pre>
<pre>possible attributes in semantic web formalisms). Translating this back</pre><pre>to one's local data management, there seems a good case for separating</pre><pre>out the two functions mentioned above, and thinking about a simple</pre>
<pre>linking system (that you can implement easily in spreadsheet pages, or</pre><pre>HTML), and then the relevant considerations for what you want the</pre><pre>"display text" to be - for yourself, and, quite possibly differently,</pre>
<pre>for other users. This might help resolve out the different issues that</pre><pre>are most relevant for each function in your contexts.</pre><pre> </pre><pre>best wishes</pre><pre> </pre><pre>David</pre><pre> </pre><pre>
At 18:11 03/05/2010, you wrote:</pre><pre> </pre>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><pre>If you are going to include semantics in the file names can I make a plea that your labels are a little more transparent -- why not use:</pre><pre> </pre><pre>
fm_2009_session10_audio.wav</pre><pre>fm_2009_session10_video.wav</pre><pre> </pre><pre>rather than FM09_v10A ?? v could stand for "version" or "volume" or who knows what else, and, as for "A", well that's anyone's guess. Also, if the "09" is a year then write it as >2009 (one might even argue for "felicity" or "meakins" rather than "FM"). I recommend separators like _ as well, as Bill Poser did in his contribution to this discussion. Note also, >that if you have more than 99 video sessions you'll need the label to be:</pre>
<pre> </pre><pre>fm_2009_session010_audio.wav</pre><pre> </pre><pre>I think there are good reasons for being a little more explicit in file names if you want to put in some (useful) semantics like this -- after all YOU know what "FM" "09" "v" "A" mean >but who else could guess? Compare that with:</pre>
<pre> </pre><pre>felicity_2009_session10_video.wav</pre><pre> </pre><pre>Best,</pre><pre>Peter</pre><pre> </pre></blockquote>
<pre>On 3 May 2010 18:19, Felicity Meakins <a href="mailto:f.meakins@uq.edu.au" target="_blank"><f.meakins@uq.edu.au></a> wrote:</pre><pre>This is a good point, particularly if you use two recorders (e.g. audio</pre>
<pre>recorded plus video camera) to record the same session. I use 'v' and 'a' to</pre><pre>distinguish these. In this respect, it is the recording _session_ that's</pre><pre>primary, not the actual recording.</pre>
<pre> </pre><pre>FM09_v10A</pre><pre> </pre><pre>FM=me</pre><pre>09=year (full date is in metadata)</pre><pre>v=video</pre><pre>10=recording session</pre><pre>A=part of recording session</pre><pre> </pre><pre>e.g. recording session may have taken place at X place but over two hours we</pre>
<pre>recorded 3 stories A, B, C.</pre><pre> </pre><pre> </pre><pre>On 3/5/10 6:13 PM, "Joe Blythe" <a href="mailto:blythe.joe@gmail.com" target="_blank"><blythe.joe@gmail.com></a> wrote:</pre><pre> </pre><pre>
</pre>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><pre>The only two cents worth I'd like to add to this discussion is that I had to</pre><pre>modify my numbering numbering system to indicate whether the original</pre>
<pre>recording was made with a video or dedicated audio recorder. I only mark the</pre><pre>video ones as "vid".</pre><pre> </pre><pre>Thus video files might be</pre><pre>20100503JBvid01.mov</pre><pre> </pre><pre>
Because you sometimes need to extract audio files from video files the video</pre><pre>file, such an extracted audio file would be</pre><pre>20100503JBvid01.wav</pre><pre> </pre><pre>This ensures that any files recorded on the same date from a dedicated audio</pre>
<pre>recorder (e.g., 20100503JBv01.wav) don't end up with the same file name.</pre><pre> </pre><pre>Joe</pre></blockquote>
<pre>--</pre><pre>Prof Peter K. Austin</pre><pre>Marit Rausing Chair in Field Linguistics</pre><pre>Department of Linguistics, SOAS</pre><pre>Thornhaugh Street, Russell Square</pre><pre>London WC1H 0XG</pre><pre>United Kingdom</pre>
<pre> </pre><pre>web: <a href="http://www.hrelp.org/aboutus/staff/index.php?cd=pa" target="_blank">http://www.hrelp.org/aboutus/staff/index.php?cd=pa</a></pre><pre>-------------</pre><pre>David Nathan</pre><pre>Endangered Languages Archive</pre>
<pre>SOAS</pre><pre>-------------</pre></blockquote>
</div>
</div>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="100%" align="center">
</div>
<pre>Dr Alex FRANÇOIS</pre><pre> </pre><pre>LACITO - CNRS, France</pre><pre> </pre><pre>2009-2011: Visiting Fellow</pre><pre> Dept of Linguistics</pre><pre> School of Culture, History and Language</pre><pre>
Australian National University</pre><pre> ACT 0200, Australia</pre><pre> </pre><pre> <a href="http://alex.francois.free.fr" target="_blank">http://alex.francois.free.fr</a></pre>
<p class="MsoNormal"> </p>
</div>
</div>
<p class="MsoNormal"><br>
<br clear="all">
<br>
-- <br>
Prof Peter K. Austin<br>
Marit Rausing Chair in Field Linguistics<br>
Department of Linguistics, SOAS<br>
Thornhaugh Street, Russell Square<br>
London WC1H 0XG<br>
United Kingdom<br>
<br>
web: <a href="http://www.hrelp.org/aboutus/staff/index.php?cd=pa" target="_blank">http://www.hrelp.org/aboutus/staff/index.php?cd=pa</a></p>
</div>
</div></div></div>
</div>
</blockquote></div><br><br clear="all"><br>-- <br>Prof Peter K. Austin<br>Marit Rausing Chair in Field Linguistics<br>Department of Linguistics, SOAS<br>Thornhaugh Street, Russell Square<br>London WC1H 0XG<br>United Kingdom<br>
<br>web: <a href="http://www.hrelp.org/aboutus/staff/index.php?cd=pa">http://www.hrelp.org/aboutus/staff/index.php?cd=pa</a><br>
</div>