- 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
Decoration Description
Decoration Description Overview
<decoDesc>
↗ contains a description of
the various decorative elements found in a manuscript. If
multiple <decoNote>
↗ elements are present you can provide general
observations in <summary>
↗ using it
directly into <decoDesc>
↗ like in the example below from Paris, Bibliothèque nationale de France, BnF Éthiopien 32. Within this
text simply use <ref>
↗ to refer to each
<decoNote>
↗ or
<locus>
↗ to refer to a folio. If there is
a <note>
↗ about all miniatures and a <note>
↗ about all drawings of a
certain type, then the sentence in description will point to
the <decoNote>
↗s involved.
<summary>
The manuscript’s decorative features are typical of the period. It includes the Eusebian Apparatus
(3+7 arrangement) set under colourful stylized arches and followed by a Tempietto. As the pages
before the beginning of the Gospel of Mark <locus target="#82v"></locus>, Luke <locus target="#127v"></locus>,
and John <locus target="#203v"></locus> contain inventories and notes it is possible that they were originally
intended to receive <ref type="authFile" corresp="AT1013EvaPortrait"></ref>. The miniatures are painted in
the <term key="FirstSolomonicStyle"></term> and recall examples produced between
<date notBefore="1300" notAfter="1450"></date>. The decorations appear to have been painted by the same artist.
</summary>
Example 1
<summary>
↗
can also be used to provide
information about the decorative features of the manuscript
that cannot be given elsewhere. In the above example, the
editor of the
<decoDesc>
↗ believes
that the manuscripts offers
evidence that is relevant to the Art Theme
AT1013EvaPortrait
even though the theme is not included in the work in
question.
DecoNote
Each decorative element in the manuscript is listed in a
<decoNote>
↗ as follows:
<decoNote type="miniature" xml:id="d30">
<locus target="#108v"></locus>
<desc>A miniature of the <ref type="authFile" corresp="AT1008Descent"></ref> in which <persName ref="PRS5684JesusCh"></persName>, who is surrounded by a
<term key="mandorla"></term> and holds a staff <term key="cross"></term>, pulls <persName ref="PRS1385Adam">Adam</persName> out of Sheol.</desc>
</decoNote>
Example 2
Include always a <locus>
↗ with @target
to
identify the position of the decoration.
There should be a ATID for each
subject represented as miniature/drawing in the
manuscript/item when possible (there should also be specific
ATIDs for subjects that cannot be
confidently identified (e.g. Saints on Horseback, Holy Men,
Group of Figures). These latter IDs are to be used only when
identification is not possible using attributes and/or
captions and/or iconography and/or context. For consistency,
when editing miniature and drawing
@type
s in
<desc>
↗ please try to follow,
when possible, the following principles.
- Order: main subject and related iconographic elements; main iconographic features from left to right and from top to bottom; and secondary elements and background.
- Generic References and Bibliographic References are given in the ATID, include only references to: works referring directly to this particular set of miniatures; or works relevant to a particular feature of the specific Art Theme that are not included in the general ATID bibliography.
- Images depicting groups of
individuals/saints will have a specific
ATID but, when possible, each
individual should be identified with the appropriate
<persName>
↗ or<personGrp>
↗ record. - Images depicting generical
geographical features (e.g. trees; mountains) can be encoded
using keywords (
<term>
↗) in the place types section. Towns, areas, etc. can use<placeName>
↗. If a geographical reference is consistently present in a Art Theme, then consider including it in the ATID rather than in the<decoNote>
↗. - Keywords (
<term>
↗) are valuable tools that you can use to provide further information about such features as the style and iconographic elements of a theme (see relevant guidelines page).
Legends and Captions
Miniatures may include:
- legends that illustrate the general subject matter of the miniature;
- shorter captions, a short sentence or a word, that identify some of the Persons/Objects/Actions in the miniature.
Legends should be
provided at the end of <desc>
↗
inside the corresponding
<decoNote>
↗ and use
<q>
↗.
Translations of legends can also be included in a separate <q>
↗ if desired, always including the respective @xml:lang
, as
in this example from DS Ethiop. 1:
<q xml:lang="gez">ዘከመ፡ ባረከቶ፡ እግዝእትነ፡ ለ<persName ref="PRS3827Ephrem">ኤፍሬም፡</persName></q>
<q xml:lang="en">How our Lady blessed Ephrem.</q>
Example 3
Captions should be associated
to the relevant iconographic element using
<foreign>
↗:
<decoDesc>
<decoNote type="miniature" xml:id="d1">
<locus target="#viii"></locus>
<desc>Miniature of <persName ref="PRS5332hezqeyas"></persName> lying at the feet of <persName ref="PRS3417David"></persName>,
identified by the caption <foreign xml:lang="gez">
<persName ref="PRS3417David">ዳዊት፡</persName> ንጉሥ።</foreign>.
<q xml:lang="gez">ዘከመ፡ ተማኅፀነ፡ ንጉሠ፡ <persName ref="PRS5332hezqeyas">ሕዝቅያስ።</persName>
</q>
</desc>
</decoNote>
</decoDesc>
Example 4
Dimensions
If available and desired, the dimensions of painted areas can be given in <dimensions>
↗ in <decoNote>
↗,
as in this example from RDW-005:
<decoNote xml:id="d2" type="drawing" corresp="#pic2">
<desc>Monochrome drawing of a magic square, possibly a <ref type="authFile" corresp="AT1140SealSol"></ref>, but without face.</desc>
<dimensions unit="mm">
<height>75</height>
<width>46</width>
</dimensions>
</decoNote>
Example 5
Miniature Collections
Manuscripts that contain exclusively miniatures and no text receive the keyword miniatureCollection. Any other keywords relevant to these miniatures, such as, for example, Hagiography, can be assigned freely.
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-04-24: stub of page
- Dorothea Reule on 2019-04-26: Added dividers
- Dorothea Reule on 2020-04-07: Added example for translation of legends
- Dorothea Reule on 2021-08-26: Added paragraph on dimensions
You found "dimensions" in 4 entries!
... Dimensions If available and des...
... If available and desired, the dimensions of painted areas can be given in dim...
...nsions of painted areas can be given in dimensions in decoNote, as ...
...nformation about the global dimensions of the object. The value outer for ...
...The value outer for type in dimensions indicates the external d...
...ions indicates the external dimensions, including the board, the ...
... The value leaf for type in dimensions indicates the size of th...
... note linked with corresp to the dimensions element. In this way, me...
... 365 265 Data on leaves dimensions taken from . ...
... Measurements in dimensions should alwa...
..., can be provided in a separate element dimensions and should be given in grammes: ...
... Data on text area and margin dimensions taken from . ...
...ote if known. The first dimensions contains the information about...