Difference between revisions of "User talk:OCIMCO"
Alhuber1502 (talk | contribs) (→The manuscript contents '''<msContents>''') |
Alhuber1502 (talk | contribs) (→The physical description '''<physDesc>''') |
||
| Line 483: | Line 483: | ||
</physDesc> | </physDesc> | ||
</pre> | </pre> | ||
| + | |||
| + | The physical description '''<physDesc>''' wrapper element subsumes a large number of different aspects generally regarded as useful in the description of manuscripts. These include aspects of the form, support, extent, and quire structure of the manuscript object and of the way in which the text is laid out on the page: the object description ('''<objectDesc>'''); the styles of writing, such as the way it is laid out on the page, the styles of writing, decorative features, any musical notation employed and any annotations or marginalia: the description of hands ('''<handDesc>'''); and discussion of its binding, seals, and any accompanying material: the binding description ('''<bindingDesc>'''). The OCIMCO project uses a combination of approaches in the encoding of the physical description section: it records highly detailed descriptions (where available) in the form of a container section of more specialized elements described below, and less detailed descriptions in the form of a series of free-text paragraphs. | ||
| + | |||
| + | The OCIMCO project makes use of the '''<objectDesc>''' element to group together those parts of the physical description which relate specifically to the text-bearing object, its format, constitution, layout, etc. The <tt>form</tt> attribute is used to indicate the specific type of writing vehicle being described, here a codex. The '''<objectDesc>''' element has two parts: a description of the support, i.e. the physical carrier on which the text is inscribed; and a description of the layout, i.e. the way text is organized on the carrier. The '''<supportDesc>''' (support description) groups elements describing the physical support for the written part of a manuscript, such as a description of the materials which make up the physical support for the written part of a manuscript, the approximate size of a text as stored on some carrier medium specified in any convenient units, | ||
| + | a description of how the leaves or bifolia are physically arranged, the numbering system or systems used to count the leaves or pages in a codex, and a description of the physical condition of the manuscript. In our example the material is indicated with the <tt>@material</tt> attribute of the '''<supportDesc>''' element, the '''<extent>''' element groups both the number of folios and the '''<dimensions>''' of the leaves and of the written text, which have been encoded in cm using the '''<height>''' and '''<width>''' elements. A simple paragraph finally summarizes the overall physical state of a manuscript within the '''<condition>''' element. | ||
==== The history of the manuscript '''<history>''' ==== | ==== The history of the manuscript '''<history>''' ==== | ||
Revision as of 17:13, 21 October 2010
Contents
ABOUT THE OXFORD AND CAMBRIDGE ISLAMIC MANUSCRIPT CATALOGUES ONLINE PROJECT (OCIMCO)
The OCIMCO project aims to greatly improve scholarly access to the valuable Islamic texts held in the Bodleian Library, Oxford, and Cambridge University Library. It is part of JISC's Digital Resources for Islamic Studies programme aimed at opening up access to a wide range of rare and important Arabic manuscripts and Islamic Studies resources.
Although much excellent work has been done in the UK to digitise medieval manuscripts like Psalters, books of hours and bestiaries, Middle Eastern manuscript culture has received less attention, yet UK organisations hold rich and valuable collections and there is great and increasing demand for access to them. The OCIMCO project is using TEI/XML<ref>TEI P5 Guidelines</ref> to create some 10,000 basic manuscript descriptions that will be freely available and searchable online. These basic descriptions will also provide a framework for future enhancements and the inclusion of more details about individual manuscripts.
As the documentation for TEI manuscript description derives from Western manuscript examples, applying these descriptive standards to Islamic manuscripts in a union catalogue present a number of challenges, which are explored in the project documentation presented here.
OCIMCO PROJECT DOCUMENTATION
The TEI's Manuscript Description module makes it possible to provide detailed descriptive information about handwritten primary sources. While the OCIMCO project has initially focussed on the retrospective conversion of existing descriptions and catalogues, it will eventually provide detailed manuscript descriptions that will include digital representations of the manuscripts themselves.
For the purpose of this documentation we have chosen a representative record which will be discussed in detail: MS. Marsh 80, one of over 700 manuscripts belonging to Narcissus Marsh, Archbishop of Armagh and fellow of Exeter College, which the Bodleian received by bequest in 1714. Below is the complete TEI-conformant description of this manuscript:
<TEI xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader xmlns="http://www.tei-c.org/ns/1.0">
<fileDesc>
<titleStmt>
<title>MS. Marsh 80 - OXFORD AND CAMBRIDGE ISLAMIC MANUSCRIPT CATALOGUES ONLINE</title>
<funder>JISC</funder>
<principal>Gillian Evison</principal>
</titleStmt>
<publicationStmt>
<date calendar="Gregorian">[Date when first made available]</date>
<publisher>Bodleian Library</publisher>
<pubPlace>
<address>
<addrLine>Department of Special Collections</addrLine>
<addrLine>Bodleian Library</addrLine>
<street>Broad Street</street>
<settlement>Oxford</settlement>
<postCode>OX1 3BG</postCode>
<addrLine><ref target="http://www.bodleian.ox.ac.uk/libraries/collections">Bodleian Library
</ref></addrLine>
<addrLine><email>oriental@bodleian.ox.ac.uk</email></addrLine>
</address>
</pubPlace>
<idno>OCIMCO</idno>
</publicationStmt>
<sourceDesc>
<msDesc xmlns="http://www.tei-c.org/ns/1.0" xml:id="OCIMCO" xml:lang="eng">
<msIdentifier>
<country>United Kingdom</country>
<region type="county">Oxfordshire</region>
<settlement>Oxford</settlement>
<institution>Oxford University</institution>
<repository>Bodleian Library</repository>
<collection type="main">Oriental Collection<collection type="sub">Marsh
Collection</collection></collection>
<idno>MS. Marsh 80</idno>
<altIdentifier type="other">
<idno>9076</idno>
</altIdentifier>
</msIdentifier>
<msContents>
<msItem>
<author>
<persName xml:lang="ara-Latn-x-lc" type="standard" key="n 80129268"
ref="http://viaf.org/viaf/90058060/">Qumrī, Abū Manṣūr
al-Ḥasan ibn Nūḥ, <date calendar="Gregorian" notBefore="1000"
notAfter="1100">11th cent.</date></persName>
<persName xml:lang="ara">
<surname>بن نوح</surname>
<forename>الحسن</forename>
<addName type="kunyah">أبو منصور</addName>
<addName type="nisbah">القمري</addName>
</persName>
</author>
<title xml:lang="ara-Latn-x-lc">Kitāb al-Ghiná wa-al-muná</title>
<title xml:lang="ara-Latn-x-lc" type="alt">al-Shamsīyah
al-Manṣūrīyah</title>
<title xml:lang="ara">كتاب الغنى والمنى</title>
<title xml:lang="ara" type="alt">الشمسية المنصورية</title>
<note>It is an incomplete copy. The text breaks off at the bottom of
folio 60b in the fifty-first bāb of the first maqālah. A complete
table of contents for the full treatise is given on folios 2a−3a.
Maqālah 1 starts on folio 3a.</note>
<incipit xml:lang="ara">بسم الله الرحمن الرحيم، الحمد لله رب العالمين
والعاقبة للمتقين...قال ابو منصور الحسن بن نوح القمري رحمه الله اني
لم ازل في صباي ومنذ عقلت احب العلوم الطبيعية وينازعني نفسي اليها
وخصوصا علم الطب</incipit>
<explicit xml:lang="ara" defective="true">فانه كثيرا ما ينقطع بذلك
والانكباب على بخار الشراب التي القيت فيه حجارة محماة فان لم ينقطع
فيجب ان يجذب المادة }}التي ينصب الى {{الحنك</explicit>
<note>At the bottom of the page, a different more cursive hand has
written: <foreign xml:lang="ara">والله الهادي الى الطريق تمت
الكتاب</foreign></note>
<listBibl>
<bibl>Golius Sale Cat., med. qu. 12</bibl>
<bibl>UAM 147 entry DCXLII (642)</bibl>
<bibl>NPAE, 590</bibl>
<bibl>GAL I 239</bibl>
<bibl>GAS III 319</bibl>
</listBibl>
<textLang mainLang="ara">Arabic</textLang>
</msItem>
</msContents>
<physDesc>
<objectDesc form="codex">
<supportDesc material="chart">
<extent>60 ff. <dimensions type="leaf" unit="cm">
<height>18.2</height>
<width>13.0</width>
</dimensions>
<dimensions type="written" unit="cm">
<height>13.2</height>
<width>7.8</width>
</dimensions>
</extent>
<condition>
<p>The paper is worm-eaten and slightly foxed. Folio 60 is
slightly water-damaged and has an unrepaired hole near the
centre.</p>
</condition>
</supportDesc>
<layoutDesc>
<layout columns="1" writtenLines="19">
<p>19 lines per page.</p>
</layout>
</layoutDesc>
</objectDesc>
<handDesc>
<handNote scope="major" script="naskh">
<p>Written in a medium-small compact <term>Naskh</term> script
tending towards <term>Nastaʿlīq</term>, in dense-black ink with
headings in red ink; some headings are now slightly tarnished,
and may have been either blue or silver at one time. There are
catchwords.</p>
</handNote>
</handDesc>
<additions>
<p>There are occasional marginalia in several hands, sometimes extensive
(e.g., folios 9b 16a, 33b, 54a), as well as some interlinear
annotations (e.g., 1b).</p>
</additions>
<bindingDesc>
<p>The volume is bound in pasteboard covers and an envelope flap. The
exterior covers and flap are simple tan paper, undecorated. The
spine is a dark-brown leather, and the fore-edge flap a more recent
light-tan soft leather. The plain pastedowns and envelope flap
lining are modern. There are no endpapers.</p>
</bindingDesc>
</physDesc>
<history>
<origin><date calendar="Gregorian" notBefore="1500" notAfter="1600"
type="approxDate">16th Century</date></origin>
<provenance>
<p>The volume is from the private collection of <name type="person"
>Jacob Golius</name>
<date calendar="Gregorian" when="1667">(d. 1667)</date> who acquired
manuscripts in the <date calendar="Gregorian" notBefore="1620"
notAfter="1630">1620s</date> (mostly in <name type="place"
>Syria</name>). The manuscript was purchased in <date
calendar="Gregorian" when="1696">1696</date> by <name
type="person">Narcissus Marsh</name>, Archbishop of Armagh</p>
</provenance>
<acquisition>
<p>Bequeathed to the <name type="org">Bodleian Library</name> by <name
type="person">Narcissus Marsh</name>, Archbishop of Armagh, upon
his death in <date calendar="Gregorian" when="1713">1713</date>.</p>
</acquisition>
</history>
<additional>
<adminInfo>
<recordHist>
<source>Manuscript description based on the Bodleian Library's
public card index of Arabic manuscripts with additional
enhancements by the OCIMCO project team.</source>
</recordHist>
<availability status="restricted">
<p>Entry to read in the Library is permitted only on presentation of
a valid reader's card (for admissions procedures contact <ref
target="http://www.bodleian.ox.ac.uk/services/admissions/"
>Bodleian Admissions</ref>). Contact
<email>oriental@bodleian.ox.ac.uk</email> for further
information on the availability of this manuscript</p>
</availability>
<note/>
</adminInfo>
</additional>
</msDesc>
</sourceDesc>
</fileDesc>
<encodingDesc>
<classDecl>
<taxonomy xml:id="LCSH">
<bibl><ref target="http://id.loc.gov/authorities/about.html#lcsh">Library of
Congress Subject Headings</ref></bibl>
</taxonomy>
</classDecl>
</encodingDesc>
<profileDesc>
<textClass>
<keywords scheme="#LCSH">
<list>
<item><ref target="http://id.loc.gov/authorities/sh85083116#concept"
>Medicine, Arabic</ref></item>
<item><ref target="http://id.loc.gov/authorities/sh85134723#concept"
>Therapeutics</ref></item>
</list>
</keywords>
</textClass>
</profileDesc>
<revisionDesc>
<change when="2009-05-14">
<name type="person">Alasdair Watson</name> created this file on 14 May 2009.
</change>
</revisionDesc>
</teiHeader>
<facsimile>
<!-- facsimile information about the manuscript -->
<graphic url="folio1r.png"/>
<graphic url="folio1v.png"/>
<graphic url="folio2r.png"/>
<graphic url="folio2v.png"/>
<!-- Alternatively you could provide 'surface' elements with more than one image per surface,
and optionally with 'zone' elements to give coordinates for any special areas of
interest -->
</facsimile>
<text>
<body>
<!-- If you had a transcription of the manuscript you would put it here -->
<p/>
</body>
</text>
</TEI>
The TEI Header Elements
The header of a TEI document provides a mechanism for describing an encoded work so that the text itself, its source(s), its encoding, and its revisions are all thoroughly documented. The <teiHeader> element provided for this purpose has four principal components:
- <fileDesc> (file description)
- contains a full bibliographic description of an electronic file.
- <encodingDesc> (encoding description)
- documents the relationship between an electronic text and the source or sources from which it was derived.
- <profileDesc> (text-profile description)
- provides a detailed description of non-bibliographic aspects of a text, specifically the languages and sublanguages used, the situation in which it was produced, the participants and their setting.
- <revisionDesc> (revision description)
- summarizes the revision history for a record.
The file description <fileDesc>
<fileDesc>
<titleStmt>
<title>MS. Marsh 80 - OXFORD AND CAMBRIDGE ISLAMIC MANUSCRIPT CATALOGUES ONLINE</title>
<funder>JISC</funder>
<principal>Gillian Evison</principal>
</titleStmt>
<publicationStmt>
<date calendar="Gregorian">[Date when first made available]</date>
<publisher>Bodleian Library</publisher>
<pubPlace>
<address>
<addrLine>Department of Special Collections</addrLine>
<addrLine>Bodleian Library</addrLine>
<street>Broad Street</street>
<settlement>Oxford</settlement>
<postCode>OX1 3BG</postCode>
<addrLine><ref target="http://www.bodleian.ox.ac.uk/libraries/collections">Bodleian Library
</ref></addrLine>
<addrLine><email>oriental@bodleian.ox.ac.uk</email></addrLine>
</address>
</pubPlace>
<idno>OCIMCO</idno>
</publicationStmt>
<sourceDesc>
<msDesc xmlns="http://www.tei-c.org/ns/1.0" xml:id="OCIMCO" xml:lang="eng">
...
</msDesc>
</sourceDesc>
</fileDesc>
The OCIMCO project makes use of the three mandatory elements in the <fileDesc> section to provide a bibliographic description of each machine-readable record. The <titleStmt> (title statement) groups information about the <title> of the record and those responsible for its intellectual content, namely the principal researcher/project manager <principal> Gillian Evison and the organization responsible for the funding of the project <funder>, the JISC.
The <publicationStmt> (publication statement) is used to group information concerning the publication or distribution of the record. The Bodleian Libraries act as <publisher> of the manuscript records, and the statement includes both the <date> of publication and the publisher's physical, online, and e-mail addresses. The identifier <idno> by which the project is known, OCIMCO, is also provided as part of the publication statement.
The <sourceDesc> (source description) finally describes the source from which an electronic record was derived or generated, which is the place for the detailed <msDesc> (manuscript description) used by the OCIMCO project, which will be discussed below.
The encoding description <encodingDesc>
<encodingDesc>
<classDecl>
<taxonomy xml:id="LCSH">
<bibl><ref target="http://id.loc.gov/authorities/about.html#lcsh">Library of
Congress Subject Headings</ref></bibl>
</taxonomy>
</classDecl>
</encodingDesc>
The OCIMCO project makes use of the TEI header's encoding description <encodingDesc> section as a place to record classification declarations in the <classDecl> element. This element contains one or more taxonomies <taxonomy> defining any descriptive classification schemes used by other parts of the header, primarily the <profileDesc> (text-profile description). An xml:id attribute is provided as a point of reference for the keywords used in the latter section. The OCIMCO project uses LCSH<ref>Library of Congress Subject Headings</ref> as its main vocabulary, which is identified by the URI in the target attribute.
The text-profile description <profileDesc>
<profileDesc>
<textClass>
<keywords scheme="#LCSH">
<list>
<item><ref target="http://id.loc.gov/authorities/sh85083116#concept"
>Medicine, Arabic</ref></item>
<item><ref target="http://id.loc.gov/authorities/sh85134723#concept"
>Therapeutics</ref></item>
</list>
</keywords>
</textClass>
</profileDesc>
The OCIMCO project uses the <textClass> element within the <profileDesc> section to classify a text by reference to the taxonomy defined in the <classDecl> element in the <encodingDesc> section, namely LCSH. The headings are recorded in a <keywords> section, the scheme attribute of which identifies the controlled vocabulary defined in the previous section. Each subject heading constitutes an <item> in the list of keywords, which references <ref's> the exact concept via a URI in the target attribute.
The revision description <revisionDesc>
<revisionDesc>
<change when="2009-05-14">
<name type="person">Alasdair Watson</name> created this file on 14 May 2009.
</change>
</revisionDesc>
The OCIMCO project records all changes to individual records in the <revisionDesc> element. This element provides essential information for the administration of large numbers of files which are being updated, corrected, or otherwise modified as well as extremely useful documentation for records being passed from researcher to researcher or system to system. This section provides an important mechanism particularly for a collaborative project like OCIMCO to log changes and provides a basic versioning mechanism for the encoders. Each change to a record is recorded in a time-stamped <change> element, using the @when attribute.
The Manuscript Description Elements
The Manuscript Description module provides a <msDesc> element for the purpose of a detailed description of a single identifiable manuscript. It appears within the <sourceDesc> element (see above) in the header of a TEI-conformant document, where the document being encoded is a digital representation of the manuscript original, whether as an encoded transcription in a <text> section, as a collection of digital images in a <facsimile> section, or as some combination of the two. The <msDesc> element has the following components, which provide more detailed information under a number of headings:
- <msIdentifier> (manuscript identifier)
- contains the information required to identify the manuscript being described.
- <msContents> (manuscript contents)
- describes the intellectual content of a manuscript or manuscript part, either as a series of paragraphs or as a series of structured manuscript items.
- <physDesc> (physical description)
- contains a full physical description of a manuscript or manuscript part, optionally subdivided using more detailed elements.
- <history>
- groups elements describing the full history of a manuscript or manuscript part.
- <additional>
- groups additional information, combining bibliographic information about a manuscript, or surrogate copies of it with curatorial or administrative information.
The manuscript identifier <msIdentifier>
<msIdentifier>
<country>United Kingdom</country>
<region type="county">Oxfordshire</region>
<settlement>Oxford</settlement>
<institution>Oxford University</institution>
<repository>Bodleian Library</repository>
<collection type="main">Oriental Collection
<collection type="sub">Marsh Collection</collection>
</collection>
<idno>MS. Marsh 80</idno>
<altIdentifier type="other">
<idno>9076</idno>
</altIdentifier>
</msIdentifier>
The <msIdentifier> (manuscript identifier) element is intended to provide an unambiguous means of uniquely identifying a particular manuscript. The OCIMCO project provides this identification in a structured way, by providing detailed information about the holding institution (the institution owning the manuscript, unless stated otherwise), collection, shelfmark, and other identifiers used to indicate its location.
The OCIMCO project uses the following non-repeatable elements available within <msIdentifier> to identify the holding institution: <country>, the name of a geo-political unit, such as a nation, country, colony, or commonwealth, in the OCIMCO project this is always the United Kingdom; <region>, the name of an administrative unit such as a state, province, or county, larger than a settlement, but smaller than a country, i.e. Oxfordshire or Cambridgeshire; <settlement>, the name of a settlement such as a city, town, or village identified as a single geo-political or administrative unit, i.e. Oxford or Cambridge; <institution>, the name of an organization such as a university or library, with which a manuscript is identified, generally its holding institution, i.e. Oxford University or Cambridge University; <repository>, the name of a repository within which manuscripts are stored, possibly forming part of an institution, i.e. the Bodleian Library or Cambridge University Library.
The manuscripts themselves are identified more precisely within the holding institutions using these elements: <collection>, the name of a collection of manuscripts, not necessarily located within a single repository, here both the main collection and sub collection to which the manucript belongs are given; <idno> (identifier), which supplies any form of identifier used to identify a bibliographic item in a standardized way, most often the item's shelfmark; <altIdentifier> (alternative identifier), an alternative or former structured identifier used for a manuscript, such as a former catalogue number.
The OCIMCO project adheres to the preferred form of citation for manuscript shelfmarks, including rules about punctuation, spacing, abbreviation, etc., used in each of the two institutions.
The manuscript contents <msContents>
<msContents>
<msItem>
<author>
<persName xml:lang="ara-Latn-x-lc" type="standard" key="n 80129268"
ref="http://viaf.org/viaf/90058060/">Qumrī, Abū Manṣūr
al-Ḥasan ibn Nūḥ,
<date calendar="Gregorian" notBefore="1000"
notAfter="1100">11th cent.</date>
</persName>
<persName xml:lang="ara">
<surname>بن نوح</surname>
<forename>الحسن</forename>
<addName type="kunyah">أبو منصور</addName>
<addName type="nisbah">القمري</addName>
</persName>
</author>
<title xml:lang="ara-Latn-x-lc">Kitāb al-Ghiná wa-al-muná</title>
<title xml:lang="ara-Latn-x-lc" type="alt">al-Shamsīyah
al-Manṣūrīyah</title>
<title xml:lang="ara">كتاب الغنى والمنى</title>
<title xml:lang="ara" type="alt">الشمسية المنصورية</title>
<note>It is an incomplete copy. The text breaks off at the bottom of
folio 60b in the fifty-first bāb of the first maqālah. A complete
table of contents for the full treatise is given on folios 2a−3a.
Maqālah 1 starts on folio 3a.</note>
<incipit xml:lang="ara">بسم الله الرحمن الرحيم، الحمد لله رب العالمين
والعاقبة للمتقين...قال ابو منصور الحسن بن نوح القمري رحمه الله اني
لم ازل في صباي ومنذ عقلت احب العلوم الطبيعية وينازعني نفسي اليها
وخصوصا علم الطب</incipit>
<explicit xml:lang="ara" defective="true">فانه كثيرا ما ينقطع بذلك
والانكباب على بخار الشراب التي القيت فيه حجارة محماة فان لم ينقطع
فيجب ان يجذب المادة }}التي ينصب الى {{الحنك</explicit>
<note>At the bottom of the page, a different more cursive hand has
written: <foreign xml:lang="ara">والله الهادي الى الطريق تمت
الكتاب</foreign>
</note>
<listBibl>
<bibl>Golius Sale Cat., med. qu. 12</bibl>
<bibl>UAM 147 entry DCXLII (642)</bibl>
<bibl>NPAE, 590</bibl>
<bibl>GAL I 239</bibl>
<bibl>GAS III 319</bibl>
</listBibl>
<textLang mainLang="ara">Arabic</textLang>
</msItem>
</msContents>
The <msContents> element is used to describe the intellectual content of a manuscript or manuscript part. The OCIMCO project uses one or more nestable <msItem> elements, each of which provides a more detailed description of a single item contained within the manuscript. Each discrete item in a manuscript or manuscript part is described with a number of component elements that can contain the author of the work, its title, a statement of responsibility for supplied information, rubrics, incipit, explicit, quotations, colophon, a note on decoration, a citation list, bibliographic citations, information concerning the manuscript's filiation, the language of the text, and general notes or annotations.
The OCIMCO project follows the recommendation that the <author> element should always contain the normalized form of an author's name, irrespective of how (or whether) this form of the name is cited in the manuscript. For this purpose the first <persName> (personal name) element gives the name of the author according to LCNAF<ref>Library of Congress Name Authority File</ref>, where the xml:lang attribute records the language code according to RFC 5646/RFC 4647, the key attribute contains the LC Control Number, and the ref attribute the name according to VIAF<ref>Virtual International Authority File</ref>. It also includes any <date> given, where the calendar attribute as well as notBefore and notAfter are used to allow for an as precise recording of dates as is possible. The form of the author's name as given in the manuscript is always retained in the form of an additional <persName> element, which gives the original language in the xml:lang attribute and is subdivided into <surname> and <forename> elements for better indexing and processing. Language-specific name components or additions, here the Arabic kunyah and nisbah, are recorded in <addName> (additional name) elements identified by the type attribute.
Similarly, the OCIMCO project follows the guideline for titles, namely that when used within a manuscript description, the <title> element should be used to supply a regularized form of the item's title, as distinct from any rubric quoted from the manuscript. Titles as well as alternative or supplied titles, which are identified using the type attribute, are therefore recorded both in Latin transliteration as well as in the original language, identified by the xml:lang attribute.
The OCIMCO project also records both the <incipit>, the opening words of the text proper, and <explicit>, the closing words of a manuscript, of sufficient length to identify the work uniquely. Any other copy-specific information concerning the intellectual content of the manuscript is recorded in plain text in <note> elements. The text language <textLang> is used to provide information about the languages and writing systems used within the manuscript, the mainLang attribute records the particular languages used similarly to the global xml:lang attribute.
Each manuscript description also contains a <listBibl> (citation list) element that contains a list of bibliographic citations of any kind. The OCIMCO project uses the following citations: ...
The physical description <physDesc>
<physDesc>
<objectDesc form="codex">
<supportDesc material="chart">
<extent>60 ff.
<dimensions type="leaf" unit="cm">
<height>18.2</height>
<width>13.0</width>
</dimensions>
<dimensions type="written" unit="cm">
<height>13.2</height>
<width>7.8</width>
</dimensions>
</extent>
<condition>
<p>The paper is worm-eaten and slightly foxed. Folio 60 is
slightly water-damaged and has an unrepaired hole near the
centre.</p>
</condition>
</supportDesc>
<layoutDesc>
<layout columns="1" writtenLines="19">
<p>19 lines per page.</p>
</layout>
</layoutDesc>
</objectDesc>
<handDesc>
<handNote scope="major" script="naskh">
<p>Written in a medium-small compact <term>Naskh</term> script
tending towards <term>Nastaʿlīq</term>, in dense-black ink with
headings in red ink; some headings are now slightly tarnished,
and may have been either blue or silver at one time. There are
catchwords.</p>
</handNote>
</handDesc>
<additions>
<p>There are occasional marginalia in several hands, sometimes extensive
(e.g., folios 9b 16a, 33b, 54a), as well as some interlinear
annotations (e.g., 1b).</p>
</additions>
<bindingDesc>
<p>The volume is bound in pasteboard covers and an envelope flap. The
exterior covers and flap are simple tan paper, undecorated. The
spine is a dark-brown leather, and the fore-edge flap a more recent
light-tan soft leather. The plain pastedowns and envelope flap
lining are modern. There are no endpapers.</p>
</bindingDesc>
</physDesc>
The physical description <physDesc> wrapper element subsumes a large number of different aspects generally regarded as useful in the description of manuscripts. These include aspects of the form, support, extent, and quire structure of the manuscript object and of the way in which the text is laid out on the page: the object description (<objectDesc>); the styles of writing, such as the way it is laid out on the page, the styles of writing, decorative features, any musical notation employed and any annotations or marginalia: the description of hands (<handDesc>); and discussion of its binding, seals, and any accompanying material: the binding description (<bindingDesc>). The OCIMCO project uses a combination of approaches in the encoding of the physical description section: it records highly detailed descriptions (where available) in the form of a container section of more specialized elements described below, and less detailed descriptions in the form of a series of free-text paragraphs.
The OCIMCO project makes use of the <objectDesc> element to group together those parts of the physical description which relate specifically to the text-bearing object, its format, constitution, layout, etc. The form attribute is used to indicate the specific type of writing vehicle being described, here a codex. The <objectDesc> element has two parts: a description of the support, i.e. the physical carrier on which the text is inscribed; and a description of the layout, i.e. the way text is organized on the carrier. The <supportDesc> (support description) groups elements describing the physical support for the written part of a manuscript, such as a description of the materials which make up the physical support for the written part of a manuscript, the approximate size of a text as stored on some carrier medium specified in any convenient units, a description of how the leaves or bifolia are physically arranged, the numbering system or systems used to count the leaves or pages in a codex, and a description of the physical condition of the manuscript. In our example the material is indicated with the @material attribute of the <supportDesc> element, the <extent> element groups both the number of folios and the <dimensions> of the leaves and of the written text, which have been encoded in cm using the <height> and <width> elements. A simple paragraph finally summarizes the overall physical state of a manuscript within the <condition> element.
The history of the manuscript <history>
<history>
<origin>
<date calendar="Gregorian" notBefore="1500" notAfter="1600"
type="approxDate">16th Century</date>
</origin>
<provenance>
<p>The volume is from the private collection of <name type="person"
>Jacob Golius</name> <date calendar="Gregorian" when="1667">(d. 1667)</date> who acquired
manuscripts in the <date calendar="Gregorian" notBefore="1620"
notAfter="1630">1620s</date> (mostly in <name type="place"
>Syria</name>). The manuscript was purchased in <date
calendar="Gregorian" when="1696">1696</date> by <name
type="person">Narcissus Marsh</name>, Archbishop of Armagh</p>
</provenance>
<acquisition>
<p>Bequeathed to the <name type="org">Bodleian Library</name> by <name
type="person">Narcissus Marsh</name>, Archbishop of Armagh, upon
his death in <date calendar="Gregorian" when="1713">1713</date>.</p>
</acquisition>
</history>
Any additional information <additional>
<additional>
<adminInfo>
<recordHist>
<source>Manuscript description based on the Bodleian Library's
public card index of Arabic manuscripts with additional
enhancements by the OCIMCO project team.
</source>
</recordHist>
<availability status="restricted">
<p>Entry to read in the Library is permitted only on presentation of
a valid reader's card (for admissions procedures contact <ref
target="http://www.bodleian.ox.ac.uk/services/admissions/"
>Bodleian Admissions</ref>). Contact
<email>oriental@bodleian.ox.ac.uk</email> for further
information on the availability of this manuscript</p>
</availability>
<note/>
</adminInfo>
</additional>
Coding Commentaries
Here at OCIMCO, we are struggling to find a satisfactory method of coding works of a derivative nature such as commentaries and translations. One method favours putting the information about the work the commentary etc., is based on in a <summary>, another in a <note>. We are still experimenting, but have come up with a possible solution to this by putting all the information in a <title> element with subelements such as another <title> for the original work the commentary was based on and <name> for the author of the original work. We are wondering if it is possible to indicate the priority of the works by having a type attribute value of, say, "primary", "secondary", etc., for the <title> and <author> elements? Please see below for a coded example:
<msItem>
<author>
<persName xml:lang="ara-Latn-x-lc" type="standard">Qūshjī, ʻAlī
ibn Muḥammad, d. 1474 or 5</persName>
<persName xml:lang="ara-Latn-x-lc" type="alt">al-Qawshajī, ʻAlī
ibn Muḥammad, ʻAlāʼ al-Dīn</persName>
<persName xml:lang="ara" type="standard">
<surname>بن محمد</surname>
<forename>علي</forename>
<addName type="laqab">علاء الدين</addName>
<addName type="kunyah">أبو القاسم</addName>
<addName type="nisbah">القوشجي</addName>
</persName>
</author>
<docAuthor>Qūshjī, ʿAlāʾ al-Dīn ʿAlī ibn Muḥammad d. 1474.</docAuthor>
<title><foreign xml:lang="ara-Latn-x-lc">al-Sharḥ al-jadīd</foreign>, a
commentary on the <title xml:lang="ara-Latn-x-lc">Tajrīd
al-ʿaqāʾid</title> of <name type="person"
xml:lang="ara-Latn-x-lc">Naṣīr al-Dīn al-Ṭūsī</name>,
1201-1274.</title>
<title xml:lang="ara">الشرح الجديد شرح تجريد الاعتقاد لنصير الدين الطوسي</title>
<note/>
<listBibl>
<bibl>GAL I 509</bibl>
<bibl/>
</listBibl>
<textLang mainLang="ara">Arabic</textLang>
</msItem>
Please see #Expressing Bibliographic Relations for Cambridge practice
CAMBRIDGE WORKING PRACTICES
Expressing Bibliographic Relations
In Cambridge we are using the type attribute in <bibl> to indicate the type of bibliographic relationship being described. Currently we are using "text-relations" for bibliographic affiliations (i.e. commentaries etc.) and "related items" to indicate either other copies of the same work or other volumes in the same set.
Examples of "text-relations":
<msContents>
<summary/>
<msItem class="commentary">
<author key="nr91037727" ref="http://viaf.org/viaf/90046369/">
<persName xml:lang="ara-Latn-x-lc" type="standard">Quṭb
al-Taḥtānī, Muḥammad ibn Muḥammad, 1294 or 5-1364 or
5</persName>
<persName xml:lang="ara-Latn-x-lc" type="org"/>
<persName xml:lang="ara-Latn-x-lc" type="alt"/>
<persName xml:lang="ara">قطب الدين الرازي <surname/>
<forename/>
<addName xml:lang="ara" type="laqab"/>
<addName xml:lang="ara" type="kunyah"/>
<addName xml:lang="ara" type="khitab"/>
<addName xml:lang="ara" type="nisbah"/>
</persName>
</author>
<respStmt>
<resp key="trl"/>
<persName/>
</respStmt>
<docAuthor/>
<title xml:lang="ara-Latn-x-lc">Sharḥ al-risālah al-shamsīyah</title>
<title xml:lang="ara-Latn-x-lc" type="alt"/>
<title xml:lang="ara">شرح الرسالة الشمسية</title>
<listBibl>
<bibl>
record in printed catalogue >no. 813
<bibl type="text-relations">Commentary on the <title
xml:lang="ara-Latn-x-lc">al-Risālah al-shamsīyah<foreign>
xml:lang="ara">الرسالة الشمسية</foreign>
</title> of <persName xml:lang="ara-Latn-x-lc" key="nr93027510"
>Qazwīnī, ʻAlī ibn ʻUmar, 1203 or 4-1276 or 7
<foreign>xml:lang="ara">نمجم الدين علي الكاتبى القزوينى</foreign>.</persName>
<textLang mainLang="ara">Arabic</textLang>
</msItem>
</msContents>
<listBibl>
<bibl>record in printrd catalogue >no. 1057</bibl>
<bibl type="text-relations">The manuscript contains also the
glosses of al-Fanārī on al-Taftāzānī's al-Muṭawwal, which is
a commentary on the <title xml:lang="ara-Latn-x-lc">Talkhīṣ
al-miftāḥ</title><foreign>xml:lang="ara">تلخيص
المفتاح</foreign>of <persName xml:lang="ara-Latn-x-lc"
>Qazwīnī, Jalāl al-Dīn Muḥammad ibn ʻAbd
al-Raḥmān, 1267 or 8-1338</persName>
<foreign>xml:lang="ara">القزوينى، جلا ل الدين محمد بن
عبدالرحمان</foreign>. This last work is, in turn, an
abridgement of the <title xml:lang="ara-Latn-x-lc"
>Miftāḥal-ʻulūm</title><foreign> xml:lang="ara">مفتاح
العلوم</foreign> of <author key="84031911"
ref="http://viaf.org/viaf/61532835/"><persName
xml:lang="ara-Latn-x-lc">Sakkākī, Yūsuf ibn Abī
Bakr, b. 1160</persName>
<persName xml:lang="ara">السكاكي، يوسف بن أبي
بكر</persName></author>.</bibl>
</adminInfo> <listBibl type="related-items"> <bibl>Other copies: <idno>Oo. 6. 32</idno>, and <idno>Add. 199</idno>.</bibl> </listBibl> </additional>
</adminInfo> <listBibl type="related-items"> <bibl>Other copies: <idno>Add. 191</idno>, which contains the entire dictionnary; and <idno>Add. 181</idno>, containing the first part of this work.</bibl> </listBibl> </additional>
REFERENCES
<references/>
