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