- ab
- abbr
- acquisition
- add
- additional
- additions
- antiphon
- app
- bibl
- binding
- bindingDesc
- catDesc
- category
- cb
- Certainty
- change
- choice
- cit
- citedRange
- collation
- collection
- colophon
- condition
- country
- creation
- custEvent
- date
- decoDesc
- decoNote
- del
- depth
- desc
- dim
- dimensions
- div
- editor
- ex
- expan
- explicit
- facsimile
- faith
- filiation
- foliation
- foreign
- gap
- geo
- graphic
- keywords
- handDesc
- handNote
- handShift
- height
- hi
- history
- idno
- incipit
- item
- l
- language
- layout
- layoutDesc
- lb
- lem
- list
- listApp
- listBibl
- listPerson
- listRelation
- listWit
- locus
- material
- measure
- msContents
- msDesc
- msIdentifier
- msItem
- msFrag
- msPart
- nationality
- notatedMusic
- note
- objectDesc
- occupation
- orig
- origDate
- origin
- origPlace
- p
- pb
- persName
- person
- personGrp
- physDesc
- place
- placeName
- provenance
- ptr
- q
- quote
- rdg
- ref
- region
- relation
- repository
- roleName
- rubric
- seal
- sealDesc
- seg
- settlement
- signatures
- source
- space
- subst
- summary
- supportDesc
- supplied
- surrogates
- TEI
- term
- textLang
- title
- unclear
- watermark
- width
- witness
- active
- ana
- assertedValue
- atLeast
- atMost
- cRef
- calendar
- cause
- cert
- color
- columns
- contemporary
- corresp
- defective
- dur
- evidence
- facs
- form
- from
- hand
- href
- ident
- key
- n
- name
- new
- notAfter
- notAfter-custom
- notBefore
- notBefore-custom
- part
- passive
- pastedown
- place
- reason
- ref
- rend
- rendition
- resp
- role
- sameAs
- script
- source
- subtype
- target
- to
- type
- unit
- url
- value
- when
- when-custom
- who
- wit
- writtenLines
- xml:base
- xml:id
- xml:lang
- @source
- Additional
- Additions and Varia
- Aligning transliteration and morphological annotations with Alpheios Alignment Tool
- Art Themes
- Attribution of single statements
- Authority files (keywords)
- Bibliographic References
- Binding Description
- Canonicalized TEI
- Catalogue Workflow
- Collation
- Colophons, Titles and Supplications
- Contributing sets of images to the research environment
- Contributing to the research environment
- Corpora
- Create New Entry
- Create a new file, delete existing, deal with doublets
- Critical Apparatus
- Critical Edition Workflow
- Dates
- Decoration Description
- Definition of Works, Textparts and Narrative Units
- Documentary Texts
- Dubious spelling
- Editing the Schema
- Editing these Guidelines
- Editions in Work Records
- Entities ID structure
- Event
- Figures and Links to Images
- General
- General Structure of Work Records
- Groups
- Hands Description
- History
- Identifiers Structure
- Images
- Images of Manuscripts for editions
- Inscriptions
- Keywords
- La Syntaxe du Codex
- Language
- Layout
- Letters
- Linking from Wikidata to the research environment
- Manuscript Contents
- Manuscript Description
- Manuscript Physical Description
- Manuscripts
- Named Entities
- Narrative Units
- Object Description
- Person
- Place or Repository
- Places
- References
- References to a text and its structure
- Referencing parts of the manuscript
- Relations
- Relative Location
- Repositories
- Revisions
- Roles and roleNames
- Scrolls
- Seals Description
- Setup
- Some useful how-to for personal workspace set up
- Spaces
- Stand-off annotations with Hypothes.is
- Standardisation of transcription from Encyclopaedia Aethiopica
- State and Certainty
- Statements about persons
- Structure
- Summary on the Use of @ref and @corresp
- TEI
- Taxonomy
- Team IDs
- Text Encoding
- Training Materials
- Transcriptions with Transkribus
- Transformation
- Transliteration Principles
- Users
- Using Xinclude
- Validation process
- Workflow
- Works
- Works Description
- Zotero Bibliography Guidelines
- titleStmt of Manuscript Records
Places
Please read the content at the following links before starting:
The information contained in this page is valid both for the encoding of place and repository records, see also Place or Repository.
This example record contains information about a single place, at
whatever granularity. It is thus important to state relationships with
other places and typologies when possible , using <relation>
↗ and @sameAs
.
Place records can be expanded with much more information, following the TEI guidelines for the element place.
<text>
<body>
<listPlace>
<place type="RegionalState" sameAs="wd:Q200127">
<placeName xml:id="n1" xml:lang="am">ብሔራዊ፡ ክልላዊ፡ መንግሥቲ፡ ትግራይ፡</placeName>
<placeName corresp="#n1" xml:lang="am" type="normalized">Bǝḥerāwi Kǝllǝlāwi Mangǝśti
Tǝgrāy</placeName>
<placeName corresp="#n1" xml:lang="en">Tǝgrāy National Regional State</placeName>
<placeName xml:id="n2" xml:lang="ti" type="alt">ትግራይ፡</placeName>
<placeName corresp="#n2" xml:lang="ti" type="normalized">Tǝgrāy</placeName>
<placeName xml:id="n3" xml:lang="am" type="alt">ትግሬ፡</placeName>
<placeName corresp="#n3" xml:lang="am" type="normalized">Tǝgre</placeName>
<state type="existence" notBefore="1991"></state>
<country ref="LOC3010Ethiop"></country>
<location source="#Smidt">
<geo>14.1666 38.8333</geo>
<height>1975 m</height>
</location>
<listBibl type="secondary">
<bibl xml:id="Smidt">
<ptr target="bm:Smidt2010EnAeTegray"></ptr>
</bibl>
<bibl>
<ptr target="bm:MantelNiecko2003EnAeAdministrative"></ptr>
</bibl>
</listBibl>
<note>
<date type="foundation" notBefore="1991">1991</date>
<ab type="history">Tǝgrāy National Regional State was created in 1991 following a
radical reshaping of the historical Tǝgrāy province and the merger of diverse
historical northern provinces.</ab>
<ab type="description">Tǝgrāy borders with <placeName ref="LOC2991Eritre">Eritrea</placeName> to the north, <placeName ref="wd:Q1049">Sudan</placeName> to the west, <placeName ref="LOC1426Amhara">ʾAmhārā</placeName> kǝllǝl to the south and <placeName ref="LOC1274Afar">ʿAfār</placeName> kǝllǝl to the east. Its national language is <persName ref="ETH2126Tegren">Tǝgrǝññā</persName> and its capital is <placeName ref="LOC4545Maqala">Maqala</placeName>. Although the state was originally
divided into four zones, in <date cert="medium">2005</date> these were
increased to six: <placeName ref="LOC6583WestTegray">Western Tǝgrāy
Zone</placeName>, <placeName ref="LOC6653EastTegray">Eastern Tǝgrāy
Zone</placeName>, <placeName ref="LOC6654CentralTegray">Central Tǝgrāy
Zone</placeName>, <placeName ref="LOC6655SudTegray">Southern Tǝgrāy
Zone</placeName>, <placeName ref="LOC6656NWTegray">North-Western Tǝgrāy
Zone</placeName>, <placeName ref="LOC6657SETegray">South-Eastern Tǝgrāy
Zone</placeName>. Tǝgrāy presents a rich cultural heritage consisting of
churches, monasteries and other religious places, both Christian and Islamic:
manuscript collections; land charters; inscriptions; etc. </ab>
</note>
</place>
</listPlace>
</body>
</text>
Example 1
New records
Before creating new entities for places like Stuttgart, Paris, London, etc. which unlike all repositories are very much unlikely to receive specific descriptions with the scope of Ethiopian Literature and Manuscript Culture, use external links to Wikidata IDs in the text, e.g.
<placeName ref="wd:Q649"></placeName>
Example 2
and in an eventually already existing place record or repository record, you can use the same Wikidata values
as follows in the same way as above for <settlement>
↗, <region>
↗ and <country>
↗.
<place type="city" sameAs="wd:Q649">
<placeName xml:id="n1" xml:lang="ru">Москва</placeName>
<placeName corresp="#n1" xml:lang="en">Moscow</placeName>
<country ref="wd:Q159"></country>
<region ref="wd:Q649"></region>
</place>
Example 3
If you are already adding the wikidata ID, it would be very helpful if you could add the BM ID to wikidata in the same workflow. To do this, you only need to have a wikidata account, see wikidata.
You are not allowed to add a @ref
in <placeName>
↗ or <persName>
↗ in a person or place record (it would not make that much sense either).
Alignment
Use @sameAs
inside <place>
↗ to declare
the authority file. Prefer Wikidata if an item is present, otherwise
use geonames.
<place type="region" sameAs="wd:Q2894614">
<placeName xml:lang="gez" xml:id="n1">ወገራ፡</placeName>
<placeName xml:lang="gez" corresp="#n1" type="normalized">Wagarā</placeName>
</place>
Example 4
GN ID number should use a prefix "gn:".
Do not add @xml:lang
if you do not know the language in which the name is attested,
prefer not to say anything instead of defaulting on a possibly untrue value.
@type
contains a value from the
controlled
list of Qualifiers .
Coordinates
Coordinates are used to display the place on a map and can be obtained from OpenStreetMap, for example, adding a pointer for a place there.
Coordinates must provide latitude longitude and be separated only by one white space.
<geo>14.308833 39.378683</geo>
Example 5
For regions, areas, and all polygons, use <geo rend="polygon">
↗
using one line for each point. Please do not add spaces at the
beginning and end of the series. You can draw your polygon with this
tool and copy-paste directly
from there. Please take care to remove the commas.
<location>
<geo rend="polygon">38.40271 12.9804713
38.2626343 13.0580747
38.1170654 13.1463524
37.9138184 13.1543761
37.7737427 13.0901794
37.7160645 12.9885004
37.6858521 12.8707149
37.5979614 12.7421585
37.6446533 12.6483782
37.6693726 12.5438397
37.7380371 12.3909763
37.8506470 12.3426849
37.9934692 12.2460756
38.1692505 12.2111802
38.4439087 12.2809664
38.4521484 12.6162171
38.4851074 12.7796608
38.4082031 12.9831477
38.40271 12.9804713</geo>
</location>
Example 6
Administrative location
If you want to give other administrative location information, use
<settlement>
↗. Add one settlement for each set of
information, but only one if there is only one set. Please do not
remove text if it is there, simply mark it up as in the following
example.
<settlement type="province" ref="LOC5932Tegray"></settlement>
<settlement when="2009-11-16" ref="LOC1564ASbiW" type="warada"></settlement>
<settlement when="2009-11-16" ref="LOC6526Asir" type="qushat"></settlement>
Example 7
Place Names
A full example of how to encode the various possible placeNames is the following:
<placeName xml:id="n1" xml:lang="am">አክሱም፡ ጽዮን፡</placeName>
<placeName corresp="#n1" xml:lang="am" type="normalized">ʾAksum Ṣǝyon</placeName>
<placeName xml:id="n2" xml:lang="gez" type="alt">ማርያም፡ ጽዮን፡</placeName>
<placeName corresp="#n2" xml:lang="gez" type="normalized">Māryām Ṣǝyon</placeName>
<placeName corresp="#n2" xml:lang="en">Mary of Zion</placeName>
<placeName xml:id="n3" xml:lang="gez" type="alt">ገበዘ፡ ጽዮን፡</placeName>
<placeName corresp="#n3" xml:lang="gez" type="normalized">Gabaza Ṣǝyon</placeName>
<country ref="LOC3010Ethiop"></country>
<region notBefore="1991" type="RegionalState" ref="LOC5932Tegray"></region>
<region notAfter="1974" type="Province" ref="LOC6556Tegre"></region>
Example 8
All <placeName>
↗s can take an @xml:id
if it is needed for referencing,
following the above example. i.e. nothing prevents Mary of Zion to
have an @xml:id
="n5" AND @corresp
="#n2"
You can enter into <placeName>
↗ a <note>
↗ element
where to describe the denomination more in detail, see, for example,
ʾAdulis
<placeName xml:id="n4" xml:lang="la" type="alt" source="#FattovichMunro">Adulitae
<note source="#Smith"><ref cRef="http://data.perseus.org/citations/urn:cts:greekLit:tlg0363.tlg007.perseus-grc1:4.7">Ptolemy 4.7.8</ref></note><note source="#Epiphanius">
Epiphanius (listing nine kingdoms of the 'Indians', he refers to the Adulites
other then to the Aksumites)</note></placeName>
<placeName xml:id="n5" type="alt" source="#FattovichMunro">WDTT <note source="#FattovichMunro">The geographical lists of the Egyptian 18th
dynasty (<date when="-1450" precision="low">ca. 1450
B.C.</date>)</note></placeName>
Example 9
use this especially if you need to provide specific @source
s for
this name of the place.
On referring to places, please look carefully for available records. e.g.:
- LOC6569Tegray (Tǝgrāy historical province) vs LOC5932Tegray (contemporary regional state)
- LOC6568Amhara (ʾAmhārā historical province) vs LOC1426Amhara (contemporary regional state)
- LOC3577Gondar (Gondar town) vs LOC6554GondarineK (Gondarine Kingdom)
Tābots
For tābots please use an <ab type="tabot">
↗
including the number of the tābots in a <measure>
↗ and <persNames type="tabot">
↗ for
each of the dedicatory persons. Avoid using @type
for other persons
mentioned in the texts.
<ab type="tabot">
<measure quantity="4"></measure>
Tābots of <persName ref="PRS3249Cyriacus" type="tabot">Qirqos</persName>, <persName ref="PRS9684Uriel" type="tabot">Urael</persName>, <persName ref="PRS6819Mary" type="tabot">Mary</persName>, <persName ref="PRS10777Madhane" type="tabot">Madḫane ʿĀlam</persName>
</ab>
Example 10
If a tābot is dedicated to an inanimate entity, use a
<ref>
↗ with appropriate type to point to a
relevant ID, as in
<ref type="authFile" corresp="Masqal">Cross</ref>
Example 11
Syriaca Historical Geography schema alignment
To encode historical places we follow in the above and what follows the Syriaca.org TEI manual for Historical Geography, with some divergences due to our project.
This page is referred to in the following pages
Revisions of this page
- Pietro Maria Liuzzo on 2018-04-30: first version of guidelines from Wiki
- Dorothea Reule on 2018-05-22: Edited and updated examples
- Dorothea Reule on 2019-01-10: Corrected link to repositories, updated Wagarā example, removed outdated sentence