Dear ELAN Workshop attendees, and anyone who might find this of interest,
\nThere were a few loose ends left at the end of the ELAN workshop last week. I’d particularly like to address one, the question as to whether we should aim for a standard set of ELAN templates which everyone uses.<\/p>\n
\nTo me this is OK if we are talking about a community of people working in the same way on the same sort of data who wish to agree on certain standards in order to make various kinds of data-sharing and analysis easier. Obviously a good idea to be using the same categories and the same set of values within those categories (although not necessarily easy to get people doing that sometimes I’ve noticed!)
\nHowever, it needs to be stressed that ELAN is a program which can be used to mark up many kinds of data in an infinite number of ways, only one of which is the Toolbox-friendly set of interlinearization tiers I displayed during the workshop.
\nTo give an example, I am marking up my data for different prosodic features. I have, among others, an Intonation tier on which I mark up different intonational tunes, and combinations of tunes. Using the powerful search function of ELAN, I am able to search instantly across hundreds of my files marked up in this way, for a particular tune. I am then able to view and hear (in its original context) any of the selections listed in my search window simply by clicking on it in the displayed list. I am then able to instantly open that selection in Praat by right-clicking on the selected area of waveform, and so am able to do acoustic analysis, or export pitch traces for illustrations in papers. Trust me, it’s incredibly useful. In effect it gives me an acoustic analysis database.
\nThis tier, and the entries in it, are not standard, as on the one hand they are language-specific, and on the other, I’m working it out as I go.
\nI also have, as another example, a Topic Index tier, which means I can instantly locate all the data we have collected on Green Sea Turtle anatomy, for example, which is useful in preparing new interviews on the subject, and for introducing the relevant data to specialists working with our project. I can have all of this data at my fingertips instantly, and export it as text in various formats, or export a translation tier as subtitles for a quicktime movie.
\nFurthermore, as it is possible to merge any number of ELAN annotations which refer to the same media, I can view an interlinear gloss imported from Toolbox, at the same time, and in the same window, as any of the non-standard annotation tiers I have created for that media. If there are tiers I’m not particularly interested in at a given time, they can be hidden so that the tier display is not cluttered.
\n‘Intonation’ and ‘Topic Index’ are just two examples of the many tiers I have created to facilitate my particular research needs. Clearly someone interested in aspects of syntax would have their data marked up quite differently. And someone working on Song would have a different set of tiers again. Etc, etc.
\nThe notion, therefore, that ELAN is useful for aligning existing Toolbox or Shoebox annotations with media files, and that’s about it, which seems to be out there, is far from the truth. I do initial transcription work in ELAN, then export selected texts to Toolbox for automatic interlinearization and lexicon building, then bring them back into ELAN and merge them with other tiers I may have been using during the same period, or tiers which I create subsequently. Of course, once imported, the morphemic gloss from Toolbox becomes available to the ELAN search function, so I can instantly bring up a list of all instantiations of 3sgA>1pl.incl prefixes, or whatever I want.
\nAll of that said, it would be useful to have a few ELAN templates available for download, as Rachel Nordlinger suggested on David Nash’s behalf, if I remember correctly. In particular, it would be good to make readily available the ELAN template which exports to Toolbox, and the marker file required by ELAN to import text from Toolbox. I’ll check if these are currently available anywhere on the web, and if not, I’ll attempt to get them uploaded somewhere and let people know.
\nI hope this may have clarified a few things for a few people.
\nBest wishes,
\nBruce Birch.
\nBruce Birch
\nPlease note I have new email address:
\nbirchb (at) unimelb.edu.au
\nIwaidja Documentation Project
\nDepartment of Linguistics and Applied Linguistics
\nUniversity of Melbourne
\nVIC 3010
\nAustralia
\nphone: +61 (0)3 8344 4588
\nmobile (aust): +61 (0) 410 103 965
\nmobile (europe) +49 (0) 162 380 4213<\/p>\n","protected":false},"excerpt":{"rendered":"
Dear ELAN Workshop attendees, and anyone who might find this of interest, There were a few loose ends left at the end of the ELAN workshop last week. I’d particularly like to address one, the question as to whether we should aim for a standard set of ELAN templates which everyone uses.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[9,4,5,6,7,3],"tags":[],"class_list":["post-3514","post","type-post","status-publish","format-standard","hentry","category-archiving","category-fieldwork","category-linguistics","category-paradisec","category-rnld","category-technology"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.paradisec.org.au\/blog\/wp-json\/wp\/v2\/posts\/3514","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.paradisec.org.au\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.paradisec.org.au\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.paradisec.org.au\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.paradisec.org.au\/blog\/wp-json\/wp\/v2\/comments?post=3514"}],"version-history":[{"count":1,"href":"https:\/\/www.paradisec.org.au\/blog\/wp-json\/wp\/v2\/posts\/3514\/revisions"}],"predecessor-version":[{"id":4112,"href":"https:\/\/www.paradisec.org.au\/blog\/wp-json\/wp\/v2\/posts\/3514\/revisions\/4112"}],"wp:attachment":[{"href":"https:\/\/www.paradisec.org.au\/blog\/wp-json\/wp\/v2\/media?parent=3514"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.paradisec.org.au\/blog\/wp-json\/wp\/v2\/categories?post=3514"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.paradisec.org.au\/blog\/wp-json\/wp\/v2\/tags?post=3514"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}