TALD_manual/datasets.html at main · LingConLab/TALD_manual · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
<!DOCTYPE html>

<html>

<head>

<meta charset="utf-8" />
<meta name="generator" content="pandoc" />
<meta http-equiv="X-UA-Compatible" content="IE=EDGE" />


<title>How to create a feature dataset</title>

<script src="site_libs/header-attrs-2.30/header-attrs.js"></script>
<script src="site_libs/jquery-3.6.0/jquery-3.6.0.min.js"></script>
<meta name="viewport" content="width=device-width, initial-scale=1" />
<link href="site_libs/bootstrap-3.3.5/css/flatly.min.css" rel="stylesheet" />
<script src="site_libs/bootstrap-3.3.5/js/bootstrap.min.js"></script>
<script src="site_libs/bootstrap-3.3.5/shim/html5shiv.min.js"></script>
<script src="site_libs/bootstrap-3.3.5/shim/respond.min.js"></script>
<style>h1 {font-size: 34px;}
       h1.title {font-size: 38px;}
       h2 {font-size: 30px;}
       h3 {font-size: 24px;}
       h4 {font-size: 18px;}
       h5 {font-size: 16px;}
       h6 {font-size: 12px;}
       code {color: inherit; background-color: rgba(0, 0, 0, 0.04);}
       pre:not([class]) { background-color: white }</style>
<script src="site_libs/jqueryui-1.13.2/jquery-ui.min.js"></script>
<link href="site_libs/tocify-1.9.1/jquery.tocify.css" rel="stylesheet" />
<script src="site_libs/tocify-1.9.1/jquery.tocify.js"></script>
<script src="site_libs/navigation-1.1/tabsets.js"></script>

<style type="text/css">
  code{white-space: pre-wrap;}
  span.smallcaps{font-variant: small-caps;}
  span.underline{text-decoration: underline;}
  div.column{display: inline-block; vertical-align: top; width: 50%;}
  div.hanging-indent{margin-left: 1.5em; text-indent: -1.5em;}
  ul.task-list{list-style: none;}
    </style>


<style type = "text/css">
.main-container {
  max-width: 940px;
  margin-left: auto;
  margin-right: auto;
}
img {
  max-width:100%;
}
.tabbed-pane {
  padding-top: 12px;
}
.html-widget {
  margin-bottom: 20px;
}
button.code-folding-btn:focus {
  outline: none;
}
summary {
  display: list-item;
}
details > summary > p:only-child {
  display: inline;
}
pre code {
  padding: 0;
}
</style>


<style type="text/css">
.dropdown-submenu {
  position: relative;
}
.dropdown-submenu>.dropdown-menu {
  top: 0;
  left: 100%;
  margin-top: -6px;
  margin-left: -1px;
  border-radius: 0 6px 6px 6px;
}
.dropdown-submenu:hover>.dropdown-menu {
  display: block;
}
.dropdown-submenu>a:after {
  display: block;
  content: " ";
  float: right;
  width: 0;
  height: 0;
  border-color: transparent;
  border-style: solid;
  border-width: 5px 0 5px 5px;
  border-left-color: #cccccc;
  margin-top: 5px;
  margin-right: -10px;
}
.dropdown-submenu:hover>a:after {
  border-left-color: #adb5bd;
}
.dropdown-submenu.pull-left {
  float: none;
}
.dropdown-submenu.pull-left>.dropdown-menu {
  left: -100%;
  margin-left: 10px;
  border-radius: 6px 0 6px 6px;
}
</style>

