- 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
Object Description
<objectDesc>
↗ contains all the
information about the object as such. Within the
@form
you should specify one of the available values. The object is further described in <supportDesc>
↗.
For the description of the quires structure, see the page collation.
For the description of the layout, see the dedicated page layout.
Support
In <support>
↗
information about the material support is given.
<support>
<material key="parchment"></material>
</support>
Example 1
In <material>
↗ with @key
enter the value
from the Writing Material taxonomy proposed from the schema.
Oxygen should prompt the values from the schema.
You can also add a @ref
with a URI of one of the values in
the EAGLE Vocabularies for material
and object type especially for inscriptions as
in the following example from RIE 246.
<support>
<material key="stone" ref="https://www.eagle-network.eu/voc/material/lod/138"></material>
<objectType ref="https://www.eagle-network.eu/voc/objtyp/lod/2">Unspecified</objectType>
</support>
Example 2
It is also possible to further describe the material and its characteristics in paragraphic form in a <p>
↗ in <support>
↗,
as in this example from DS Ethiop 5:
<support>
<material key="parchment"></material>
<p>Parchment repairs on <locus target="#23 #26"></locus>. Hole in the parchment on <locus target="#46"></locus>.</p>
</support>
Example 3
Extent
<extent>
↗ contains information about
the global dimensions of the object. The value outer for
@type
in <dimensions>
↗
indicates the external dimensions, including the board, the
cover, and the spine. The value leaf for
@type
in <dimensions>
↗ indicates the size of
the leaf. The leaf from which the measurements have been
taken can be added in a
<note>
↗ linked with @corresp
to the <dimensions>
↗ element.
In this way, measurements of several leaves can be added.
Other values for @type
are possible.
<extent>
<measure unit="leaf">183</measure>
<measure unit="leaf" type="blank">3</measure>
<measure unit="quire">25</measure>
<dimensions type="outer" unit="mm">
<height>370</height>
<width>270</width>
<depth>115</depth>
</dimensions>
<dimensions type="leaf" unit="mm" xml:id="leafdim">
<height>365</height>
<width>265</width>
</dimensions>
<note corresp="#leafdim">
Data on leaves dimensions
taken from <locus target="#6r"></locus>.
</note>
</extent>
Example 4
Measurements in <dimensions>
↗ should
always be given in millimetres, unless the source catalogues provides them otherwise.
You can add more precise information on a range of dimension using
@atLeast
and @atMost
, which will be given priority in the visualization
but, please, add a single valid value as content as in the following example.
<height unit="mm" atLeast="310" atMost="330">320</height>
Example 5
You can also specify which leaves are blank, adding a
<locus>
↗ immediately after the relative
measure.
To record the presence of protective leaves, please use a syntax involving only Arabic numerals, like 3+69+1 to indicate that there are three guard leaves at the beginning and another one at the end.
<measure unit="leaf">3+69+1</measure>
Example 6
Please use only integers in <measure>
↗. For all searching purposes only integers will be used.
Instead of placing your measure around the entire thing which you deem a measure, try a more specific tagging
A + <measure unit="quire">11</measure>
Protection quire + <measure unit="quire">19</measure>
Protection quire + 19 (<measure unit="quire">20</measure>)
Example 7
To indicate the number of strips sewn together to produce a scroll, you can add a <measure>
↗ in a <note>
↗, as in BDLaethf10:
<extent>
<dimensions type="outer" unit="in">
<height>78</height>
<width>5.5</width>
</dimensions>
<note>Consists of <measure unit="strips">3</measure> strips.</note>
</extent>
Example 8
The weight of manuscripts, if known, can be provided in a separate element <dimensions>
↗ and should be given in grammes:
<measure type="weight" unit="g">84</measure>
Example 9
Foliation
Any information available on the foliation of the manuscript can be entered in <foliation>
↗,
as in this example from DS Ethiop. 3:
<foliation resp="DR DN">Foliation in pencil in the middle of the bottom margin.</foliation>
Example 10
If different numbering systems are present in the manuscript, a <list>
↗ of <item>
↗s can be
used. If more than one foliation system is described, it might be useful to indicate which one is followed in the record,
as in this example from
DS Ethiop. 2:
<foliation>
<list>
<item xml:id="fol1">
<locus from="ir" to="84v"></locus>
Foliation in pencil in Eastern Arabic numerals in the lower right corner, from <q xml:lang="ar">١</q> on
<locus target="#ir"></locus> until <q xml:lang="ar">٨٦</q> on <locus target="#84r"></locus>.
</item>
<item xml:id="fol2" resp="DN DR">
<locus from="ir" to="84v"></locus>
Foliation in pencil in the middle of the bottom margin of the folio. This is the foliation used as reference in this record.
</item>
</list>
</foliation>
Example 11
If necessary, it is also possible to refer to more than one foliation in the <msItems>
↗ by adding several <locus>
↗
with @corresp
having the values of the respective @xml:id
s indicated in <foliation>
↗, as in
BnF d'Abbadie 66A:
<msItem xml:id="ms_i1.1.7.2">
<locus from="6va" to="7vb" corresp="#fol1"></locus>
<locus from="213ra" to="213vb" corresp="#fol1"></locus>
<locus from="6va" to="8vb" corresp="#fol2"></locus>
<title type="complete" ref="LIT4032SenkessarS#Mask7Sawiryanos"></title>
<textLang mainLang="gez"></textLang>
</msItem>
Example 12
Condition
You can also add a <condition>
↗
element containing a fully marked-up description of the
condition of the manuscript. Do indicate a general
value from the State of Preservation Taxonomy proposed from the schema for indexing
purposes.
<condition key="deficient"></condition>
Example 13
If no information on the condition of the manuscript is available, the element should be simply not added to the record.
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 2018-06-12: Added mistara example
- Dorothea Reule on 2018-07-06: Added paragraph on scroll strips
- Dorothea Reule on 2019-04-05: Updated foliation paragraph with real examples
- Dorothea Reule on 2020-02-11: Added weight
- Dorothea Reule on 2020-04-17: Added examples to support and foliation
You found "ruling" in 2 entries!
...measurements, punctuation, pricking and ruling, etc., as in this example ...
... Ruling and pricking Within ...
...yout you can also encode information on ruling and pricking using ...
... A misṭāra was used for ruling. ...
...ng. Ruling is partly visible; pricking is visib...
... pricking is visible. Ruling pattern: 1A-1A-1A...
...tly visible (s. 29r). Ruling pricks are mostly visible (s. 20r). ...
... The upper line is written above the ruling. The bottom line i...
... The bottom line is written above the ruling. ...