-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathchapters.rmd
62 lines (41 loc) · 4.23 KB
/
chapters.rmd
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
---
title: "How to write a chapter"
output:
html_document:
fig_cap: yes
highlight: tango
smooth_scroll: no
theme: flatly
toc: yes
toc_float: yes
---
```{r setup, include=FALSE}
knitr::opts_chunk$set(echo = TRUE)
```
Each feature dataset is accompanied by an introductory chapter. You can browse the [Atlas](http://lingconlab.ru/dagatlas/features.html) for some examples.
It can be convenient to write a draft in a google doc in your feature folder, but ultimately the text will have to be formatted in `Rmarkdown`. You can download a template for formatting a chapter [here](chapter_template/chapter_template.Rmd) and the cheat sheet [here](chapter_template/chapter_cheatsheet.Rmd).
# Structure of the text
Below is a list of recommended sections and points to address in the text.
### Introduction
- Briefly explains what the feature is
- Gives a general characterization of how it is expressed in East Caucasian
- Gives a general characterization of how it is expressed cross-linguistically
- If applicable: describes how the classification in [TALD](http://lingconlab.ru/dagatlas) differs from [WALS](http://wals.info) (e.g. our chapter on the [Standard of Comparison](http://lingconlab.ru/dagatlas/standard_of_comparison.html) shows more sub-types of spatial comparatives)
- Describes the goal of the text / map in one sentence: "Our goal is to classify the languages of Daghestan according to the type of spatial form used to mark the standard of comparison."
### Results
- Summarizes the different types/values you discovered; types identified in the text should correspond to values shown on the map. If you want to fuse multiple types into one category, be sure to explain this decision in the text.
>**A hypothetical example:**
[Comparative constructions](http://lingconlab.ru/dagatlas/standard_of_comparison.html) are usually based on spatial case forms, which consist of a localization and a directionality. Let's say Chiara only cares about directionality, because differences in localization occur more rarely and do not show an interesting distribution. She can choose to create general categories based on directionality (e.g. essive and elative), and mention in her text that elative includes both super-elative and cont-elative forms.
- Provide examples
- Identify which types are more or less common
### Distribution
- Does the distribution of different types show a genealogical and / or areal signal?
# Literature references
For the chapter, you will have to compile your own list of references using this [table template](https://docs.google.com/spreadsheets/d/1DrNPxHFnCHaUAdFgPzdAhXMJ4nEzl0MvZsTcvcA03EY/edit#gid=0). You can see an example of a completed list of references [here](https://docs.google.com/spreadsheets/d/1e2WS1F9P0Eyp4et99JrH4PDxEQnHk1OcSzV6c3Vl6-I/edit#gid=883415171).
The references should be in [bibtex](https://en.wikipedia.org/wiki/BibTeX) format. You can find a list of entry types and their arguments [here](https://www.bibtex.com/e/entry-types/). Our [literature database](https://docs.google.com/spreadsheets/d/1XmOaGjd3ri6uA6yKBNobEfRqkPnsO3ljy_DssM2JrqM/edit?usp=sharing) is an example of a table of references in [bibtex](https://en.wikipedia.org/wiki/BibTeX) format.
In case you cite a source from our library in your chapter, all you have to do is copy the information from the [literature database](https://docs.google.com/spreadsheets/d/1XmOaGjd3ri6uA6yKBNobEfRqkPnsO3ljy_DssM2JrqM/edit?usp=sharing) to your own table.
When you are done, upload the table with references to your feature folder using the following filenaming convention: name of your feature *_bib*, e.g. **standard_of_comparison_bib**. Note that the column headers should be in uppercase.
The table will be converted to a `.bib` file for the website automatically.
# Pro-tip
Avoid spending a lot of time on formatting examples and compiling lists of abbreviations and references in your google doc draft version. Ultimately you will have to format your text in `Rmarkdown`, which will do a lot of the more annoying work for you.
Don't be scared if you are not very experienced with R: all you need to format a chapter is [R](https://www.r-project.org) + [RStudio](https://www.rstudio.com) and our [chapter template](chapter_template/chapter_template.Rmd).