<script type="text/javascript">
// manage active state of menu based on current page
$(document).ready(function () {
  // active menu anchor
  href = window.location.pathname
  href = href.substr(href.lastIndexOf('/') + 1)
  if (href === "")
    href = "index.html";
  var menuAnchor = $('a[href="' + href + '"]');

  // mark the anchor link active (and if it's in a dropdown, also mark that active)
  var dropdown = menuAnchor.closest('li.dropdown');
  if (window.bootstrap) { // Bootstrap 4+
    menuAnchor.addClass('active');
    dropdown.find('> .dropdown-toggle').addClass('active');
  } else { // Bootstrap 3
    menuAnchor.parent().addClass('active');
    dropdown.addClass('active');
  }

  // Navbar adjustments
  var navHeight = $(".navbar").first().height() + 15;
  var style = document.createElement('style');
  var pt = "padding-top: " + navHeight + "px; ";
  var mt = "margin-top: -" + navHeight + "px; ";
  var css = "";
  // offset scroll position for anchor links (for fixed navbar)
  for (var i = 1; i <= 6; i++) {
    css += ".section h" + i + "{ " + pt + mt + "}\n";
  }
  style.innerHTML = "body {" + pt + "padding-bottom: 40px; }\n" + css;
  document.head.appendChild(style);
});
</script>

<!-- tabsets -->

<style type="text/css">
.tabset-dropdown > .nav-tabs {
  display: inline-table;
  max-height: 500px;
  min-height: 44px;
  overflow-y: auto;
  border: 1px solid #ddd;
  border-radius: 4px;
}

.tabset-dropdown > .nav-tabs > li.active:before, .tabset-dropdown > .nav-tabs.nav-tabs-open:before {
  content: "\e259";
  font-family: 'Glyphicons Halflings';
  display: inline-block;
  padding: 10px;
  border-right: 1px solid #ddd;
}

.tabset-dropdown > .nav-tabs.nav-tabs-open > li.active:before {
  content: "\e258";
  font-family: 'Glyphicons Halflings';
  border: none;
}

.tabset-dropdown > .nav-tabs > li.active {
  display: block;
}

.tabset-dropdown > .nav-tabs > li > a,
.tabset-dropdown > .nav-tabs > li > a:focus,
.tabset-dropdown > .nav-tabs > li > a:hover {
  border: none;
  display: inline-block;
  border-radius: 4px;
  background-color: transparent;
}

.tabset-dropdown > .nav-tabs.nav-tabs-open > li {
  display: block;
  float: none;
}

.tabset-dropdown > .nav-tabs > li {
  display: none;
}
</style>

<!-- code folding -->


<style type="text/css">

#TOC {
  margin: 25px 0px 20px 0px;
}
@media (max-width: 768px) {
#TOC {
  position: relative;
  width: 100%;
}
}

@media print {
.toc-content {
  /* see https://github.com/w3c/csswg-drafts/issues/4434 */
  float: right;
}
}

.toc-content {
  padding-left: 30px;
  padding-right: 40px;
}

div.main-container {
  max-width: 1200px;
}

div.tocify {
  width: 20%;
  max-width: 260px;
  max-height: 85%;
}

@media (min-width: 768px) and (max-width: 991px) {
  div.tocify {
    width: 25%;
  }
}

@media (max-width: 767px) {
  div.tocify {
    width: 100%;
    max-width: none;
  }
}

.tocify ul, .tocify li {
  line-height: 20px;
}

.tocify-subheader .tocify-item {
  font-size: 0.90em;
}

.tocify .list-group-item {
  border-radius: 0px;
}


</style>


</head>

<body>


<div class="container-fluid main-container">


<!-- setup 3col/9col grid for toc_float and main content  -->
<div class="row">
<div class="col-xs-12 col-sm-4 col-md-3">
<div id="TOC" class="tocify">
</div>
</div>

<div class="toc-content col-xs-12 col-sm-8 col-md-9">


<div class="navbar navbar-default  navbar-fixed-top" role="navigation">
  <div class="container">
    <div class="navbar-header">
      <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-bs-toggle="collapse" data-target="#navbar" data-bs-target="#navbar">
        <span class="icon-bar"></span>
        <span class="icon-bar"></span>
        <span class="icon-bar"></span>
      </button>
      <a class="navbar-brand" href="index.html">TALD Contributor Manual</a>
    </div>
    <div id="navbar" class="navbar-collapse collapse">
      <ul class="nav navbar-nav">
        <li>
  <a href="index.html">Home</a>
</li>
<li>
  <a href="steps.html">How to start</a>
</li>
<li>
  <a href="methods.html">Methods</a>
</li>
<li>
  <a href="datasets.html">Datasets</a>
</li>
<li>
  <a href="chapters.html">Chapters</a>
