- there are two pages with id layoutDesc!
- Additions and Varia
- Art Themes
- Attribution of single statements
- Authority files (keywords)
- Bibliographic References
- Binding Description
- Create New Entry
- Critical Apparatus
- 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
- General Structure of Work Records
- Hands Description
- Identifiers Structure
- Images of Manuscripts for editions
- Manuscript Contents
- Manuscript Description
- Manuscript Physical Description
- Named Entities
- Narrative Units
- Object Description
- Place or Repository
- Relative Location
- Roles and roleNames
- Seals Description
- Some useful how-to for personal workspace set up
- Stand-off annotations with Hypothes.is
- Standardisation of transcription from Encyclopaedia Aethiopica
- State and Certainty
- Statements about persons
- Summary on the Use of @ref and @corresp
- Team IDs
- Text Encoding
- Transliteration Principles
- Validation process
- Works Description
- Zotero Bibliography Guidelines
- titleStmt of Manuscript Records
This record contains information about a single individual, including names, occupation, nationality, birth, death, residence, etc.
It can be expanded with much more information, following TEI guidelines for person
The elements of a person's record constitute in their entirety a brief biographical sketch of the record's subject. It is therefore not necessary to
limit the description of the person's life to a single element. Instead, all information should be encoded at the appropriate place in the record,
We usually assign n1 to the standard name in Fidal, and point with
@corresp to that for transliteration and translations of the same.
<persName>↗s will have other IDs, which can be anything which is a valid
@xml:id but better if the are in the format 'n\d+'.
If you want to add a typical spelling which is used to search a name, like in https://github.com/BetaMasaheft/Documentation/issues/506, the safest place to add it so that it is indexed without affecting the actual content of the entry is in a new teiHeader//titleStmt/title
You can also use
@type with value main to further specify what the label name of the person should be.
This is of course redundant when the
<persName>↗ you assign this attribute would be already the one picked by the titles rules, which are in order of
<persName[@type = 'main']>↗
<persName[@corresp = '#n1'][@xml:lang = 'gez']>↗
<persName[@corresp = '#n1'][@xml:lang = 'en'][@type = 'normalized']>↗
<persName[@corresp = '#n1'][@xml:lang[not(. = 'en')][not(. = 'gez')]]>↗
Changing the IDs to arrive at a certain visualization is deceptory as in the following example, where
The correct way to do this is
which will print in the application 'Cyprian of Antioch' instead of the usual first candidate 'Qoṗrǝyānos', the normalized transcription of the name in Fidal.
Sometimes it is difficult to distinguish between the birth name and given name.
The name given at the time of birth, is encoded as the a
<persName>↗ with an attribute
@type with value birth.
However, there are exceptions where a person has been forced to change his or her birth name to another name for various reasons.
In this case a new name should be given to a person with
In our person records there are persons who have both a birth name and a given name.
Here a typical example is a woman named Aster Gānnoo, who was an Oromo pioneer who
worked with Onesimos Nasib on the translation of the Bible into Oromo. Her Oromo name,
which she had got from her parents, was called ሰልባን፡ but later she changed her name to አስቴር፡. In this case, we mark ሰልባን፡ as birth name where as አስቴር፡ as a given name.
Surname and Forename
<forename>↗ only for European names. For other names
you can use
<genName>↗ (e.g. for the ordinal in the name of a
king) or simply
<persName>↗ you can give a
For international saints and biblical figures, the English name should be used. "Saint" as a title should be spelled with a capital and can be abbreviated St (without dot)
If the name contains a role, please tag it as
<roleName>↗ and add a
Also the encoding in the first example above is correct, althoug this second method has been preferred.
For Saints you might wish to record the commemoration dates. Please follow the following example. It is always preferable to include the source for the date (Sǝnkǝssār, Dǝggwā, EAe...).
Epithets should be recorded as
<addName type='epithet'>↗ and should have their
@xml:id with a chosen value. Assuming the
@xml:id is in this case "SaviourOfTheWorld" ID to be copied
there will be the like 'PRS5684JesusCh#SaviourOfTheWorld'
Unknown or incomplete names
If the name of a person is only partly attested in a manuscript,
<persName>↗ in the person record
should only contain the attested part of the name or be normalized. It
should not be marked up in any way. Mark up should instead be carried
out in the text of the manuscript which contains this name. Note that
it is not necessary to create a record if there is not enough
information available on the person to ensure the record's
Information about this person
<floruit>↗ contains the date of the major active years of the record's subject. The paragraphical information given in
<floruit>↗ does not aim at describing
the whole life of the person in question, but focusses on what they have done in their active years. For instance, for metropolitans, kings etc. it would usually encompass the years between
their appointment and death or replacement. See for example ʾAbbāy Habta Ṣǝyon:
<occupation>↗ can take
You can also use multiple
<occupation>↗ elements and add
to assign the occupation to a period. Also only one of
the two is OK. The use of
should be restricted to scholars involved in the study of
Ethiopian manuscripts. All persons whose records contain
are displayed on the homepage. Try to limit the use of
<occupation>↗ to actual occupations.
If you are unsure about whether some information on a person
should be added in
a new issue. "Angel", for instance, is not an
occupation, but can be added to the record as a keyword:
In similar way,
<occupation type="ruler">↗ refers specifically an occupation of a king or a queen or
in the contemporary system of political administration can it be a president (head of the state) or prime minister (in the parliamentary form of government).
Therefore, in this case
<occupation type="ruler">↗ uses for all Ethiopian kings, while
refers largely a person whose occupation belongs to the category of political but he/she can be a ruler
(governor of a province), courtier and other political posts.
It also entails the various occupations of medieval civil offices of the Christian kingdom of Ethiopia.
<faith>↗ you will find a list of values
<person>↗ to declare the authority file. Prefer
Wikidata if an item is present, otherways use VIAF.
If you want to give extremes of the date also in
@notAfter please follow
guidelines for date. When the date is given as a value and no
further information is provided, it is not necessary to repeat the
dating in the content of the element:
<death when="1636" evidence="internal">↗
is sufficient. However, if the element contains text, the value will
not be visualized. The date should therefore be included explicitly in
the content as in this example from Yamāna Krǝstos:
Each relationship should be listed separately in a
<relation>↗, even if the same relationship exists
between this and more than one other entity.
@name contains the name of the relation.
Allowed values are those in the
Ontology. you can filter them out in oXygen typing snap: in the
@active should contain the
@xml:id of the
@passive should contain the IDs
of the related persons, separated by a space
As usual all elements can take a
The relationship between a work and its subject is expressed in the person record:
For distinct groups of people as an abstract notion (so a
"specific group of monks", but not "friary" or
"family") we use a record in TEI which is the same as that
for a person, but contains a
<personGrp>↗ in the
listPerson, with the persNames of the group. Relations should then be
used to provide evidence for members of this group, which can be fixed
or flexible. The members of the group can be indicated in the group
record by using snap:Group, however, it is sufficient to include the
relation saws:isMemberOf in each individual person record of members
of the group.
Members of the group should have a relation saws:isMemberOf linking to the group record. This is valid for example for monks belonging to the orders of Takla Hāymānot, Sāmuʾel of Waldəbbā or ʾEwosṭātewos. In a similar way, various bodies of military regiments are also be represented as
Revisions of this page
- Pietro Maria Liuzzo on 2018-04-30: first version of guidelines from Wiki
- Dorothea Reule on 2018-05-23: Added title priorities
- Dorothea Reule on 2018-07-06: Added use of floruit