Back to top: Input
File structure
Each input file is a plain ASCII file, that can be produced with any word editor, without any formatting.
The label includes four elements, the first three separated by a hyphen, thus for example: CAR-ZB415-rL.d.
- The identifier for this particular project (the program is used for other projects as well), which in this case is CAR
- The date, according to an internal convention (ZB is the code for 2017, followed by a single character for the month and a double digit for the day) – in our example, ZB415 for April 15, 2017. For all the year codes, see on urkesh.org
- The initials of the author, according to a convention determined by the editors – in our example rL for Laerke Recht.
- The extension "d" (for database), preceded by a period.
Hyperlinks are enclosed by < >, e.g. , <Themes/stratigraphy.htm>stratigraphy</a>* which yields <a href=”Themes/stratigraphy.htm”>stratigraphy</a>
Entries relating to the bibliography or the notes can be entered together in the same input file.
Back to top: Input
Roster
The Roster identifies the variables that are used as codes to define each entry in a given input file. At this point, the program processes only bibiiographical entries and notes.
Entries highlighted in yellow are headers: everything that follows, until the next header, refers to it.
Each record is introduced by a code followed by a space, as shown in the list below. If a record contains more than one paragraph, then each successive paragraph is introduced by a tab.
code definition example
; notes disregarded by program
ID identifier for bibliographical entries Adams&Adams1987Purpose AU author Y year T title P publication details NR reference to note 13.5.3 S summary SA summary author SD summary date
NOTES identifier for notes 13.5.3 NT text of note NA note author ND note date
Back to top: Input
Text formatting
- //word// for italics: word
- ^^word^^ for bold: word
- ##word## for bold italic: word
- an actual tab for five non-breaking spaces
- *!word!* for a word that is to be included in the indices
- **!word!** for a word that is to be included in the indices, but is not to be given in the text
Back to top: Input
Sample input file for bibliography
In the following example, codes and formating marks are highlighted only for ease of reference.
ID Arakawa&al2015WineGlassShape AU Arakawa, Takahiro //et al//. Y 2015 T "A Sniffer-Camera for Imaging of Ethanol Vaporization from Wine: The Effect of Wine Glass Shape" P in //Analyst// 140.8, pp. 2881-2886 NR 16.3.2 S In modern society, certain *!vessel shapes!* are associated with specific contents (e.g. wine from a wine glass, tea from a mug/cup etc.), and we may even feel that colour influences the experience of a food or drink.**!classification!** This is usually believed to be culturally determined or a kind of 'optical illusion', but this study provides some indication that science can at least partially support our intuitions. ; indicate more specifically why this is relevant to CAR SA rL SD July 2016
Here is the output as it appears in the Arakawa &al 2015 Wine Glass Shape (hyperlinks have been added as needed, and items marked with !-! or !-! have been entered in the proper place in the indices):
Arakawa, Takahiro et al.
2015 "A Sniffer-Camera for Imaging of Ethanol Vaporization from Wine: The Effect of Wine Glass Shape"in Analyst 140.8, pp. 2881-2886. 16.3.2
Back to top: Input
Sample input file for notes
NOTES 1.1.5 Structure a. On the "fashion" of *!structuralism!* see Caws 1997 Structuralism b. The expression "a *!long argument!*" was dear to *!Darwin!*... c. A similar idea of the 'construct' of *!data!* can be found in Roskams 2001 Excavation. NA rL ND February 2014 d. For a problematisation of the relationship between 'experts' and public **!public outreach!** and the hidden hierarchies and territorial boundaries implicated, see Karlssonandgustafsson 2006 Heritage Clans. NA rL ND October 2014
Back to top: Input