- 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
Keywords
Use of keywords
Keywords are used as values of @key
in <term>
↗in many different places in the records. Each keyword has an authority file and an entry
in the taxonomy.
Keywords listed in keywords
Keywords can be listed in <keywords>
↗ in <textClass>
↗ in principle for all record types. You can use one or more of the values
provided for @key
. You can assign as many keywords as needed. The subject keywords
"ChristianLiterature", "IslamicLiterature" and "BetaEsraelLiterature" should be assigned
to all work and manuscript records belonging to these traditions.
<textClass>
<keywords>
<term key="ChristianLiterature"></term>
<term key="Gon"></term>
<term key="Liturgy"></term>
</keywords>
</textClass>
Example 1
It is very useful and important that at least one Period Keyword is assigned to each work and manuscript record.
Each of these is linked to a stable URI provided by Perio.do.
In the following table, they are summarized although they are available in the contextual menu via the schema.
Keyword | Period |
---|---|
PreAks | Pre Aksumite |
Eaks | Early Aksumite |
Aks | Aksumite |
Paks1 | Post Aksumite I |
Paks2 | Post Aksumite II |
Gon | Gondarine |
ZaMa | Zamana Masāfǝnt |
MoPe | Modern Period |
Keywords in manuscript records
This means that it is not necessary to limit the keywords to the principal text, but keywords for any additional or minor texts contained in the manuscript should also be assigned.
Keywords in work records
Always assign a period keyword, using the keywords referring to Ethiopian literary periods only in records belonging to the Ethiopian tradition.
Keywords in person records
Generic information on types of persons is also encoded as keywords. For the difference between person types and occupation, see persons.
<textClass>
<keywords>
<term key="angel"></term>
</keywords>
</textClass>
Example 2
You can also add a @ref
with a URI of one of the values in
the EAGLE Vocabularies for the type of inscription
especially for inscriptions as
in the following example from RIE180.
<keywords scheme="#ethioauthlist">
<term key="Other" ref="https://www.eagle-network.eu/voc/typeins/lod/137" cert="low"></term>
<term key="LegalDocument"></term>
<term key="Aks"></term>
</keywords>
Example 3
Keywords in other parts of the files
You can use <term>
↗ also in other parts of the files where the schema allows it. In the following example term is used in a <decoNote>
↗, other possible uses
are in additions or binding descriptions.
<decoNote type="miniature" xml:id="d1">
<locus target="#2r" facs="f17"></locus>
<desc>
The <title type="complete" ref="LIT1349EpistlEusebius"></title> runs between
<locus from="2r" to="3r"></locus> and is placed under brightly coloured
<term key="arch">arches</term> that rest
on <term key="curtain">curtained</term>
<term key="column">columns</term>.
Several <term key="bird">birds</term> are placed atop the arch. The opening page,
<locus target="#2r"></locus> features a pair of <foreign xml:lang="gez">ጣዎስ፡</foreign>
flanking a <term key="cross">cross</term> and four
<foreign xml:lang="gez">ዱራ፡</foreign> birds.
The following pages feature the <foreign xml:lang="gez">ጠይራት፡</foreign>
birds on arches decorated with <term key="interlace"></term> patterns.
</desc>
</decoNote>
Example 4
Taxonomy and creating new keywords
The values available for @key
have to be included in the taxonomy.
New keywords can be created as needed, but especially when they concern many files or introduce a new way of use should be first discussed in an issue.
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
- Pietro Maria Liuzzo on 2018-05-15: Split into paragraphs and added example
- Dorothea Reule on 2019-07-12: modified structure, small edits