</li>
<li>
  <a href="maps.html">Maps</a>
</li>
      </ul>
      <ul class="nav navbar-nav navbar-right">

      </ul>
    </div><!--/.nav-collapse -->
  </div><!--/.container -->
</div><!--/.navbar -->

<div id="header">


<h1 class="title toc-ignore">How to create a feature dataset</h1>

</div>


<p>Feature datasets for the Atlas are based on descriptive
literature.</p>
<p>To create a dataset you will need the following things:</p>
<ul>
<li>Access to our <a
href="https://drive.google.com/drive/folders/1qN3TpzX-wTxiX2ZX0ZNJ6SledqzLHE5W">drive</a></li>
<li>A <a
href="https://docs.google.com/spreadsheets/d/1HCoEBiz8A2Vd9LUApRLtMANpnsUJN-k6EaXrBYfN0IU/edit#gid=0">dataset
template</a></li>
<li>Our <a
href="https://drive.google.com/drive/folders/14RBA31Cj1MsFSiV4E_ZqTLGOhI1dUfMD">library</a>
of descriptive sources</li>
<li>Our <a
href="https://docs.google.com/spreadsheets/d/1XmOaGjd3ri6uA6yKBNobEfRqkPnsO3ljy_DssM2JrqM/edit?usp=sharing">literature
database</a> with bibliographical information about the sources in the
library</li>
</ul>
<p>Start by creating a folder for your feature in the drive, and upload
your dataset there, even if it is still a work in progress: this makes
it easier to discuss any problems or questions you might have.</p>
<p>You can see an example of a completed feature dataset <a
href="https://docs.google.com/spreadsheets/d/1Emf_uhLgwlLWkqmnCKOJKm2OyyIUt4weq_qqklc_sWo/edit?usp=sharing">here</a>.</p>
<p>For a quick reference on how to collect data, see the <a
href="steps.html">Step-by-step</a> instructions. The instructions below
go into more detail.</p>
<div id="list-of-columns" class="section level1">
<h1>List of columns</h1>
<p>Some of the columns are <strong>required</strong> (without them,
there may be problems with rendering maps and chapters) and some
<em><strong>are not</strong></em>.</p>
<p>Note: if you use an apostrophe (for example, in the name of a village
(<code>Tad-Magitl'</code>) or in transcription), use <a
href="https://en.wikipedia.org/wiki/%27_(disambiguation)">U+0027</a>
<code>'</code>. If you are working in Excel, when loading the table to
the drive, make sure that the apostrophes remain correct.</p>
<ul>
<li><strong>id</strong> - unique number for each row = one observation
in your dataset</li>
<li><strong>family</strong> - language family (optional)</li>
<li><strong>group</strong> - language branch/group (optional)</li>
<li><strong>language</strong> - language name (see <a
href="https://lingconlab.github.io/TALD/languages.html">the following
page</a> and <a
href="https://raw.githubusercontent.com/LingConLab/TALD/refs/heads/master/data/tald_villages.csv">this
dataset</a> for the details)</li>
<li><strong>idiom</strong> - the name of a language variety; descriptive
sources provide information on specific dialects or village varieties of
languages, and we aim to be as precise as possible about where our
information comes from; this also means that if a source says: “in
dialect X, the same form is used”, you can add this as an observation to
your dataset. (see <a
href="https://lingconlab.github.io/TALD/languages.html">the following
page</a> and <a
href="https://raw.githubusercontent.com/LingConLab/TALD/refs/heads/master/data/tald_villages.csv">this
dataset</a> for the details)</li>
<li><strong>type</strong> - specifies whether the idiom is a village
variety, a dialect spoken in multiple villages, or a standard language;
please use our standard names and type classifications.</li>
</ul>
<blockquote>
<p>You can search for the name and type of a certain idiom in <a
href="https://raw.githubusercontent.com/LingConLab/TALD/refs/heads/master/data/tald_villages.csv">the
East Caucasian villages dataset</a>. Sometimes the information on which
idioms are described and where the data has been collected is given at
the beginning of the source, so we recommend to search for this
information there.</p>
</blockquote>
<ul>
<li><strong>genlang_point</strong> - for our maps showing one datapoint
per language we need to choose which datapoint (in case we have multiple
points per language) is representative and will thus be showed on this
map. For this purpose you need to set the appropriate row in this column
to <em>yes</em> (no more than one per language), and set all other
observations for the same language to <em>no</em>; see also <a
href="philosophy.html#current_approach">Methods - Current approach</a>.
The full list of languages can be found <a
href="https://lingconlab.ru/tald/languages.html">here</a>.</li>
<li><strong>map</strong> - in some cases there are multiple observations
for one idiom (e.g. one frequent suffix and a more marginal one to
express the same meaning). On the map we can show <em>only one value per
datapoint</em>, so you can use this column to set information you want
to see on the map to <em>yes</em> and everything else to
<em>no</em>.</li>
</ul>
<blockquote>
<p>One value = one row in the dataset. If you have multiple values for
one idiom, create two rows for this idiom, each with a unique id. The
general rule of thumb for the <strong>genlang_point</strong> column is 1
“yes” per language, for <strong>map</strong> it is 1 “yes” per
idiom.</p>
</blockquote>
<ul>
<li><strong>chapter</strong> - the name of your chapter</li>
<li><strong>feature1</strong> - the name of the feature: the chapter <a
href="https://lingconlab.ru/tald/evidentiality_tense_map.html">Evidentiality
in the tense system</a>, for example, has two features:
<em>Evidentiality as a meaning of the perfect</em> and <em>Evidentiality
in the tense system</em>. The name of each feature should be
capitalized. The content of <strong>feature1</strong> will be used as a
title for your map.</li>
<li><strong>value1</strong> - the relevant values of a specific feature
(e.g. attested / not attested). Try not to use too many values for the
feature. The more values there are, the more difficult it is to perceive
the final map.</li>
</ul>
<blockquote>
<p>Maps are generated based on the <strong>value1</strong> column. If
you want to show the distribution of multiple parameters, please name
further columns <strong>value2</strong>, <strong>value3</strong>, etc.,
and accordingly: <strong>feature2</strong>,
<strong>feature3</strong>.</p>
</blockquote>
<ul>
<li><p><strong>source</strong> - reference to the source you consulted
(see <a href="#literature-references">Literature references</a>
below)</p></li>
<li><p><strong>page</strong> - relevant page in the source</p></li>
<li><p><em><strong>comment</strong></em> - in this column you can “pour
out your soul” in the words of G.A. Moroz: add any kind of thought on an
observation or the source it appears in. Keep in mind, however, that
anything you write here will be visible to users of the Atlas. So please
write your comments in English, and make them clear and
informative</p></li>
<li><p><em><strong>form</strong></em> - what the phoneme / morpheme /
construction / lexeme looks like in <a
href="#transcription">Caucasiologist transcription</a></p></li>
<li><p><em><strong>example_as_in_source</strong></em> - original
transcription of the example</p></li>
<li><p><em><strong>example</strong></em> - example of how the form is
used (if applicable) in <a href="#transcription">Caucasiologist
transcription</a> with morpheme boundaries</p></li>
<li><p><em><strong>translation_as_in_source</strong></em> - original
translation of the example</p></li>
<li><p><em><strong>translation</strong></em> - your own English
translation of the example in case the source was in Russian or you
dislike the original translation for some reason</p></li>
<li><p><em><strong>gloss</strong></em> - glosses for the example. Please
follow the <a
href="https://www.eva.mpg.de/lingua/pdf/Glossing-Rules.pdf">Leipzig
glossing rules</a> where possible. This includes unifying glosses from
the original sources if necessary. Format the non-lexical glosses in
CAPS.</p></li>
<li><p><em><strong>example_source</strong></em> - reference to the
source of the example</p></li>
<li><p><em><strong>example_page</strong></em> - page reference for the
example</p></li>
<li><p><em><strong>example_comment</strong></em> - any kind of comment
you would like to add regarding the example</p></li>
<li><p><strong>contributor</strong> - your name in English, so we know
how to properly credit your work</p></li>
<li><p><strong>date</strong> - the date on which you submitted your
table; edits of the table after its first publication on the website
will receive a new date stamp accordingly.</p></li>
</ul>
</div>
<div id="literature-references" class="section level1">
<h1>Literature references</h1>
<p>When you add a reference to your dataset, check if it is already
listed in the <a
href="https://docs.google.com/spreadsheets/d/1XmOaGjd3ri6uA6yKBNobEfRqkPnsO3ljy_DssM2JrqM/edit?usp=sharing">literature
database</a>. If yes, copy the <strong>bibtexkey</strong> of the
reference from the database to the <strong>source</strong> column in
your table.</p>
<blockquote>
<p>A <strong>bibtexkey</strong> is a unique identifier for a source
which allows us to easily cite sources across the Atlas.</p>
</blockquote>
<p>(You can find our <a
href="https://docs.google.com/spreadsheets/d/1XmOaGjd3ri6uA6yKBNobEfRqkPnsO3ljy_DssM2JrqM/edit?usp=sharing">library</a>
of descriptive sources here.)</p>
<p>In case you used multiple sources for one row / observation, separate
the keys with a semicolon <strong>and space</strong> (<strong>;
</strong>), and do the same with the page numbers in the adjacent
column.</p>
<p>If you refer to multiple page ranges from one source, separate them
with a comma.</p>
<p>If the entire source was relevant, for example because it was a paper
devoted to your topic, or because you read the whole grammar and the
feature is not mentioned anywhere, indicate NA in the page column.</p>
<table>
<thead>
<tr class="header">
<th>source</th>
<th>page</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>khalilova2009; khalilova2011</td>
<td>221, 234–239; NA</td>
</tr>
</tbody>
</table>
<p>In the example above, pages 221 and 234-239 from
<code>khalilova2009</code> have relevant information about the feature,
while the paper <code>khalilova2011</code> was consulted/is relevant in
its entirety.</p>
<p>If the source of the information is a personal conversation, it is
necessary to indicate the name of the source with a note
<code>p.c.</code> for example <code>Santa Claus, p.c.</code>.</p>
<div id="adding-new-literature" class="section level2">
<h2>Adding new literature</h2>
<p>If you use a source which is not in our database yet, you will have
to add it by submitting a <a
href="https://docs.google.com/forms/d/e/1FAIpQLSfekbCiSi5TVtJDAWcAzIajkwYyoR8WjRJ1tjkt0QS6kdkIEA/viewform?usp=sf_link">form</a>
with the necessary information.</p>
<blockquote>
<p>Russian resources are listed in Cyrillic script with a translation in
English of the <strong>title</strong> and <strong>booktitle</strong>
fields.</p>
</blockquote>
<p>The <strong>bibtexkey</strong> for a source is constructed as
follows:</p>
<p><code>khalilova2009</code><br />
surname (Latin script, lower case letters) + year</p>
<p>If there are two authors, use both surnames, cf. Chumakina &amp;
Corbett (2008) becomes <code>chumakinacorbett2008</code>. For sources
with more than two authors, write down only the surname of the first
author followed by <em>et al</em>,
e.g. <code>alekseevetal2008</code>.</p>
<p>In case a different resource by the same author and from the same
year is already present in the <a
href="https://docs.google.com/spreadsheets/d/1XmOaGjd3ri6uA6yKBNobEfRqkPnsO3ljy_DssM2JrqM/edit?usp=sharing">literature
database</a>, add a keyword <em>following</em> the year,
e.g. <code>bokarev1949</code> / <code>bokarev1949avar</code>.</p>
<p><strong>For unpublished sources</strong> use the surname followed by
the word draft, and the year in which the manuscript was produced or
when it was expected to be published, for example
`creisselsdraft2020’.</p>
<blockquote>
<p>The <strong>‘author’</strong> field should be filled as follows: last
name, name and (if present) the first letter of the patronymic or second
name, for example: <em>Абдуллаев, Сайгид Н</em>. If the source has more
than one author use <em>and</em> (in English): <em>Абдуллаева, Айшат З.
and Гаджиахмедов, Нурмагомед Э. and Кадыраджиев, Калсын С.</em> etc. If
the source does not specify the full names, try to find them on the
Internet rather than using initials.</p>
</blockquote>
<p>For city names in the <strong>‘address’</strong> field use English
names, e.g. <em>Moscow</em>, not <em>Москва</em>.</p>
<p>Don’t forget to upload a copy of the source to the appropriate folder
in the <a
href="https://drive.google.com/drive/folders/14RBA31Cj1MsFSiV4E_ZqTLGOhI1dUfMD?usp=sharing">library</a>
using the <strong>bibtexkey</strong> as filename.</p>
</div>
</div>
<div id="transcription" class="section level1">
<h1>Transcription</h1>
<p>Some general principles for transcription:</p>
<ul>
<li>we mostly follow IPA conventions but with a few notable exceptions:
<ul>
<li>ts = c, ʃ = š, tʃ = č, tɬ, tɬ’ = ƛ , ƛ’, dʒ = ǯ , ʒ = ž</li>
<li>nasalization is indicated with a tilde (~) above the vowel: aⁿ &gt;
ã</li>
<li>except diphtongs, because they would require double tildes, which
looks pretty afwul: ũ̃̃o (in the source code these are two vowels with a
tilde above it side-by-side)</li>
<li>gemination as well as long vowels are indicated with a lengthmark ː
(triangles, not dots): чч &gt; čː for consonants, ō &gt; oː for
vowels</li>
</ul></li>
<li><a
href="https://docs.google.com/spreadsheets/d/1KYV1yOettrVlsv2HFqpL_inoGCRmOyzmBoX10Ku4Oio/edit#gid=1009521071">here</a>
is a table with all of the phonemes attested in the languages of our
sample, transcribed in IPA (column <strong>phoneme</strong>); how to
transcribe them for the atlas (column <strong>TALD</strong>), and how
they are represented in different idioms and sources (all other
columns). If you click on a column, you can view the bibtexkey of the
source (in addition to the language and idiom). This also means that if
you have the bibtexkey of a grammar, you can quickly find the
corresponding phoneme and transcription.</li>
</ul>
</div>
<div id="help" class="section level1">
<h1>Help</h1>
<p>For any general questions about data collection or the library, you
can always contact Chiara.</p>
<p>If you have a more specific question about your feature, please also
contact Chiara, and she will connect you with an expert consultant for
your feature.</p>
</div>


</div>
</div>

</div>

<script>

// add bootstrap table styles to pandoc tables
function bootstrapStylePandocTables() {
  $('tr.odd').parent('tbody').parent('table').addClass('table table-condensed');
}
$(document).ready(function () {
  bootstrapStylePandocTables();
});


</script>

<!-- tabsets -->

<script>
$(document).ready(function () {
  window.buildTabsets("TOC");
});

$(document).ready(function () {
  $('.tabset-dropdown > .nav-tabs > li').click(function () {
    $(this).parent().toggleClass('nav-tabs-open');
  });
});
</script>

<!-- code folding -->

<script>
$(document).ready(function ()  {

    // temporarily add toc-ignore selector to headers for the consistency with Pandoc
    $('.unlisted.unnumbered').addClass('toc-ignore')

    // move toc-ignore selectors from section div to header
    $('div.section.toc-ignore')
        .removeClass('toc-ignore')
        .children('h1,h2,h3,h4,h5').addClass('toc-ignore');

    // establish options
    var options = {
      selectors: "h1,h2,h3",
      theme: "bootstrap3",
      context: '.toc-content',
      hashGenerator: function (text) {
        return text.replace(/[.\\/?&!#<>]/g, '').replace(/\s/g, '_');
      },
      ignoreSelector: ".toc-ignore",
      scrollTo: 0
    };
    options.showAndHide = true;
    options.smoothScroll = true;

    // tocify
    var toc = $("#TOC").tocify(options).data("toc-tocify");
});
</script>

<!-- dynamically load mathjax for compatibility with self-contained -->
<script>
  (function () {
    var script = document.createElement("script");
    script.type = "text/javascript";
    script.src  = "https://mathjax.rstudio.com/latest/MathJax.js?config=TeX-AMS-MML_HTMLorMML";
    document.getElementsByTagName("head")[0].appendChild(script);
  })();
</script>

</body>
</html>